Search Results gl_alloc_batches




Overview
Explore in AI Chat

Overview

The GL_ALLOC_BATCHES table is a core data object within the Oracle E-Business Suite General Ledger (GL) module. It serves as the master repository for MassAllocation and MassBudget batch definitions. These batches are critical tools for automating the periodic distribution of amounts, such as overhead or budget figures, across multiple accounting flexfield combinations. The table stores the high-level batch configuration, including its name, status, and associated chart of accounts, enabling users to define, validate, and submit allocation processes efficiently. Its role is central to the allocation engine, acting as the parent container for the specific allocation formulas and tracking the execution history.

Key Information Stored

The table's primary key is the system-generated ALLOCATION_BATCH_ID, which uniquely identifies each batch. A unique key constraint also exists on the combination of NAME and CHART_OF_ACCOUNTS_ID, ensuring batch names are unique within a given accounting structure. Other significant columns include STATUS, which indicates whether the batch is defined, validated, or processed; VALIDATION_REQUEST_ID, which stores the identifier from the FND_CONCURRENT_REQUESTS table for the concurrent request that validated the batch's formulas; and LAST_UPDATE_DATE/LAST_UPDATED_BY for audit purposes. The CHART_OF_ACCOUNTS_ID links the batch to its specific accounting flexfield structure.

Common Use Cases and Queries

A primary use case is generating reports on batch status or troubleshooting allocation runs. Administrators often query this table to list all batches for a ledger or to find batches pending validation. Common SQL patterns include joining to FND_CONCURRENT_REQUESTS to get validation request details or to GL_ALLOC_FORMULAS to review the underlying calculation rules. For example, to find batches that failed validation, one might query the STATUS column and join on VALIDATION_REQUEST_ID to examine the concurrent request outcome. Another typical query retrieves all batches for a specific chart of accounts to manage or archive allocation definitions.

Related Objects

GL_ALLOC_BATCHES has defined foreign key relationships with several key General Ledger tables, forming the core of the allocation architecture. The documented relationships are:

  • GL_ALLOC_FORMULAS: Child table. GL_ALLOC_FORMULAS.ALLOCATION_BATCH_ID references GL_ALLOC_BATCHES.ALLOCATION_BATCH_ID. This stores the individual allocation rules within a batch.
  • GL_ALLOC_HISTORY: Child table. GL_ALLOC_HISTORY.ALLOCATION_BATCH_ID references GL_ALLOC_BATCHES.ALLOCATION_BATCH_ID. This logs the execution results of each batch run.
  • GL_AUTO_ALLOC_BATCHES: Child table. GL_AUTO_ALLOC_BATCHES.BATCH_ID references GL_ALLOC_BATCHES.ALLOCATION_BATCH_ID. This links to the setup for automatically scheduled allocation batches.
  • FND_CONCURRENT_REQUESTS: Parent table. GL_ALLOC_BATCHES.VALIDATION_REQUEST_ID references FND_CONCURRENT_REQUESTS.REQUEST_ID. This provides the status and details of the concurrent process used to validate the batch.
These relationships illustrate the table's position as a central hub for allocation processing data.