Search Results rg_report_requests_v




Overview
Explore in AI Chat

Overview

RG_REPORT_REQUESTS_V is an Application Report Generator (RG) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The Application Report Generator is the historical predecessor of the Financial Statement Generator (FSG) in Oracle General Ledger. Its RG_% tables store the definitions and runtime requests for report sets, including row sets, column sets, content sets, row orders, and display sets. RG_REPORT_REQUESTS_V exposes a denormalized, security-aware projection over submitted report requests joined to their owning report definitions and the associated RG axis, content, order, and display set components.

Functionally, the view serves two purposes. First, it presents a flattened reporting structure in which request-level overrides and report-definition defaults are both visible, which is essential for troubleshooting how a specific report execution obtained its parameters. Second, it enforces FSG-style data security by invoking FND_DATA_SECURITY.CHECK_FUNCTION for reports whose SECURITY_FLAG is set to 'Y', exposing the result in the USE_PRIVILEGE column. The view is therefore relevant to both reporting and integration scenarios that need to programmatically read RG report request metadata while respecting application-level privilege checks.

Underlying Base Objects

The view is defined over the synonyms RG_REPORTS, RG_REPORT_REQUESTS, RG_REPORT_AXIS_SETS, RG_REPORT_CONTENT_SETS, RG_REPORT_DISPLAY_SETS, and RG_ROW_ORDERS. These resolve to the corresponding APPS base tables in the RG schema. The primary driving table is RG_REPORT_REQUESTS (aliased RQ), which is outer-joined in spirit to RG_REPORTS (RP) so that each request inherits report-level defaults such as ROUNDING_OPTION, SEGMENT_OVERRIDE, and OVERRIDE_ALC_LEDGER_CURRENCY.

Two database packages are referenced in the SELECT list: FND_GLOBAL for the current user name and FND_DATA_SECURITY for the privilege function. Four additional synonym-based objects supply descriptive names for the axis sets used as row sets and column sets, the content, order, and display sets. Both the request (RQ) and report (RP) sides expose the same set of override attributes, allowing a query to distinguish a request-time override from a report-definition default.

Key Columns

Common Use Cases and Queries

Typical use cases include auditing submitted RG report requests, verifying which currency and ledger a request resolved to, and joining to concurrent manager views to determine request status. A representative query filtering for a specific ledger currency follows:

SELECT report_request_id, report_name, period_name,
       ledger_id, alc_ledger_currency,
       override_alc_ledger_currency, use_privilege
FROM   apps.rg_report_requests_v
WHERE  alc_ledger_currency = :p_currency
  AND  use_privilege = 'Y';

Queries should generally filter on USE_PRIVILEGE = 'Y' when the view is consumed by a user-facing integration, since rows with 'N' represent report definitions the current user is not entitled to view. Note that the view text is complex and references package functions, so it should be treated as read-only and not used as a target of DML.