Search Results report_title




Overview
Explore in AI Chat

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

Overview

RG_REPORTS is the master definition table for the Application Report Generator (product code RG) in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the RG schema and stores one row per report definition, serving as the central hub that ties together the column set, row set, content set, display set, row order, and parameter set components that together describe how a report is laid out, calculated, and rendered. Because RG drives the FSG-style financial reporting engine used across General Ledger and related products, RG_REPORTS is effectively the configuration backbone for user-defined reports: each record captures the report name, its owning application, its title, its output and rounding behavior, and the various axis and content structures referenced by foreign key.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table is dense with descriptive and configuration attributes (rounding option, output option, minimum display level, security flag) rather than representing a pure many-to-many link between two hubs. It can therefore be modeled as a satellite attached to a report hub keyed on REPORT_ID, with the RG_* set tables acting as referenced hubs or links depending on how the reporting components are themselves decomposed.

Key Information Stored

The surrogate primary key is REPORT_ID, enforced by RG_REPORTS_PK. Two unique indexes define business-key candidates: RG_REPORTS_U1 on REPORT_ID and RG_REPORTS_U2 on the combination of NAME and APPLICATION_ID, meaning a report name must be unique within its owning application.

Among the 45 documented columns, the most significant include:

Common Use Cases and Queries

Typical use cases include auditing which reports reference a given row set or column set, listing all reports for an application, and resolving the full report definition for a run request. A simple lookup by business key:

  • SELECT report_id, name, report_title FROM rg_reports WHERE name = :p_name AND application_id = :p_app;
  • Find reports sharing a row set: SELECT r.name, r.report_id FROM rg_reports r WHERE r.row_set_id = :p_row_set;
  • Trace requests back to definitions: SELECT rq.request_id, r.name FROM rg_report_requests rq, rg_reports r WHERE rq.report_id = r.report_id AND r.name = :p_name;
  • Identify reports lacking a display set or parameter set for cleanup prior to upgrade.

Because REPORT_ID is inherited by RG_REPORT_REQUESTS and RG_REPORT_SET_REQ_DETAILS, RG_REPORTS is also the anchor for reconciling submitted versus defined reports and for impact analysis when a shared set is modified.

Related Objects

The following relationships are documented and are the most significant for navigation: