Results for “rg_report_set_req_details_u1”

12 results




Overview
Explore in AI Chat

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

Overview

RG.RG_REPORT_SET_REQ_DETAILS is a transactional detail table in the Oracle E-Business Suite Report Group (RG) schema. It stores the line-level submission tracking records that make up a report set request, capturing for each report in a report set the associated concurrent request identifier and the order in which the report was submitted to the concurrent manager. The table is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and carries the FND Design Data reference RG.RG_REPORT_SET_REQ_DETAILS.

Its role is that of a child detail entity: each row describes one report within a single report set submission, while the header-level context (the report set request itself) lives in RG_REPORT_SET_REQUESTS. This structure enables EBS to track, per report set run, which concurrent request was generated for each member report and the sequence position of that report in the set definition.

From a heuristic Data Vault classification derived from the foreign key structure, this table models as a link (or, depending on interpretation, a link-satellite hybrid). Its associations connect a report set request, a report definition, and a concurrent request; it is not a standalone hub because it has no independent business key beyond the composite of its parent reference and sequence.

Key Information Stored

The table contains five documented columns, and the most significant are described below. The composite primary key RG_REPORT_SET_REQ_DETAILS_PK is defined on (REPORT_SET_REQUEST_ID, SEQUENCE), and the unique index RG_REPORT_SET_REQ_DETAILS_U1 mirrors this as (REPORT_SET_REQUEST_ID, SEQUENCE), making that pair the business-key candidate used to enforce one row per report position in a set.

  • REPORT_SET_REQUEST_ID (NUMBER(15)) — Report set request defining column; the foreign key back to RG_REPORT_SET_REQUESTS identifying the parent submission. It is the primary business-key column of the unique index RG_REPORT_SET_REQ_DETAILS_U1.
  • SEQUENCE (NUMBER) — Report sequence in the report set; the second component of the unique index and the primary key, ordering the reports within a set.
  • REPORT_ID (NUMBER(15)) — Report defining column; a foreign key to RG_REPORTS identifying which report definition the row represents.
  • CONCURRENT_REQUEST_ID (NUMBER(15)) — Report concurrent request id; a foreign key to FND_CONCURRENT_REQUESTS linking the row to the actual runtime submission of that report.
  • REPORT_SEQUENCE (NUMBER(15)) — A numeric sequence value carried for the report, used during submission ordering logic.

The stored index is defined on the columns REPORT_SET_REQUEST_ID and SEQUENCE and is of type NORMAL, uniqueness UNIQUE, located in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical scenarios include reconciling each report set submission to its underlying concurrent requests, auditing submission order, and reporting on which concurrent request corresponds to each member report. A straightforward query retrieves all detail rows for a given report set request, as documented:

  • SELECT REPORT_SET_REQUEST_ID, SEQUENCE, REPORT_ID, CONCURRENT_REQUEST_ID, REPORT_SEQUENCE FROM RG.RG_REPORT_SET_REQ_DETAILS;
  • Joining to FND_CONCURRENT_REQUESTS on CONCURRENT_REQUEST_ID to obtain phase, status, and completion details per report.
  • Joining to RG_REPORT_SET_REQUESTS on REPORT_SET_REQUEST_ID to resolve header-level submission metadata.
  • Aggregating counts of REPORT_ID per REPORT_SET_REQUEST_ID to confirm how many reports were submitted in a set.

These queries support operational troubleshooting of report set runs and historical auditing of concurrent reporting activity.

Related Objects

The table is bound to its neighbors through the following documented foreign keys and dependencies:

  • RG.RG_REPORT_SET_REQUESTS — referenced via REPORT_SET_REQUEST_ID, the parent header of each report set submission.
  • RG.RG_REPORTS — referenced via REPORT_ID, supplying the member report definition.
  • FND_CONCURRENT_REQUESTS — referenced via CONCURRENT_REQUEST_ID, linking to the runtime concurrent submission.
  • APPS.RG_REPORT_SET_REQ_DETAILS — a synonym/view dependency in the APPS schema used by application code.

The metadata notes that the table does not reference any other database object beyond the foreign keys listed, and it is referenced by the APPS synonym of the same name.