Results for “concurrent_request_id”

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

Overview

RG_REPORT_SET_REQ_DETAILS is a table in the RG (Application Report Generator) schema of Oracle E-Business Suite. It records the individual reports executed as part of a report set submission. For every report set submitted through the Application Report Generator, this table holds one row per constituent report run, providing the drill-down layer beneath the parent report set submission. Its role is to bridge the logical definition of a report set to the concrete concurrent requests that actually execute each report, enabling tracking, auditing, and re-submission of grouped reports.

The supplied metadata classifies this object, using a heuristic Data Vault lens, as a link table. This is a modeling suggestion: RG_REPORT_SET_REQ_DETAILS resolves associations between a report set request, an individual report definition, and the concurrent request that executed it, rather than acting as a descriptive hub or satellite. Practically, it functions as a transaction detail table that records the one-to-many expansion of a report set into its member report submissions.

Key Information Stored

The table contains five documented columns, with the composite primary key and a unique business-key candidate carrying the identity semantics:

• REPORT_SET_REQUEST_ID — Foreign key to the parent report set submission in RG_REPORT_SET_REQUESTS. Identifies which report set run this detail row belongs to. Part of both the primary key and the unique index.
• SEQUENCE — Ordinal position of the detail row within a report set submission. Part of the primary key (RG_REPORT_SET_REQ_DETAILS_PK) and the unique index.
• REPORT_ID — Foreign key to RG_REPORTS, identifying the individual report definition that was run.
• CONCURRENT_REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS, linking the detail row to the actual concurrent program submission and its execution status, phase, and output.
• REPORT_SEQUENCE — Sequence value controlling the order in which the member reports are processed or presented within the report set.

The surrogate identity is the composite primary key RG_REPORT_SET_REQ_DETAILS_PK (REPORT_SET_REQUEST_ID, SEQUENCE). A second unique index, RG_REPORT_SET_REQ_DETAILS_U1, is defined on the same pair (REPORT_SET_REQUEST_ID, SEQUENCE), confirming the business key that uniquely identifies each report run per report set submission.

Common Use Cases and Queries

Typical scenarios include determining which reports ran under a given report set submission, resolving each member report to its concurrent request for status monitoring, and reporting on report set membership and ordering.

• Retrieve all reports for a report set request:

  SELECT d.sequence, d.report_id, d.report_sequence, d.concurrent_request_id
  FROM   rg_report_set_req_details d
  WHERE  d.report_set_request_id = :p_request_id
  ORDER  BY d.report_sequence;

• Join to concurrent requests to check execution phase and status:

  SELECT d.report_set_request_id, r.request_id, r.phase_code, r.status_code
  FROM   rg_report_set_req_details d,
         fnd_concurrent_requests  r
  WHERE  d.concurrent_request_id = r.request_id
  AND    d.report_set_request_id = :p_request_id;

• Resolve the report definition name:

  SELECT d.report_set_request_id, d.report_id, rg.report_name
  FROM   rg_report_set_req_details d,
         rg_reports               rg
  WHERE  d.report_id = rg.report_id
  AND    d.report_set_request_id = :p_request_id;

These queries support operational monitoring, diagnostics of partially completed report sets, and audit reporting on grouped report executions.

Related Objects

The table is anchored by three foreign-key relationships and one parent key relationship. The most significant related objects are:

• RG_REPORT_SET_REQUESTS — Parent table; joined on REPORT_SET_REQUEST_ID = REPORT_SET_REQUESTS.REPORT_SET_REQUEST_ID. Supplies the report set submission header.
• RG_REPORTS — Joined on REPORT_ID = RG_REPORTS.REPORT_ID. Provides the individual report definition and name.
• FND_CONCURRENT_REQUESTS — Joined on CONCURRENT_REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID. Provides execution phase, status, and completion details for each member report.
• FND_CONCURRENT_PROGRAMS — Typically referenced indirectly via the concurrent request to identify the executable program for each report.
• RG_REPORT_SET_REQ_DETAILS_PK / RG_REPORT_SET_REQ_DETAILS_U1 — Composite primary key and unique index that enforce uniqueness of each report run per submission.

Together, these relationships make RG_REPORT_SET_REQ_DETAILS the central link between report set definitions, their submissions, and the concurrent execution records that result.