Search Results gl_auto_alloc_batches




Overview
Explore in AI Chat

Overview

The GL_AUTO_ALLOC_BATCHES table is a core repository table within the Oracle E-Business Suite General Ledger module. Its primary function is to manage the assignment of specific batch processes to an allocation set. An allocation set is a configuration entity used to group and execute multiple allocation rules or journal batches in a defined sequence. This table acts as the junction, linking allocation sets (GL_AUTO_ALLOC_SETS) to the individual batches from various source processes. Its role is critical for automating and streamlining complex periodic accounting tasks, such as allocations, recurring journal generation, and budget/encumbrance processing, by enabling their coordinated execution.

Key Information Stored

The table stores the essential foreign key relationships that define these assignments. Its structure is defined by a composite primary key consisting of three columns: ALLOCATION_SET_ID, BATCH_ID, and BATCH_TYPE_CODE. The ALLOCATION_SET_ID links to the parent allocation set. The BATCH_ID holds the unique identifier of the specific batch being assigned. The BATCH_TYPE_CODE is a critical column that determines the source module and type of the batch, which dictates which foreign key relationship is active. Based on the provided metadata, valid batch types include MassAllocation, Mass Budgets, Mass Encumbrances, Recurring Journals, or Projects batches. The table's foreign keys enforce integrity by linking BATCH_ID to GL_ALLOC_BATCHES for allocation batches or to PA_ALLOC_RULES_ALL for Projects batches, depending on the BATCH_TYPE_CODE.

Common Use Cases and Queries

A primary use case is auditing and reporting on the composition of allocation sets. Administrators can query this table to list all batches assigned to a specific set, understanding the execution order and dependencies. Another common scenario is troubleshooting failed allocation set runs, where identifying the constituent batches is the first step. A typical query would join GL_AUTO_ALLOC_BATCHES to GL_AUTO_ALLOC_SETS and the relevant batch table (e.g., GL_ALLOC_BATCHES) based on the BATCH_TYPE_CODE.

  • Sample Query: To list all MassAllocation batches in an allocation set named 'Q4_DEPT_ALLOC':
    SELECT gab.batch_id, gab.batch_type_code, gb.name
    FROM gl_auto_alloc_batches gab,
    gl_auto_alloc_sets gas,
    gl_alloc_batches gb
    WHERE gab.allocation_set_id = gas.allocation_set_id
    AND gas.name = 'Q4_DEPT_ALLOC'
    AND gab.batch_type_code = 'M' -- Example code for MassAllocation
    AND gab.batch_id = gb.batch_id;

Related Objects

This table is central to the allocation set architecture and has defined relationships with several key objects. The primary parent table is GL_AUTO_ALLOC_SETS, which holds the definition of the allocation set itself. Child relationships are conditional on the BATCH_TYPE_CODE: for General Ledger batches (MassAllocation, etc.), it references GL_ALLOC_BATCHES; for Projects-related batches, it references PA_ALLOC_RULES_ALL. In application logic, this table is accessed by the allocation set submission and processing engines within the General Ledger module. Direct modifications should be performed through the Oracle EBS user interface or supported APIs to maintain data integrity.