Results for “fnd_conc_req_stat”

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

Overview

FND_CONC_REQ_STAT is a table in the APPLSYS schema that belongs to the FND (Application Object Library) product within Oracle E-Business Suite. Its name and structure indicate that it stores runtime statistics associated with concurrent requests managed by the Concurrent Manager subsystem. Each row captures a single statistic value for a specific request and process type, allowing the system to record performance or execution metrics tied to individual concurrent program invocations.

The documented description carries the note "Retrofitted," indicating that the object was introduced or adjusted to conform to a later architectural convention while remaining compatible with earlier releases. In Oracle EBS 12.1.1 and 12.2.2 this table functions as an internal operational repository rather than a user-facing transactional entity. Its heuristic Data Vault classification, mined from the documented foreign key structure, is standalone. Following standard Data Vault modeling practice, it may be treated as an independent satellite-like structure keyed on REQ_ID, PROCESS_TYPE, and STATISTIC#, without a parent hub or link dependency in the documented metadata.

Key Information Stored

The documented physical schema comprises four columns stored under the APPLSYS owner. The primary key FND_CONC_REQ_STAT_PK is a composite key defined over REQ_ID, PROCESS_TYPE, and STATISTIC#. The most significant columns are:

• REQ_ID — Identifies the concurrent request to which the statistic belongs. This is the principal business-key candidate linking the row to FND_CONCURRENT_REQUESTS.
• PROCESS_TYPE — Distinguishes the concurrent manager process or phase (for example, the worker or a specific manager type) under which the statistic was gathered.
• STATISTIC# — A numeric identifier or sequence that labels the particular statistic being tracked. Together with REQ_ID and PROCESS_TYPE it forms the unique composite key.
• VALUE — The measured quantity for the statistic, such as elapsed time, rows processed, or other runtime counter associated with the request and process type.

All three key columns are business-key candidates rather than a single surrogate identifier; the composite primary key enforces uniqueness across the request, process type, and statistic number combination. The VALUE column carries the payload of the record.

Common Use Cases and Queries

Because this table records per-request process statistics, its primary use is diagnostic and performance-oriented reporting. DBAs and developers query it to trace concurrent request behavior, detect slow-running programs, and correlate statistics with specific process types. Typical patterns include joining REQ_ID back to FND_CONCURRENT_REQUESTS to obtain the program name, phase, and status.

• Retrieving all statistics for a given request: SELECT PROCESS_TYPE, STATISTIC#, VALUE FROM APPLSYS.FND_CONC_REQ_STAT WHERE REQ_ID = :req_id;
• Aggregating values by statistic across requests to profile concurrent program performance.
• Joining to FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS to attribute statistics to specific programs and users.
• Feeding monitoring or AWR-style reporting that summarizes Concurrent Manager throughput.

Related Objects

The documented relationship data classifies this object as standalone, but the REQ_ID column logically associates it with the concurrent request and program infrastructure. Significant related objects include:

• FND_CONCURRENT_REQUESTS — joined on REQ_ID; the parent record of every request.
• FND_CONCURRENT_PROGRAMS — defines the executable programs whose requests are tracked.
• FND_CONCURRENT_PROGRAM_SERIAL — governs serialization of program runs referenced by requests.
• FND_CONCURRENT_QUEUES — the queues through which requests and their statistics are processed.
• FND_CONCURRENT_WORKER_REQUESTS / FND_CONCURRENT_PROCESSES — the process infrastructure that produces the PROCESS_TYPE dimension.

These joins allow statistic data to be reported in the context of the broader Concurrent Manager model.