Search Results column_set




Overview
Explore in AI Chat

Overview

The APPS.RG_REPORT_NAME_V view is a reporting and integration construct within the Oracle Application Report Generator (RG) module, the technology stack underpinning Financial Statement Generator (FSG) reports in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated, denormalized projection of report definitions stored in RG_REPORTS, enriched with descriptive names for the axis sets, content sets, display sets, and row orders that a report references. Because raw FSG report metadata is distributed across multiple normalized tables and identified only by numeric IDs, RG_REPORT_NAME_V provides a single queryable surface that resolves those IDs into human-readable values and computes a runtime privilege indicator.

The view carries a status of VALID in the APPS schema and is owned by the Application Object Library. It is commonly consumed by concurrent programs, custom reporting extracts, diagnostic scripts, and integration interfaces that must enumerate or validate FSG report definitions without traversing the underlying schema directly.

Underlying Base Objects

RG_REPORT_NAME_V is defined over the following documented base objects:

  • RG_REPORTS (synonym to the RG_REPORTS table) — the primary driving table, supplying application, report identity, title, description, unit of measure, and all axis-set foreign keys.
  • RG_REPORT_AXIS_SETS — joined twice, once as the column set (AXIS_SET_TYPE = 'C') and once as the row set (AXIS_SET_TYPE = 'R').
  • RG_REPORT_CONTENT_SETS, RG_REPORT_DISPLAY_SETS, and RG_ROW_ORDERS — outer-joined to resolve optional content, display, and row ordering references.
  • RG_LOOKUPS — used to filter out ad hoc reports whose names carry the configured FSG ad hoc prefix.
  • FND_DATA_SECURITY (package) and FND_GLOBAL (package) — invoked in the SELECT list to evaluate the USE_PRIVILEGE flag against the caller's data security profile.

The joins on content set, display set, and row order are outer joins, so reports lacking these optional attributes remain visible. The column and row set joins are inner joins, reflecting that every valid report must reference both.

Key Columns

Common Use Cases and Queries

Typical uses include auditing report definitions, extracting FSG metadata for migration, and enforcing data security at query time. The following examples illustrate practical access patterns.

  • List all reports with their resolved axis set names:

SELECT report_id, name, report_title, column_set, row_set, unit_of_measure_id FROM apps.rg_report_name_v ORDER BY name;

  • Retrieve reports only where the current user holds execution privilege:

SELECT name, report_title, use_privilege FROM apps.rg_report_name_v WHERE use_privilege = 'Y';

  • Locate a specific unit of measure assignment:

SELECT report_id, name, report_title FROM apps.rg_report_name_v WHERE unit_of_measure_id = :p_uom_id;

Because USE_PRIVILEGE is evaluated against FND_GLOBAL.USER_NAME at execution time, queries should be run in a session where the application context is correctly initialized. Ad hoc reports are automatically excluded by the RG_LOOKUPS filter, ensuring only named FSG reports are returned.