Results for “gl_alloc_batches”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GL_ALLOC_BATCHES is a General Ledger table that stores the definition and control records for MassAllocation and MassBudget batches in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row represents one allocation or budget batch header, holding the accounting flexfield context, validation state, and audit information required for the batch to be validated and executed through concurrent processing. MassAllocations distribute balances across accounts according to defined formulas, while MassBudget batches create budget journal entries using the same allocation engine. GL_ALLOC_BATCHES therefore acts as the parent record against which formulas, run history, and auto-allocation definitions are organized.
Within a Data Vault modeling context, the primary key and foreign key structure suggest this object behaves as a hub-leaning entity: the surrogate ALLOCATION_BATCH_ID is a stable, non-business identifier, and the table serves as the anchor to which descriptive and transactional satellites (formulas, history, auto-allocation rules) attach. This classification is a heuristic derived from the FK topology and should be treated as a modeling suggestion rather than a documented Oracle designation.
Key Information Stored
The table contains 13 documented columns. The most significant are:
- ALLOCATION_BATCH_ID — Surrogate primary key, uniquely identifying each allocation batch record via GL_ALLOC_BATCHES_PK and the unique index GL_ALLOC_BATCHES_U1.
- NAME — The user-assigned batch name. Combined with CHART_OF_ACCOUNTS_ID, it forms the business-key candidate enforced by unique index GL_ALLOC_BATCHES_U2.
- CHART_OF_ACCOUNTS_ID — Identifies the chart of accounts the batch belongs to; part of the composite unique business key.
- VALIDATION_STATUS — Tracks whether the batch has passed validation prior to execution.
- ACTUAL_FLAG — Distinguishes the balance type (for example, actual versus budget) that the batch operates against.
- VALIDATION_REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS, linking the batch to its validation concurrent program run.
- DESCRIPTION — Free-text description of the batch.
- SECURITY_FLAG — Indicates whether definition access security applies to the batch.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking who created and last modified the record and when.
Common Use Cases and Queries
Typical scenarios include verifying validation status before submitting a batch, listing all batches for a given chart of accounts, and reconciling allocation output against run history. A representative query joins the batch header to its formulas:
SELECT b.name, b.validation_status, b.actual_flag FROM gl.gl_alloc_batches b WHERE b.chart_of_accounts_id = :coa_id;SELECT b.name, f.* FROM gl.gl_alloc_batches b, gl.gl_alloc_formulas f WHERE b.allocation_batch_id = f.allocation_batch_id;SELECT b.name, r.request_id, r.phase_code FROM gl.gl_alloc_batches b, fnd_concurrent_requests r WHERE b.validation_request_id = r.request_id;
Reporting use cases include audit trails of batch creation, monitoring of batches awaiting validation, and impact analysis before running MassAllocation or MassBudget processes.
Related Objects
GL_ALLOC_BATCHES participates in several documented relationships:
- GL_ALLOC_FORMULAS — Child table joined on ALLOCATION_BATCH_ID; holds the formula lines applied by each batch.
- GL_ALLOC_HISTORY — Child table joined on ALLOCATION_BATCH_ID; stores past execution results.
- GL_AUTO_ALLOC_BATCHES — Child table joined on BATCH_ID; links batches to automatic allocation definitions.
- FND_CONCURRENT_REQUESTS — Parent lookup joined on VALIDATION_REQUEST_ID for validation run status.
- GL_MGT_SEG_UPGRADE_H — Referenced by CHART_OF_ACCOUNTS_ID in the documented FK structure.
These dependencies confirm GL_ALLOC_BATCHES as the central parent object for allocation definitions within the General Ledger module.
-
MassAllocations and MassBudget batches
-
MassAllocations and MassBudget batches
-
TABLE: GL.GL_ALLOC_BATCHES 12.1.1
-
TABLE: GL.GL_ALLOC_BATCHES 12.2.2
-
VIEW: GL.GL_ALLOC_BATCHES# 12.2.2
-
View: GL_ALLOC_BATCHES_LOV_V 12.1.1
10SC ONLY
APPS.GL_ALLOC_BATCHES_LOV_V·↳ FND_DATA_SECURITY·↳ FND_GLOBAL·↳ GL_ALLOC_BATCHES·Explore GL module →
-
View: GL_ALLOC_BATCHES_LOV_V 12.2.2
10SC ONLY
APPS.GL_ALLOC_BATCHES_LOV_V·↳ FND_DATA_SECURITY·↳ FND_GLOBAL·↳ GL_ALLOC_BATCHES·Explore GL module →
-
View: GL_ALLOC_BATCHES_V 12.1.1
10SC ONLY
APPS.GL_ALLOC_BATCHES_V·↳ FND_DATA_SECURITY·↳ FND_GLOBAL·↳ GL_ALLOC_BATCHES·Explore GL module →
-
MassAllocations and MassBudget formulas
-
View: GL_ALLOC_BATCHES_V 12.2.2
10SC ONLY
APPS.GL_ALLOC_BATCHES_V·↳ FND_DATA_SECURITY·↳ FND_GLOBAL·↳ GL_ALLOC_BATCHES·Explore GL module →
-
APPS.GL_AUTO_ALLOC_BATCH_HISTORY_V·↳ GL_ALLOC_BATCHES·↳ GL_AUTO_ALLOC_BATCH_HISTORY·↳ GL_AUTO_ALLOC_VW_PKG·Explore GL module →
-
APPS.GL_AUTO_ALLOC_BATCH_HISTORY_V·↳ GL_ALLOC_BATCHES·↳ GL_AUTO_ALLOC_BATCH_HISTORY·↳ GL_AUTO_ALLOC_VW_PKG·Explore GL module →
-
MassAllocations and MassBudget formulas
-
10SC ONLY
Not implemented in this database·Explore GL module →
-
VIEW: GL.GL_ALLOC_BATCHES# 12.2.2
-
10SC ONLY
Not implemented in this database·Explore GL module →
-
History of MassAllocation and MassBudget runs
-
History of MassAllocation and MassBudget runs