Results for “output_option”

12 results




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

Overview

The RG_REPORT_REQUESTS table is a core transactional object within the Application Report Generator (RG) product of Oracle E-Business Suite. It serves two closely related purposes: tracking individual report execution requests and defining the assignment of reports to report sets. In EBS 12.1.1 and 12.2.2, the table is owned by the RG schema and is classified as VALID. Each row effectively represents a request for a specific report, bound to a report set, governed by a ledger, a currency, a period, and a set of runtime options that determine how the report is rendered when submitted through the concurrent manager.

From a dimensional modeling perspective, the heuristic Data Vault classification of this table is link. This reflects its role as an associative structure that connects otherwise independent hubs — reports, report sets, ledgers, concurrent requests, row orders, and content sets — through its foreign keys. This classification should be treated as a modeling suggestion rather than a prescriptive fact, but it accurately captures the many-to-many, relationship-centric nature of the data.

Key Information Stored

The table contains 47 documented columns. The most functionally significant are:

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and fifteen ATTRIBUTE descriptor-flex columns are also present.

Common Use Cases and Queries

Typical use cases include auditing which reports were requested against a given ledger, tracing an RG request back to its concurrent request, and reconstructing how a report set was composed.

Resolving a specific request:

  • SELECT * FROM RG.RG_REPORT_REQUESTS WHERE REPORT_REQUEST_ID = :p_id;

Joining to the concurrent manager to determine execution status:

  • SELECT r.REPORT_REQUEST_ID, c.REQUEST_ID, c.PHASE_CODE, c.STATUS_CODE FROM RG.RG_REPORT_REQUESTS r JOIN FND_CONCURRENT_REQUESTS c ON r.CONCURRENT_REQUEST_ID = c.CONCURRENT_REQUEST_ID;

Listing all report requests for a ledger and period:

  • SELECT REPORT_REQUEST_ID, REPORT_ID, PERIOD_NAME FROM RG.RG_REPORT_REQUESTS WHERE LEDGER_ID = :ledger AND PERIOD_NAME = :period;

Related Objects

The following objects are directly referenced by foreign keys from RG_REPORT_REQUESTS and are the most significant for joining:

  • RG_REPORTS — via REPORT_ID; defines the report itself.
  • RG_REPORT_SETS — via REPORT_SET_ID; groups reports into sets.
  • FND_CONCURRENT_REQUESTS — via CONCURRENT_REQUEST_ID; execution and status tracking.
  • GL_LEDGERS — via LEDGER_ID; accounting ledger context.
  • FND_ID_FLEX_STRUCTURES — via APPLICATION_ID, ID_FLEX_CODE_11I, and STRUCTURE_ID; key flexfield definition.
  • FND_CURRENCIES — via UNIT_OF_MEASURE_ID_11I; currency/unit of measure.
  • RG_REPORT_CONTENT_SETS — via CONTENT_SET_ID.
  • RG_ROW_ORDERS — via ROW_ORDER_ID.
  • RG_REPORT_DISPLAY_SETS — via REPORT_DISPLAY_SET_ID.