Search Results rg_report_requests




Overview
Explore in AI Chat

Overview

The RG_REPORT_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) Application Report Generator (RG) module. Its primary function is to track report execution requests and manage the assignment of individual reports to report sets. A report set is a collection of reports that can be submitted as a single concurrent request. This table acts as the central junction, linking the definition of a report set to its constituent reports and recording the runtime details of each report's execution. It is critical for the operational workflow of generating and managing complex financial and operational reports within EBS versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores metadata and runtime parameters for each report request. Its primary key is REPORT_REQUEST_ID, which uniquely identifies each request instance. The table maintains the structural relationship between a report set and its reports via the foreign key columns REPORT_SET_ID and REPORT_ID. Key operational data includes the CONCURRENT_REQUEST_ID, which links to the standard EBS concurrent request tracking system (FND_CONCURRENT_REQUESTS). Other significant columns define the reporting context, such as LEDGER_ID for the financial ledger, APPLICATION_ID and ID_FLEX_CODE_11I for the key flexfield structure, and UNIT_OF_MEASURE_ID_11I for the currency. The table also references configuration objects like CONTENT_SET_ID, ROW_ORDER_ID, and REPORT_DISPLAY_SET_ID, which control the data content, row sequencing, and display formatting of the generated report output.

Common Use Cases and Queries

A primary use case is diagnosing the status and history of report set submissions. System administrators or functional users can query this table to determine which reports were part of a specific run, their individual completion statuses, and their associated concurrent request IDs for log file review. A common diagnostic query would join RG_REPORT_REQUESTS with FND_CONCURRENT_REQUESTS and RG_REPORTS. Another critical scenario involves auditing and impact analysis before modifying or deleting a report definition; queries against this table can identify all report sets that incorporate a specific report. Sample SQL to find details for a specific report set execution would be:

  • SELECT rgrr.report_request_id, rgrr.concurrent_request_id, rgr.report_name, fcr.request_id, fcr.status_code FROM rg_report_requests rgrr JOIN rg_reports rgr ON rgrr.report_id = rgr.report_id JOIN fnd_concurrent_requests fcr ON rgrr.concurrent_request_id = fcr.request_id WHERE rgrr.report_set_id = :p_report_set_id ORDER BY rgrr.report_request_id;

Related Objects

The RG_REPORT_REQUESTS table has extensive foreign key relationships, highlighting its central role in the Report Generator schema. Key documented relationships include:

  • RG_REPORTS via REPORT_ID: References the master definition of the report.
  • RG_REPORT_SETS via REPORT_SET_ID: References the parent report set definition.
  • FND_CONCURRENT_REQUESTS via CONCURRENT_REQUEST_ID: Links to the EBS concurrent manager execution log.
  • GL_LEDGERS via LEDGER_ID: Specifies the primary ledger for the report data.
  • FND_ID_FLEX_STRUCTURES via (APPLICATION_ID, ID_FLEX_CODE_11I, STRUCTURE_ID): Defines the key flexfield structure used.
  • FND_CURRENCIES via UNIT_OF_MEASURE_ID_11I: Specifies the reporting currency.
  • RG_REPORT_CONTENT_SETS via CONTENT_SET_ID: References the data content rules.
  • RG_ROW_ORDERS via ROW_ORDER_ID: References the row ordering rules.
  • RG_REPORT_DISPLAY_SETS via REPORT_DISPLAY_SET_ID: References the display formatting rules.