Search Results gl_das_autoreverse_set_u

Overview

APPS.GL_AUTOREV_CRITERIA_SETS_V is a data-security-enabled view in the Oracle E-Business Suite General Ledger module. It exposes the definition records of Automatic Reversal Criteria Sets — the configuration objects that determine how journal entries flagged for automatic reversal are reversed (by reversal period, reversal method, and associated criteria). The view is central to the "GL_DAS_AUTOREVERSE_SET" data access set / security object, which governs which users may view, use, or modify a given criteria set.

Unlike the underlying base table GL_AUTOREV_CRITERIA_SETS, this view augments each row with three computed privilege columns — VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE — derived at query time via calls to the FND_DATA_SECURITY package. This makes the view the appropriate access point for any form, concurrent program, or custom report that must respect Oracle's function-based data security semantics. It is exposed under the APPS schema and is therefore callable from any standard EBS session where the APPS synonym is resolvable.

Underlying Base Objects

The view is defined over a single base object, GL_AUTOREV_CRITERIA_SETS (aliased GLAC), which in a standard EBS installation is exposed through an APPS-owned synonym over the GL schema table. The view is further dependent on two PL/SQL packages referenced in its SELECT list:

• FND_DATA_SECURITY — invoked three times, once per privilege column, to evaluate whether the current user (FND_GLOBAL.USER_NAME) holds view, use, or modify rights on the criteria set.
• FND_GLOBAL — supplies the USER_NAME value passed into the security check.

Because the privilege logic is evaluated row-by-row inside a DECODE, the security_flag on the base record acts as a gate: if SECURITY_FLAG is not 'Y', all three privilege columns resolve to 'Y' unconditionally. Only when security is enabled does the function call determine the actual privilege.

Key Columns

• ROW_ID — the ROWID of the underlying base row; used for row-level operations.
• CRITERIA_SET_ID — the primary key of the automatic reversal criteria set.
• CRITERIA_SET_NAME / CRITERIA_SET_DESC — the user-facing identification and description.
• SECURITY_FLAG — indicates whether the criteria set participates in function-based security.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — computed columns returning 'Y' or 'N'; the values reflect rights granted through the GL_DAS_AUTOREVERSE_SET_V, GL_DAS_AUTOREVERSE_SET_U, and GL_DAS_AUTOREVERSE_SET_M security functions respectively.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard auditing columns inherited from the base table.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for extending the object.

Common Use Cases and Queries

The primary use case is driving LOVs, forms, and reports that must only present criteria sets the current user is permitted to see or act upon. A typical query filters on the privilege columns rather than the raw table:

SELECT criteria_set_id, criteria_set_name, criteria_set_desc
FROM apps.gl_autorev_criteria_sets_v
WHERE view_privilege = 'Y'
ORDER BY criteria_set_name;

To enforce use rather than view rights — for example, when populating a reversal selection list — the predicate would be WHERE use_privilege = 'Y'. A diagnostic query to audit security coverage across all criteria sets might select SECURITY_FLAG alongside the three privilege columns to confirm that secure sets are returning the expected grant values for the logged-in user. Because the privilege columns are computed through FND_DATA_SECURITY, avoid wrapping the view in aggregate or set-based operations that would force repeated evaluation; instead, materialize or cache the filtered set when performance is a concern.