Search Results ar_conc_process_requests_u1




Overview
Explore in AI Chat

Overview

The AR.AR_CONC_PROCESS_REQUESTS table is an Oracle Receivables control table that tracks the list of AutoInvoice and Customer Merge concurrent requests that are, or should be, currently running within an EBS instance. Because the AutoInvoice and Customer Merge programs support multiple concurrent instances, this table serves as the authoritative registry of which request instances are considered "current." If AutoInvoice encounters an error or terminates abnormally, the corresponding row is marked with the request that is not current; a subsequent run of AutoInvoice re-marks that row. This coordination mechanism prevents stale or orphaned request identifiers from being treated as active and is therefore central to the correctness of high-volume Receivables processing in both 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. It functions as an auxiliary attribute table anchored to the concurrent request infrastructure, carrying process-state information rather than serving as an independent hub or a many-to-many link. The classification is heuristic and should be treated as a modeling suggestion rather than a physical constraint.

Key Information Stored

The documented physical schema is intentionally minimal, containing only two columns. The most important elements are:

  • REQUEST_ID (NUMBER(15)) — The primary key of the table and the sole column of the unique index AR_CONC_PROCESS_REQUESTS_U1. It identifies the concurrent request and is the concurrent program "who column," acting as a foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID.
  • CONCURRENT_PROGRAM_NAME (VARCHAR2(30)) — The name of the concurrent process (for example, the AutoInvoice or Customer Merge program) associated with the request row. This is a descriptive attribute rather than a key candidate.

The surrogate primary key is REQUEST_ID, and the unique index AR_CONC_PROCESS_REQUESTS_U1 (REQUEST_ID) is the business-key candidate documented in the metadata. The table is stored in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and the unique index resides in APPS_TS_TX_IDX. The dependency metadata notes that this table references no other database object, though REQUEST_ID functionally maps to FND_CONCURRENT_REQUESTS.

Common Use Cases and Queries

Typical scenarios include diagnosing stuck AutoInvoice runs, identifying which request instances are currently regarded as active, and reconciling Receivables request activity against the concurrent manager. A straightforward listing query is:

  • SELECT CONCURRENT_PROGRAM_NAME, REQUEST_ID FROM AR.AR_CONC_PROCESS_REQUESTS;
  • Joining to the concurrent requests infrastructure to retrieve program and phase details: SELECT a.CONCURRENT_PROGRAM_NAME, a.REQUEST_ID, r.PHASE_CODE, r.STATUS_CODE FROM AR.AR_CONC_PROCESS_REQUESTS a, FND_CONCURRENT_REQUESTS r WHERE a.REQUEST_ID = r.REQUEST_ID;
  • Filtering to a specific program for operational monitoring: SELECT REQUEST_ID FROM AR.AR_CONC_PROCESS_REQUESTS WHERE CONCURRENT_PROGRAM_NAME = 'RAXMTR';
  • Detecting orphaned rows where the referenced concurrent request no longer exists, using an outer join against FND_CONCURRENT_REQUESTS.

Reporting use cases center on operational health checks of AutoInvoice and Customer Merge throughput and on troubleshooting duplicate or conflicting program instances.

Related Objects

The table is referenced by the APPS synonym AR_CONC_PROCESS_REQUESTS, which is the normal access path for application and reporting code. The principal related object is FND_CONCURRENT_REQUESTS, joined on REQUEST_ID, which supplies lifecycle and phase information absent from this table. AutoInvoice (RAXMTR/RAXTRX) and Customer Merge (ARXCMER) programs interact with this table as part of their run-time coordination logic. Additional dependencies include the Receivables interface and customer merge processing tables that these programs populate, though the documented metadata establishes FND_CONCURRENT_REQUESTS and the APPS synonym as the most significant directly related objects.