Search Results show_validation_status

Overview

APPS.GL_ALLOC_BATCHES_V is a security-enabled reporting view over the General Ledger allocation batch definition table. It exposes the header-level attributes of allocation batches — the containers that group allocation formulas, definitions, and generated journal entries — together with three computed privilege columns derived from Oracle EBS data security. The view is owned by APPS and is documented in ETRM for Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a base table, it is intended for read access in forms, reports, and integration queries, not for direct DML. Its distinguishing feature is the runtime evaluation of data security through FND_DATA_SECURITY and FND_GLOBAL, which makes the rows and privileges returned dependent on the responsibility and user context in which the query executes.

Underlying Base Objects

The view's sole underlying base object is GL_ALLOC_BATCHES, referenced through a synonym. GL_ALLOC_BATCHES stores the allocation batch header, including the batch name, chart of accounts, actual flag, security flag, descriptive text, and standard WHO audit columns. Four documented dependencies support the view: the GL_ALLOC_BATCHES synonym supplies the row data; FND_DATA_SECURITY is the package invoked via CHECK_FUNCTION to evaluate whether the current user may view, use, or modify a given batch; FND_GLOBAL supplies the current user name passed to the security check; and GL_LOOKUPS is referenced for lookup validation of flag values. The actual_flag column is the pivot on which the view's security logic turns: when the flag indicates a budget batch, the view evaluates the GL_DAS_MASSBUDGET family of data security objects, and for all other (actual) batches it evaluates the GL_DAS_MASSALLOCATION family. The '_V', '_U', and '_M' suffixes correspond to view, use, and modify privilege checks respectively.

Key Columns

• ROW_ID — the physical ROWID of the underlying GL_ALLOC_BATCHES row.
• ALLOCATION_BATCH_ID — primary key of the allocation batch.
• NAME — the user-defined batch name.
• CHART_OF_ACCOUNTS_ID — chart of accounts to which the batch belongs.
• ACTUAL_FLAG — indicates whether the batch is an actual or budget allocation; drives which data security object is evaluated ('B' selects the mass budget objects).
• SECURITY_FLAG — when 'Y', row-level data security is enforced; when not 'Y', privileges resolve to 'Y'.
• DESCRIPTION — free-text description of the batch.
• VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — computed 'Y'/'N' indicators from FND_DATA_SECURITY.CHECK_FUNCTION, resolving view, use, and modify rights for the current user, responsibility, and batch.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include listing allocation batches visible to a user, filtering batches by actual versus budget flag, and gating UI or report actions on the computed privilege columns. A standard query filters on the actual_flag value the user searched for:

• SELECT allocation_batch_id, name, actual_flag, security_flag, view_privilege, use_privilege, modify_privilege FROM apps.gl_allocation_batches_v WHERE actual_flag = 'A' ORDER BY name;
• SELECT allocation_batch_id, name FROM apps.gl_allocation_batches_v WHERE view_privilege = 'Y' AND chart_of_accounts_id = :coa_id;
• SELECT b.name, b.description FROM apps.gl_allocation_batches_v b WHERE b.modify_privilege = 'Y' AND b.actual_flag = 'B';

Because privileges are evaluated at query time using FND_GLOBAL.USER_NAME, results differ by session responsibility. Reports should always filter on the relevant privilege column rather than assuming unrestricted access.