Results for “rg_report_display_groups_v”

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

Overview

RG_REPORT_DISPLAY_GROUPS_V is an Oracle E-Business Suite view owned by the APPS schema and registered under the RG (Application Report Generator) product. Its documented description is "10SC ONLY," indicating that the view was introduced to support a specific release or localization context rather than serving as a general-purpose, cross-module reporting interface. Within the Oracle EBS 12.1.1 and 12.2.2 data model, it functions as a secured presentation layer over report display group definitions. A report display group defines the pairing of a row set with a column set, together with a sequencing window (the FROM_SEQUENCE to TO_SEQUENCE range) that governs how report content is laid out. This view enriches the raw display-group record with resolved row set and column set names and with runtime data-security privileges, so that downstream report-generation logic and inquiry screens can determine both the structure of a display group and whether the current user is authorized to use its component axis sets.

Underlying Base Objects

The view is defined over two base tables and references two packages:

• RG_REPORT_DISPLAY_GROUPS (referenced through a synonym) — the driving table, aliased DG. It supplies the display group identity, naming, sequencing range, and the standard EBS WHO columns and descriptive flexfield attributes.
• RG_REPORT_AXIS_SETS (referenced through a synonym) — joined twice, as RS for the row set and CSET for the column set. These joins resolve ROW_SET_ID and COLUMN_SET_ID to human-readable names.
• FND_DATA_SECURITY (package) — invoked through CHECK_FUNCTION to evaluate user privileges against the GL_DAS_FSG_ROW_SET_U and GL_DAS_FSG_COLUMN_SET_U security functions.
• FND_GLOBAL (package) — supplies USER_NAME to the security check.

Both axis-set joins are outer joins ((+)), meaning a display group is returned even when its row set or column set is null or unresolvable. The row-set and column-set security checks are gated on each axis set's SECURITY_FLAG; when the flag is not 'Y', the corresponding privilege column resolves to 'Y' by default.

Key Columns

• REPORT_DISPLAY_GROUP_ID — primary identifier of the display group.
• NAME and DESCRIPTION — user-facing labels for the group.
• ROW_SET_ID, ROW_SET — the row axis set identifier and its resolved name.
• COLUMN_SET_ID, COLUMN_SET — the column axis set identifier and its resolved name.
• FROM_SEQUENCE and TO_SEQUENCE — the sequence window bounding the report lines or columns included; the search term to_sequence maps directly to the TO_SEQUENCE column, the upper bound of this range.
• ROW_SET_USE_PRIVILEGE and COL_SET_USE_PRIVILEGE — decoded values ('Y' or 'N') indicating whether the current user may use the associated row set and column set, derived from FND_DATA_SECURITY.CHECK_FUNCTION.
• ROW_ID — the base table row identifier, exposed for updatable or block-based forms.
• WHO and DFF columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CONTEXT, ATTRIBUTE1 through ATTRIBUTE15) — standard audit and descriptive flexfield support.

Common Use Cases and Queries

The view is typically queried to list display group definitions, to inspect the sequencing window of a group, or to verify data-security privileges before rendering a report. A representative query lists the group structure with resolved axis-set names and sequence bounds:

• SELECT report_display_group_id, name, row_set, column_set, from_sequence, to_sequence FROM rg_report_display_groups_v;
• To locate groups covering a specific upper sequence bound: SELECT name, from_sequence, to_sequence FROM rg_report_display_groups_v WHERE to_sequence = :p_to_sequence;
• To filter only groups the current user is privileged to run: SELECT name, row_set, column_set FROM rg_report_display_groups_v WHERE row_set_use_privilege = 'Y' AND col_set_use_privilege = 'Y';

Because the privilege columns depend on FND_GLOBAL.USER_NAME and FND_DATA_SECURITY.CHECK_FUNCTION, results are session- and responsibility-sensitive. Queries executed outside a properly initialized EBS session may return unpredictable privilege values; such checks should therefore be made from within the application or a correctly initialized database session.