Search Results get_seq_header_name

Overview

FUN_SEQ is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the central sequencing engine for the Oracle Financials product family, generating and managing document sequence numbers and their associated assignments across subledger and general ledger transactions. In Oracle EBS, legal and regulatory requirements frequently mandate that certain financial documents (invoices, payments, journals, receipts) be assigned a unique, gapless sequence per legal entity, ledger, and document category. FUN_SEQ encapsulates the logic that fulfills this obligation, providing reusable APIs so that other application modules do not each have to reimplement sequence assignment, auditability, and gapless-number enforcement.

The package carries an API classification of OTHER in the ETRM documentation and exposes twenty-nine documented procedures and functions. It is both a consumer and a provider: it reads its own configuration tables while being invoked by high-level financial modules such as subledger accounting (XLA), period status management (FUN_PERIOD_STATUS_PKG), and open interface processing (FUN_OPEN_INTERFACE_PKG).

Key Procedures and Functions

The documented interface centers on retrieving and generating sequence numbers, together with context and assignment resolution:

• GET_SEQUENCE_NUMBER – Top-level entry point that returns the next or current sequence number for a given assignment, applying applicable context and control rules.
• GET_SEQUENCE_NUMBER_NO_COMMIT / GET_SEQUENCE_NUMBER_COMMIT – Variations of sequence retrieval that respectively suppress or force an explicit commit of the sequencing transaction, giving callers control over transaction boundaries.
• GENERATE_SEQUENCE_NUMBER – Produces a new sequence value, updating the underlying sequence state as required.
• RESET – Resets sequence state, typically used for periodic or administrative reinitialization.
• GET_ASSIGNED_SEQUENCE_INFO / GET_ASSIGNED_SEQUENCE_HEADER / GET_SEQ_HEADER_ASSIGNMENT – Return assignment, header, and contextual metadata describing how a sequence is assigned to a document type or entity.
• GET_IC_ASSIGNED_SEQ_HEADER – Retrieves assigned sequence header information for intercompany processing scenarios.
• GET_ASSIGN_CONTEXT_INFO / GET_CACHED_CONTEXT_INFO / GET_SEQ_CONTEXT_NAME – Resolve the sequence context (such as ledger, entity, or category) and provide cached lookups for performance.
• GET_CACHED_SEQ_HEADER_ASSIGN / GET_CACHED_SEQ_HEADER_EXP / GET_SEQ_HEADER_EXCEPTION / GET_SEQ_HEADER_NAME – Cached retrieval of header assignment and header-level exception handling information.
• GET_SEQ_VERSION – Returns version information associated with the sequence configuration.
• GET_CONTROL_DATE_VALUE – Supplies the control date used when determining effective sequence configuration.
• UPDATE_GAPLESS_STATUS / UPDATE_DB_STATUS – Maintain gapless sequence status and database status flags used during sequencing operations.

Tables Accessed

FUN_SEQ references the following APPS synonym tables:

• FUN_SEQ_ASSIGNMENTS – Stores the mapping between sequence assignments and the document categories or processes that use them.
• FUN_SEQ_CONTEXTS – Holds context definitions that qualify when and how a sequence applies.
• FUN_SEQ_HEADERS – Contains header-level sequence configuration, including numbering rules and control information.
• FUN_SEQ_VERSIONS – Tracks versions of sequence configuration for auditability and historical accuracy.
• PLITBLM – A PL/SQL index-by table type used internally for bulk processing and in-memory collection manipulation.

Usage Notes

FUN_SEQ is not typically invoked directly from Oracle Forms user interfaces. Rather, it is called programmatically by higher-level packages during transaction processing. Documented references include FUN_OPEN_INTERFACE_PKG, FUN_PERIOD_STATUS_PKG, FUN_SEQ_BATCH, FUN_SEQ_W (the workflow-attached wrapper), FUN_TRX_PVT, XLA_ACCOUNTING_PKG, XLA_JOURNAL_ENTRIES_PKG, XLA_REPORTING_SEQUENCE_PKG, and XLA_SEQUENCE_DATAFIX_PKG.

This dependency profile indicates that customizations and diagnostic scripts should treat FUN_SEQ as low-level infrastructure. When troubleshooting missing, duplicated, or non-sequential document numbers, developers commonly query the FUN_SEQ_HEADERS, FUN_SEQ_ASSIGNMENTS, and FUN_SEQ_CONTEXTS tables directly, then trace the caller from the referencing packages listed above. Because several entry points control commits explicitly, custom code integrating with FUN_SEQ must select the COMMIT or NO_COMMIT variant appropriate to its own transaction boundaries to preserve gapless numbering integrity.