Search Results batch_init

Overview

APPS.GL_GLPPOS_ACCTSEQ_PKG is a General Ledger posting support package delivered as part of the Oracle E-Business Suite GL module. It is classified under the ETRM as an "OTHER" API, meaning it is an internal, implementation-support object rather than a public PL/SQL interface intended for direct customer invocation. The package body provides the accounting sequence initialization logic used by the posting process to prepare ledgers before journal entries are assigned their accounting sequence values.

The single documented procedure, Batch_Init, coordinates the initialization of batch-level accounting sequencing for a posting run. It identifies the distinct ledgers participating in a posting run for a given chart of accounts, attempts to lock those ledgers for sequence initialization through the FUN_SEQ_BATCH service, and records any ledgers that could not be locked into a global temporary table. The package thus acts as a bridge between the GL posting run structures and the underlying accounting sequence engine that guarantees gap-controlled, sequential journal entry numbering.

Key Procedures and Functions

• BATCH_INIT — The only documented procedure in the package. It accepts a request identifier, a chart of accounts identifier, and a posting run identifier, and returns a count of ledgers that were locked. Its logic selects the distinct ledger identifiers associated with incomplete journal batches in the posting run, delegates to FUN_SEQ_BATCH.batch_init for sequence initialization, and, where ledgers were locked, inserts them into the GL_POSTING_ACCT_SEQ_GT global temporary table. The returned count communicates how many ledgers were successfully locked, which the caller uses to determine whether posting can proceed. The procedure includes standard exception handling that re-raises application exceptions and, for any other error, raises a message using the GL_UNHANDLED_EXCEPTION token with the procedure name recorded.

No other procedures or functions are documented for this package body, and the extract confirms the package contains only Batch_Init within the GL_GLPPOS_ACCTSEQ_PKG body scope.

Tables Accessed

• GL_JE_BATCHES — Read to identify journal batches belonging to the current posting run, filtered by chart of accounts and by status of 'I' (incomplete). These batches define the scope of the sequence initialization.
• GL_JE_HEADERS — Joined to GL_JE_BATCHES to retrieve the distinct ledger identifiers associated with those batches, since ledger context resides at the header level.
• GL_POSTING_ACCT_SEQ_GT — Written to via a FORALL bulk insert. This global temporary table holds the ledger identifiers that were successfully locked by FUN_SEQ_BATCH.batch_init and is consumed downstream by the posting process.
• PLITBLM — Referenced through an APPS synonym, appearing in the documented table list. This is typically related to the posting/interim processing infrastructure that supports the accounting sequence workflow.

Usage Notes

Because the package is classified as OTHER and is referenced by no other documented packages, it is intended to be called within the internal GL posting flow rather than from custom code. Typical invocation occurs when a posting run executes: the posting engine invokes Batch_Init to establish ledger-level locks and populate the temporary sequence table before accounting entries are written.

Users searching for "batch_init" are most likely tracing posting diagnostics or investigating sequence lock behavior. Since the procedure does not appear on a public API list, custom integrations should not call it directly; instead, they should rely on the supported posting submission mechanisms. The out parameter reporting locked ledger counts is useful for diagnosing contention scenarios where a ledger cannot be locked, which is a common cause of posting delays or failures in high-volume, multi-ledger environments.