Search Results modify_privilege




Overview
Explore in AI Chat

Overview

GL_AUTOREV_CRITERIA_SETS_V is a General Ledger (GL) data security view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the auto-reverse criteria sets defined in the GL_AUTOREV_CRITERIA_SETS base entity and augments each row with three runtime-computed privilege indicators: VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE. These indicators are produced by calling the FND_DATA_SECURITY.CHECK_FUNCTION API against the GL_DAS_AUTOREVERSE_SET data security object, comparing the requesting user against the grants established in the Data Access Set (DAS) security model.

The view plays a specific role in the EBS security and reporting layer rather than in transactional postings. Where the underlying table stores the definition of an auto-reverse criteria set (its name, description and descriptive flexfield context), this view answers the authorization question: can the current user see, use, or change the criteria set? Because the privilege columns are evaluated at query time via FND_GLOBAL.USER_NAME, the result set is user-context sensitive and must be queried from within a session that has an authenticated FND_GLOBAL context.

Underlying Base Objects

The view definition references the following documented underlying objects:

Each privilege expression is wrapped in DECODE logic. When SECURITY_FLAG is not 'Y' the view returns 'Y' unconditionally, meaning the criteria set is treated as unrestricted. Only when SECURITY_FLAG = 'Y' is the FND_DATA_SECURITY lookup actually performed, with a returned value of 'T' translated to 'Y' and all other outcomes to 'N'.

Key Columns

  • ROW_ID — the ROWID of the underlying base row, used by Oracle Forms for optimistic locking and direct row addressing.
  • CRITERIA_SET_ID — the unique surrogate key of the auto-reverse criteria set; the value passed into each data security check.
  • CRITERIA_SET_NAME / CRITERIA_SET_DESC — the user-facing identifier and description of the criteria set.
  • SECURITY_FLAG — controls whether DAS-based security is enforced for the row; 'Y' activates the privilege evaluation.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segment values attached to the criteria set.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit ("WHO") columns.
  • VIEW_PRIVILEGE — 'Y' if the current user may view the criteria set via the GL_DAS_AUTOREVERSE_SET_V data security object.
  • USE_PRIVILEGE — 'Y' if the user may apply or use the criteria set (GL_DAS_AUTOREVERSE_SET_U).
  • MODIFY_PRIVILEGE — 'Y' if the user may change the criteria set (GL_DAS_AUTOREVERSE_SET_M). This is the column typically targeted by searches such as "modify_privilege", since it governs whether a user is permitted to alter the auto-reverse criteria set definition.

Common Use Cases and Queries

The view is typically consumed by forms, concurrent programs and custom extensions that must render criteria sets according to the caller's data access set grants. A frequent pattern is filtering out rows the user cannot use or change. For example, to list every criteria set the current user may modify:

  • SELECT criteria_set_id, criteria_set_name, criteria_set_desc, modify_privilege FROM apps.gl_autorev_criteria_sets_v WHERE modify_privilege = 'Y';

To audit privileges across all criteria sets for the current session:

  • SELECT criteria_set_name, security_flag, view_privilege, use_privilege, modify_privilege FROM apps.gl_autorev_criteria_sets_v ORDER BY criteria_set_name;

Because the privilege columns depend on FND_GLOBAL context, queries issued from a plain SQL*Plus session without APPS initialization may return 'N' for all secured rows. Integrators should therefore invoke the view through the concurrent manager, an OA Framework page, or an explicitly initialized session to obtain accurate privilege results.