Search Results gl_alloc_batches_v




Overview
Explore in AI Chat

Overview

GL_ALLOC_BATCHES_V is an APPS-owned reporting and integration view in the Oracle General Ledger (GL) module, documented as "10SC ONLY" in the ETRM reference for Oracle EBS 12.1.1 and 12.2.2. It presents allocation batch header information from the GL_ALLOC_BATCHES base table, augmented with descriptive lookup text and function-security-derived privileges. Its principal purpose is to expose mass allocation and mass budget batch definitions together with their validation state, allowing reports, concurrent programs, and external integrations to retrieve batch metadata without directly querying the underlying transactional table.

The view is particularly relevant to searches involving validation_request_id, since it exposes both VALIDATION_REQUEST_ID and VALIDATION_STATUS columns, and derives the human-readable status description by joining to the GL_LOOKUPS view on lookup type VALIDATION_STATUS. This makes the view the natural access point for determining which validation concurrent request governs a given allocation batch and how that request resolved.

Underlying Base Objects

The view is defined over four documented objects:

The security logic is conditional: when SECURITY_FLAG is 'Y', the view calls CHECK_FUNCTION against menu function names that switch on ACTUAL_FLAG. For actual ('A') balances the functions are GL_DAS_MASSALLOCATION(_V/_U/_M), and for budget ('B') balances they are GL_DAS_MASSBUDGET(_V/_U/_M). When SECURITY_FLAG is 'T', the privilege is forced to 'Y'; otherwise it evaluates to 'N'. Where FND_DATA_SECURITY returns NULL, the privilege resolves to NULL.

Key Columns

  • ROW_ID — the base table ROWID, useful for direct row identification.
  • ALLOCATION_BATCH_ID — primary identifier of the allocation batch, also used as the security check value.
  • NAME, DESCRIPTION — batch name and free-text description.
  • CHART_OF_ACCOUNTS_ID — chart of accounts to which the batch belongs.
  • ACTUAL_FLAG — distinguishes actual ('A') from budget ('B') batches and drives which data security functions are applied.
  • SECURITY_FLAG — controls whether data security is enforced ('Y'), bypassed ('T'), or not applicable.
  • VALIDATION_REQUEST_ID — the concurrent request identifier for the batch validation run.
  • VALIDATION_STATUS — the stored code for the batch's validation state.
  • SHOW_VALIDATION_STATUS — the GL_LOOKUPS meaning that decodes VALIDATION_STATUS.
  • VIEW_PRIVILEGE, USE_PRIVILEGE, MODIFY_PRIVILEGE — security-derived flags indicating whether the current user may see, use, or modify the batch.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

A frequent requirement is correlating a batch with its validation concurrent request, which is precisely why the view contains VALIDATION_REQUEST_ID:

SELECT allocation_batch_id, name, validation_request_id, validation_status, show_validation_status FROM apps.gl_alloc_batches_v WHERE validation_request_id = :request_id;

Listing batches whose validation is still pending or failed, with the lookup description resolved, is equally straightforward:

SELECT allocation_batch_id, name, show_validation_status, view_privilege FROM apps.gl_alloc_batches_v WHERE actual_flag = 'A' AND security_flag = 'Y' ORDER BY creation_date DESC;

Because the view applies FND_DATA_SECURITY, callers invoking it as APPS automatically receive only rows the current user is entitled to view or modify. Integrations should therefore prefer GL_ALLOC_BATCHES_V over the base synonym wherever the lookup meaning and privilege flags are needed, while noting the documented "10SC ONLY" restriction governing its intended deployment scope.