Search Results rg_reports

Overview

The RG_REPORTS table is the central repository for report definitions within the Application Report Generator (RG) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. This module is a core financial reporting engine used to define, generate, and manage complex financial statements and operational reports. The table serves as the master definition table, storing the essential metadata that defines a report's structure, layout, and data sources. Every report created within the RG module is represented by a single record in this table, making it fundamental to the reporting infrastructure.

Key Information Stored

The table's structure captures the complete blueprint of a report. Its primary key is REPORT_ID, a unique system-generated identifier. The composite unique key on NAME and APPLICATION_ID ensures report names are unique within a specific Oracle application. Critical foreign key columns link the report definition to its constituent components, defining its axes, content, and display properties. These include ROW_SET_ID and COLUMN_SET_ID (linking to RG_REPORT_AXIS_SETS for the report matrix), CONTENT_SET_ID (linking to RG_REPORT_CONTENT_SETS for the data values), and REPORT_DISPLAY_SET_ID (for formatting). Additional columns manage structural elements like ROW_ORDER_ID and references to key flexfield structures (APPLICATION_ID, ID_FLEX_CODE_11I, STRUCTURE_ID) for segment-based reporting.

Common Use Cases and Queries

This table is primarily accessed for report administration, auditing, and troubleshooting. Common operational scenarios include identifying all reports within a module, diagnosing report execution issues by examining their definition, and generating inventories of reports. A typical query retrieves a report's core definition and its linked components:

• Report Inventory by Application: SELECT report_id, name, description FROM rg.rg_reports WHERE application_id = &app_id ORDER BY name;
• Report Structure Analysis: SELECT r.name, a1.name row_set, a2.name column_set, c.name content_set FROM rg.rg_reports r, rg.rg_report_axis_sets a1, rg.rg_report_axis_sets a2, rg.rg_report_content_sets c WHERE r.row_set_id = a1.axis_set_id AND r.column_set_id = a2.axis_set_id AND r.content_set_id = c.content_set_id;
• Linking to Report Runs: Queries often join RG_REPORTS to RG_REPORT_REQUESTS to analyze submission history for a specific report definition.

Related Objects

The RG_REPORTS table has extensive relationships within the RG schema, acting as a hub for report configuration. Key related objects, as defined by its foreign keys, include:

• RG_REPORT_AXIS_SETS: Referenced twice for ROW_SET_ID and COLUMN_SET_ID, defining the rows and columns of the report matrix.
• RG_REPORT_CONTENT_SETS: Referenced by CONTENT_SET_ID, defining the measures or data values to be populated in the report cells.
• RG_REPORT_DISPLAY_SETS: Defines formatting and display properties for the report output.
• RG_REPORT_REQUESTS & RG_REPORT_SET_REQ_DETAILS: Child tables that store each instance of a report submission or run, linked via REPORT_ID.
• RG_ROW_ORDERS: Defines the sorting order for report rows.
• FND_ID_FLEX_STRUCTURES & FND_CURRENCIES: Reference tables for flexfield structures and currency units, respectively.