Results for “fnd_run_requests”

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

Overview

FND_RUN_REQUESTS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the setup information required to run the individual reports contained within report sets. When a report set is submitted as a concurrent request, Oracle EBS consults FND_RUN_REQUESTS to determine how each member program of that set should be executed — the arguments to pass, the printer to route output to, the print style to apply, the number of copies, and whether the output should be saved. Essentially, it is the execution-instance configuration layer that sits between the definition of a report set and the actual concurrent requests generated at runtime.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure suggests this object behaves as a link table. It connects parent concurrent requests, request set programs, concurrent programs, printers, and print styles through a composite key, rather than acting as a standalone hub of a single business entity or a pure descriptive satellite. Modelers should treat it as an associative construct that resolves a many-to-many relationship between report set members and the requests that execute them.

Key Information Stored

FND_RUN_REQUESTS contains 117 documented columns. The most significant, and the ones forming the composite primary key FND_RUN_REQUESTS_PK (also implemented as unique index FND_RUN_REQUESTS_U1), are:

• PARENT_REQUEST_ID — identifies the parent concurrent request that submitted the report set.
• REQUEST_SET_PROGRAM_ID — identifies the specific program within the request set.
• SET_APPLICATION_ID — the application owning the request set.
• REQUEST_SET_ID — the request set definition identifier.
• APPLICATION_ID and CONCURRENT_PROGRAM_ID — the concurrent program executed for this set member.
• REQUEST_ID — the child concurrent request generated from this row.
• NUMBER_OF_COPIES — copies to print.
• PRINTER and PRINT_STYLE — output routing and formatting.
• SAVE_OUTPUT_FLAG — whether output is retained after completion.
• ARGUMENT1 through ARGUMENT100 — the runtime parameters passed to the concurrent program.
• ORG_ID — the operating unit context for multi-org enabled programs.
• NLS_LANGUAGE, NLS_TERRITORY, NUMERIC_CHARACTERS — localization settings applied to the run.

The surrogate key is the composite of PARENT_REQUEST_ID, REQUEST_SET_PROGRAM_ID, SET_APPLICATION_ID, and REQUEST_SET_ID, which together constitute the business-key candidate enforced by the unique index.

Common Use Cases and Queries

Typical scenarios include auditing how a report set was configured for a given submission, tracing which child requests were spawned by a parent request, diagnosing missing or malformed arguments (ARGUMENT1–ARGUMENT100), and reporting on printer or output-routing configuration for batches of report set runs.

A representative query joins the parent request to its child execution rows:

SELECT frr.parent_request_id, frr.request_id, frr.concurrent_program_id,
       frr.printer, frr.print_style, frr.save_output_flag
FROM   applsys.fnd_run_requests frr
WHERE  frr.parent_request_id = :parent_request_id;

To pivot arguments for a specific child run, analysts frequently select ARGUMENT1..ARGUMENTn alongside FND_CONCURRENT_REQUESTS to correlate parameter values with a submitted program. Reporting use cases include reconciliation of report set output delivery, verification of printer defaults, and validation that ORG_ID and NLS settings match expectations across operating units.

Related Objects

The FK relationships documented in the ETRM metadata identify the following dependent and referenced objects:

• FND_CONCURRENT_REQUESTS — referenced twice, via PARENT_REQUEST_ID (the parent report set submission) and via REQUEST_ID (the individual child request).
• FND_REQUEST_SET_PROGRAMS — referenced through SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_PROGRAM_ID, linking run rows to set membership definitions.
• FND_CONCURRENT_PROGRAMS — referenced through APPLICATION_ID and CONCURRENT_PROGRAM_ID, supplying program metadata.
• FND_PRINTER — referenced through the PRINTER column for output routing.
• FND_PRINTER_STYLES — referenced through the PRINT_STYLE column for formatting.

Together these tables form the operational chain from report set definition through submission, execution, and printed output, with FND_RUN_REQUESTS serving as the central associative record captured at run time.