Search Results rg_report_set_name_v

Overview

The RG_REPORT_SET_NAME_V view is a secure, denormalized projection over the Application Report Generator report set definitions stored in APPS.RG_REPORT_SETS. It resides in the APPS schema and is owned by that schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose the identifying and descriptive attributes of a report set—such as its name, description, and application context—while conditionally applying Oracle data security so that only authorized users can see report sets protected by a security flag.

Within the RG (Application Report Generator) module, a report set groups related report definitions for consolidated execution and submission, frequently in conjunction with Financial Statement Generator (FSG) reporting. The view therefore plays a role in both reporting configuration and integration, allowing forms, concurrent programs, and custom code to resolve a REPORT_SET_ID to a human-readable name and to determine whether the current user holds the privilege to use the set. The description on record indicates the object was created for a specific release context (documented as "10SC ONLY"), yet the view remains valid and deployed in the 12.1.1 and 12.2.2 schemas, and it continues to be referenced by name-based lookups throughout the RG/FSG stack.

Underlying Base Objects

The view is defined solely over the synonym RG_REPORT_SETS, which resolves to the base report set table in the APPS schema. No joins to other base tables are performed; instead, the view layers a scalar security evaluation on top of the underlying rows using two PL/SQL package calls:

• FND_DATA_SECURITY.CHECK_FUNCTION — invoked to evaluate whether the current user may access a given report set. The function is passed a group identifier, the object names GL_DAS_FSG_REPORT_SET_U and GL_DAS_FSG_REPORT_SET, the report set identifier as a character value, and the current user name from FND_GLOBAL.USER_NAME. It returns a flag that is decoded into the derived USE_PRIVILEGE column.
• FND_GLOBAL.USER_NAME — supplies the identity used by the data security check.
• RG_REPORT_SETS — the synonym supplying all projected columns (REPORT_SET_ID, NAME, DESCRIPTION, APPLICATION_ID, ID_FLEX_CODE, STRUCTURE_ID, and SECURITY_FLAG).

Because the security predicate is embedded in the SELECT list through a DECODE rather than a WHERE clause, rows are not physically filtered; access control is expressed as the computed USE_PRIVILEGE value. Note the ETRM metadata also lists FND_DATA_SECURITY (PACKAGE) and FND_GLOBAL (PACKAGE) as referenced objects, confirming these dependencies.

Key Columns

• REPORT_SET_ID — the primary identifier for the report set; the value most commonly used as a foreign key in RG configuration tables and as the search key referenced when users query by "report_set_id."
• NAME — the user-facing name of the report set.
• DESCRIPTION — free-text description of the report set's purpose.
• APPLICATION_ID — the application (product) to which the report set belongs, enabling filtering by module.
• ID_FLEX_CODE — the key flexfield code associated with the report set, relevant for FSG-style reporting structures.
• STRUCTURE_ID — the flexfield structure identifier that qualifies ID_FLEX_CODE.
• USE_PRIVILEGE — a derived flag (Y/N) indicating whether the current session's user has security access to the report set. It is computed by decoding SECURITY_FLAG: where the flag is N (or otherwise), the user is granted access; where it is Y, access depends on the outcome of FND_DATA_SECURITY.CHECK_FUNCTION.

Common Use Cases and Queries

The view is typically used to build name-based list-of-values queries, to validate security before submitting a report set, and to drive custom integrations that need report set names without re-implementing the security logic.

Resolving an identifier to a name and description:

• SELECT report_set_id, name, description, use_privilege FROM apps.rg_report_set_name_v WHERE report_set_id = :p_report_set_id;

Listing only report sets the current user is permitted to use:

• SELECT report_set_id, name FROM apps.rg_report_set_name_v WHERE use_privilege = 'Y' ORDER BY name;

Restricting by application and flexfield context for FSG-related integrations:

• SELECT name FROM apps.rg_report_set_name_v WHERE application_id = :p_app_id AND id_flex_code = :p_flex_code AND use_privilege = 'Y';

Because USE_PRIVILEGE is evaluated per session, queries should be issued in the context of the intended user; calling the view under a different FND_GLOBAL identity may yield different results.