Results for “request_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CONC_PROCESS_REQUESTS is a Receivables module table in the AR schema that stores information about concurrent requests that are either currently running or have been terminated. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a lightweight tracking registry that Receivables concurrent programs use to record and monitor their own execution state and to coordinate processing across multiple program invocations. It does not hold transactional Receivables data such as invoices, receipts, or adjustments; instead it operates as an operational control structure that complements the standard Oracle Concurrent Manager framework.

The table is deliberately narrow, comprising only two documented columns: REQUEST_ID and CONCURRENT_PROGRAM_NAME. Despite this minimal footprint, it plays an important role in diagnostic and administrative workflows, allowing DBAs and support analysts to identify which Receivables programs are active, which have aborted, and which have been manually terminated. The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning, suggesting that the table is best modeled as a satellite hanging off a hub or link anchored by the concurrent request identity, rather than as an independent hub in its own right. This classification reflects the fact that the table describes attributes of an existing concurrent request entity maintained in FND_CONCURRENT_REQUESTS.

Key Information Stored

The documented physical schema exposes exactly two columns, and both are central to the table's purpose:

• REQUEST_ID — The primary key of the table, defined by the constraint AR_CONC_PROCESS_REQUESTS_PK. It is also the sole business-key candidate, enforced by the unique index AR_CONC_PROCESS_REQUESTS_U1. This column is a foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID, tying each row to the master concurrent request record maintained by the Concurrent Manager.
• CONCURRENT_PROGRAM_NAME — Holds the name of the concurrent program associated with the request. This denormalized value allows Receivables-specific logic and diagnostics to identify the program without joining to FND_CONCURRENT_PROGRAMS.

Because the primary key and the unique business-key index both target REQUEST_ID, the surrogate and business key are effectively the same column. No additional descriptive attributes such as status, phase, or timestamps are persisted in this table; those details must be retrieved from FND_CONCURRENT_REQUESTS when required.

Common Use Cases and Queries

Typical usage centers on operational monitoring and troubleshooting of Receivables concurrent processing. Analysts frequently query this table to enumerate currently running or terminated program instances and then join to the Concurrent Manager tables for status detail. A representative query is:

• SELECT acpr.request_id, acpr.concurrent_program_name, fcr.phase_code, fcr.status_code, fcr.actual_start_date, fcr.actual_completion_date FROM ar.ar_conc_process_requests acpr, fnd_concurrent_requests fcr WHERE acpr.request_id = fcr.request_id;
• Identifying stuck or terminated Receivables jobs by filtering on phase and status codes in FND_CONCURRENT_REQUESTS after joining on REQUEST_ID.
• Auditing which Receivables programs were executed during a specific interval by correlating the returned REQUEST_ID values with request history.
• Supporting cleanup routines that reconcile entries in AR_CONC_PROCESS_REQUESTS against the master request table to detect orphaned rows.

Because the table is small, queries against it are inexpensive, making it suitable for inclusion in dashboards and scheduled health checks.

Related Objects

The most significant relationship is with the Oracle Concurrent Manager infrastructure. The following objects are most relevant:

• FND_CONCURRENT_REQUESTS — The master table of all concurrent requests; joined on REQUEST_ID and the sole documented foreign key parent.
• FND_CONCURRENT_PROGRAMS — Provides program definitions and can be joined on CONCURRENT_PROGRAM_NAME for descriptive metadata.
• FND_CONCURRENT_PROGRAM_SERIAL and FND_CONCURRENT_QUEUES — Supply queue and serialization context for running programs.
• FND_CONCURRENT_REQUEST_OUTPUT and FND_CONCURRENT_REQUEST_LOG — Hold output and log files keyed by REQUEST_ID.
• FND_CONCURRENT_WORKER_REQUESTS — Links parent requests to child requests for multi-phase programs.
• AR_INTERIM_* and AR_* staging tables — Many Receivables batch programs that populate this control table also write to staging objects during the same run.

These relationships confirm that AR_CONC_PROCESS_REQUESTS is best understood as a satellite to the concurrent request hub, supporting Receivables-specific process tracking over the shared Concurrent Manager framework.