Search Results populate_rep_seq_prog_gt

Overview

APPS.FUN_SEQ_BATCH is a server-side PL/SQL package in Oracle E-Business Suite that supports the generation and management of sequential document numbers processed in bulk. It belongs to the Oracle Financials sequencing infrastructure, which underpins gapless and non-gapless sequence assignment for subledger accounting entries, General Ledger journal headers, and related accounting events. The package operates as a batch-oriented engine: rather than issuing sequence values one at a time, it populates staging structures that allow large volumes of accounting entries to be numbered efficiently in a single pass.

The package source is versioned at header 120.20, indicating it is a mature, shipping object within the Financials family. Its primary role is fulfilled through the POPULATE_SEQ_REQUESTS procedure, which is the entry point most commonly associated with the package by administrators and developers searching for "populate_seq_requests". This procedure assembles the set of sequence requests that the batch engine subsequently processes.

Key Procedures and Functions

The package exposes fifteen documented procedures. BATCH_INIT and BATCH_EXIT manage the lifecycle of a batch run, establishing and releasing the working context used by the remaining routines. GENERATE_BULK_NUMBERS performs the core operation of producing sequence values for the collected requests.

The POPULATE family prepares and loads the batch staging structures. POPULATE_SEQ_REQUESTS builds the request set from source accounting data; POPULATE_SEQ_INFO and POPULATE_ACCT_SEQ_INFO derive the applicable sequence version and assignment information for each request; POPULATE_SEQ_CONTEXT resolves contextual attributes that govern sequencing rules; POPULATE_SEQ_HEADERS determines the sequence header to be applied; POPULATE_NUMBERS assigns the resulting numeric values; and POPULATE_ACCT_SEQ_PROG_VIEW and POPULATE_REP_SEQ_PROG_GT load reporting and program-level views or temporary tables used for downstream processing. SORT_ACCT_ENTRIES orders collected accounting entries into a deterministic sequence before numbering. DELETE_SEQ_REQUESTS clears staged requests, and RELEASE_LOCK frees the concurrency locks held during batch processing. The package declares extensive collection types, including tables of sequence versions, assignment identifiers, ledger and journal header identifiers, and context values, all indexed by source identifier, which confirms its set-based bulk design.

Tables Accessed

The package reads and writes several core sequencing and accounting tables through APPS synonyms. FUN_SEQ_HEADERS, FUN_SEQ_VERSIONS, FUN_SEQ_ASSIGNMENTS, and FUN_SEQ_CONTEXTS define the sequence configuration hierarchy — header, version, assignment, and context — and are the authoritative source for how numbers are allocated. FUN_SEQ_REQUESTS and FUN_SEQ_BATCH_GT serve as the request staging and global temporary structures that drive the batch run.

Accounting source data is drawn from GL_JE_HEADERS for General Ledger journal headers and from XLA_AE_HEADERS for subledger accounting entry headers; XLA_SEQ_JE_HEADERS_GT is a staging structure for journal entry sequencing. GL_PERIOD_STATUSES is consulted to validate the period context for numbered entries. FND_CONCURRENT_REQUESTS identifies the concurrent request executing the batch, and DUAL and PLITBLM are used for utility operations and PL/SQL table handling.

Usage Notes

FUN_SEQ_BATCH is not typically called directly by end users. It is invoked by concurrent programs and internal Financials processes, particularly those that number journal entries and subledger accounting entries in bulk before posting. The package is referenced by five other packages, indicating it functions as a shared service within the sequencing infrastructure rather than a standalone utility.

Custom code should prefer the documented entry points, especially the POPULATE_SEQ_REQUESTS workflow, rather than manipulating FUN_SEQ_* tables directly, since sequence integrity depends on the lock management performed by BATCH_INIT, RELEASE_LOCK, and BATCH_EXIT. Because the package is shipped with an "OTHER" API classification and a "noship" source header, it is not a formally supported public API; extensions should be validated against the specific EBS release in use, whether 12.1.1 or 12.2.2.