Search Results gl_alloc_batches_s

Overview

APPS.GL_ALLOC_BATCHES_PKG is a PL/SQL package body in the Oracle E-Business Suite General Ledger (GL) schema. Its business purpose is to manage allocation batch definitions within the GL allocation engine. Allocation batches group one or more allocation formulas into a single executable unit, enabling the mass distribution of balances from source accounts to target accounts according to defined allocation rules. The package encapsulates the standard insert, update, lock, and delete operations required to maintain rows in the GL_ALLOC_BATCHES base table and its associated MLS (Multi-Language Support) table, GL_ALLOC_BATCHES_S. It also supports batch-level validation and duplication logic used when administrators build or copy allocation definitions through the Allocation Batch definition form.

Key Procedures and Functions

The ETRM metadata documents eight callable units within this package body:

• CHECK_UNIQUE — Verifies that a proposed allocation batch definition does not conflict with an existing batch, ensuring allocation batch names or identifiers remain unique before insert or update.
• GET_UNIQUE_ID — Generates or retrieves the next unique identifier required for a new allocation batch row.
• INSERT_ROW — Inserts a new allocation batch record, populating both the base table and the MLS translation table for the current language.
• LOCK_ROW — Acquires a row-level lock on an existing allocation batch to prevent concurrent modification during an update transaction.
• UPDATE_ROW — Applies changes to an existing allocation batch definition, including its descriptive and translation attributes.
• DELETE_ROW — Removes an allocation batch and its associated translation rows, subject to referential integrity checks against dependent formulas.
• AUTOCOPY — Duplicates an existing allocation batch, copying batch-level attributes so administrators can clone definitions with minimal rekeying.
• CHECK_BATCH — Performs validation of an allocation batch prior to submission, checking that the batch is complete and conforms to required business rules.

These procedures are not declared as public APIs (classification OTHER), and no parameter lists are documented, so they should be treated as internal implementation units.

Tables Accessed

The package references the following tables through APPS synonyms:

• GL_ALLOC_BATCHES — The primary base table holding allocation batch headers; subject to insert, update, lock, delete, and validation.
• GL_ALLOC_BATCHES_S — The MLS translation table storing language-specific batch names and descriptions.
• GL_ALLOC_FORMULAS and GL_ALLOC_FORMULAS_S — Referenced to associate allocation formulas with a batch and to validate dependencies.
• GL_ALLOC_FORMULA_LINES — Referenced to inspect formula detail lines that belong to a batch.
• GL_AUTO_ALLOC_BATCHES — Used in the AUTOCOPY flow to retrieve source batch data for duplication.
• DUAL — Utility reference for single-row queries and sequence-like operations.

The package additionally depends on APP_EXCEPTION, FND_MESSAGE, and APP_EXCEPTIONS for error handling and message resolution.

Usage Notes

GL_ALLOC_BATCHES_PKG is typically invoked indirectly by the Oracle GL Allocation Batch definition form and by concurrent programs that create or validate allocation batches. Because the ETRM metadata records that this package is not referenced by any other database object and exposes no documented public API parameters, direct custom calls are discouraged; developers requiring similar behavior should use the supported Allocation APIs or the form itself. When extending or debugging allocation batch maintenance, treating these procedures as internal ensures upgrade safety, since Oracle may change their signatures without notice in 12.1.1 or 12.2.2.