Search Results fun_seq_batch




Overview
Explore in AI Chat

Overview

The APPS.FUN_SEQ_BATCH package body is a server-side PL/SQL component within the Oracle E-Business Suite Financials sequencing framework. It provides the bulk-processing engine responsible for generating and assigning journal entry sequence numbers across batches of subledger accounting entries. In Oracle EBS 12.1.1 and 12.2.2, legal sequencing of accounting transactions is a statutory requirement in many jurisdictions; journal entries must be numbered in a strictly consecutive manner within a defined sequence and accounting period. The FUN_SEQ_BATCH package consolidates these operations so that high volumes of entries can be numbered efficiently in a single concurrent run rather than through row-by-row online processing.

The package operates in the APPS schema and is a dependent of FUN_SEQ, the core sequencing engine. It is not referenced by any other database object, confirming its role as a top-level driver rather than a utility library. The object is currently VALID in the dictionary.

Key Procedures and Functions

Fifteen documented procedures comprise the package interface. The batch lifecycle is framed by BATCH_INIT and BATCH_EXIT, which establish and tear down processing context, including concurrent request state and logging through FND_LOG and FND_CONCURRENT. RELEASE_LOCK manages serialization so that a sequence range is not contended by concurrent batch workers.

Data preparation is handled by a family of populate routines: POPULATE_SEQ_INFO, POPULATE_SEQ_REQUESTS, POPULATE_SEQ_CONTEXT, POPULATE_SEQ_HEADERS, and POPULATE_NUMBERS. These populate the global temporary and staging structures used during the run. Accounting-specific staging is performed by POPULATE_ACCT_SEQ_INFO and POPULATE_ACCT_SEQ_PROG_VIEW, while POPULATE_REP_SEQ_PROG_GT handles reporting sequence generation. GENERATE_BULK_NUMBERS is the primary engine that assigns sequence values in bulk to the staged entries. SORT_ACCT_ENTRIES orders entries deterministically before numbering, and DELETE_SEQ_REQUESTS performs cleanup of processed request records. Together these procedures implement the full assign-sort-number-persist cycle.

Tables Accessed

The package reads and writes the principal sequencing configuration tables FUN_SEQ_ASSIGNMENTS, FUN_SEQ_CONTEXTS, FUN_SEQ_HEADERS, and FUN_SEQ_VERSIONS, which define which sequences apply to which ledger, category, and period combinations. Assignment results are staged in FUN_SEQ_REQUESTS and the global temporary table FUN_SEQ_BATCH_GT. Journal sources are drawn from GL_JE_HEADERS and XLA_AE_HEADERS, with XLA_ACCT_PROG_SEQ_V and XLA_SEQ_JE_HEADERS_GT supplying subledger accounting sequence data. GL_PERIOD_STATUSES validates open or closed period status, and FND_CONCURRENT_REQUESTS tracks the concurrent request lifecycle. DUAL and PLITBLM are used for PL/SQL utility operations.

Usage Notes

FUN_SEQ_BATCH is typically invoked indirectly through concurrent programs that perform bulk journal sequencing, rather than being called directly from forms or custom code. Because it is referenced by five other packages, standard practice is to trigger it through those supported entry points. Direct invocation should be attempted only by experienced developers, executed as a concurrent request so that FND_CONCURRENT locks, logging, and completion status are correctly managed. Any custom code calling these procedures must ensure the batch context procedures BATCH_INIT and BATCH_EXIT bracket the numbering calls, and that RELEASE_LOCK is issued to avoid leaving sequence ranges locked.