Results for “security_flag”

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

Overview

The RG_REPORT_AXIS_SETS_LOV_V view is a secured list-of-values (LOV) presentation layer defined in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the RG – Application Report Generator product, the module responsible for the Financial Statement Generator (FSG) reporting framework and related report-building utilities. The view exposes row and column axis sets — the building blocks of FSG reports — together with dynamically computed privilege flags that govern whether the currently connected user may view, use, or modify each axis set.

The view is named with the _LOV_V suffix, indicating its primary purpose is to feed LOV windows and flexfield-style pickers within the Application Report Generator UI, rather than to serve as a general-purpose data source. When a user searches on axis_set_id, this view is typically the object supplying candidate values, because it combines descriptive attributes (name, description) with security evaluation in a single query.

Underlying Base Objects

The view is defined over the RG_REPORT_AXIS_SETS synonym, which resolves to the base axis-set table holding row sets and column sets. Two PL/SQL packages are referenced in the SELECT list to enforce function security:

• FND_DATA_SECURITY.CHECK_FUNCTION — evaluates whether the current user holds the appropriate function privilege for a given axis set, returning a flag consumed by the DECODE logic.
• FND_GLOBAL.USER_NAME — supplies the current user identity passed into the security check.

Because the view text references ROWID as ROW_ID and applies DECODE-based privilege derivation, it is a non-updatable view intended strictly for read access. No joins to other tables are present; the security model is applied entirely through the embedded function calls.

Key Columns

• ROW_ID — the ROWID of the underlying base row, used as a unique identifier in LOV navigation.
• NAME and DESCRIPTION — the user-facing label and long description of the axis set.
• APPLICATION_ID — owning application, distinguishing FSG content by product registration.
• AXIS_SET_TYPE — discriminates between row sets ('R') and column sets, and drives which security function name is passed to CHECK_FUNCTION.
• AXIS_SET_ID — the primary surrogate key for the axis set; this is the value commonly filtered or returned when users query on axis_set_id.
• SECURITY_FLAG — indicates whether the axis set is secured; values other than 'Y' bypass the dynamic check.
• STRUCTURE_ID and ID_FLEX_CODE — identify the accounting flexfield structure associated with the axis set.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — computed flags ('Y' or 'N') reflecting the current user's rights, derived from the GL_DAS_FSG_ROW_SET* and GL_DAS_FSG_COLUMN_SET* function names.

Common Use Cases and Queries

The view is most often queried to populate an LOV or to verify that a user can access a specific axis set before a report is launched. A typical lookup by identifier might read:

• SELECT axis_set_id, name, axis_set_type FROM rg_report_axis_sets_lov_v WHERE axis_set_id = :p_id;
• SELECT axis_set_id, name FROM rg_report_axis_sets_lov_v WHERE axis_set_type = 'R' AND view_privilege = 'Y'; — returns only row sets the user may view.
• SELECT name, modify_privilege FROM rg_report_axis_sets_lov_v WHERE axis_set_id IN (101, 102); — checks modification rights for a set of candidate sets.

Consultants commonly use the view during FSG troubleshooting to confirm that a missing axis set is excluded by privilege logic rather than absent from the base table. Developers should avoid basing concurrent programs or interfaces on this view, since its privilege columns depend on the runtime user session and are unsuitable for batch, multi-user processing.