Search Results get_next_user_sequence

Overview

FND_SEQNUM is the Oracle E-Business Suite document sequence engine. Document sequences provide gapless, auditable numbering for business documents such as invoices, journals, purchase orders, payments, and receipts, supporting statutory legal numbering requirements in many jurisdictions. The package body APPS.FND_SEQNUM implements the runtime logic behind the Administrative Document Sequences functionality. It resolves which sequence applies to a given document category and entity, retrieves the next available value, and records usage. The package is tightly coupled to the Document Sequences setup schema, reading definitions from FND_DOCUMENT_SEQUENCES and their assignment records, and it dispatches to underlying database sequences or internal counters depending on whether a sequence is defined as gapless, automatic, or manual. Because it is invoked by numerous EBS products during transaction entry and posting, the package reports a status of VALID and is referenced by 47 other packages, making it a critical shared component of the EBS application foundation layer.

Key Procedures and Functions

• GET_NEXT_SEQUENCE — Returns the next document sequence value for a specified sequence assignment.
• GET_SEQ_NAME — Resolves and returns the name of a document sequence.
• GET_NEXT_AUTO_SEQ / GET_NEXT_AUTO_SEQUENCE — Retrieve the next value for automatically generated (database-backed) sequences.
• CREATE_GAPLESS_SEQUENCES / CREATE_GAPLESS_SEQUENCE — Create the supporting structure for gapless sequences, which are implemented to avoid gaps in numbering.
• GET_NEXT_USER_SEQUENCE — Returns the next value for manually entered, user-defined sequences.
• CREATE_DB_SEQ — Creates the underlying Oracle database sequence used by automatic sequence types.
• GET_SEQ_INFO — Returns descriptive information about a document sequence, such as its type and category.
• CREATE_AUDIT_REC — Writes an audit record capturing sequence usage.
• GET_SEQ_VAL — Returns the current value of a sequence.
• DEFINE_DOC_SEQ — Defines a document sequence record in the setup tables.
• ASSIGN_DOC_SEQ — Assigns a sequence to an application, category, and entity.

Tables Accessed

• FND_DOCUMENT_SEQUENCES / FND_DOCUMENT_SEQUENCES_S — Holds sequence definitions and their translation records.
• FND_DOC_SEQUENCE_ASSIGNMENTS / FND_DOC_SEQUENCE_ASSIGNMENTS_S — Stores sequence assignments to applications, categories, and entities.
• FND_DOC_SEQUENCE_CATEGORIES — Defines the document categories against which sequences are assigned.
• FND_DOC_SEQUENCE_USERS — Tracks per-user sequence usage assignments.
• FND_APPLICATION, FND_PRODUCT_INSTALLATIONS — Identify the owning application and installation context.
• FND_DESCR_FLEX_COLUMN_USAGES — Supports descriptive flexfield context for sequence usage.
• FND_ORACLE_USERID, FND_GLOBAL, FND_PROFILE — Provide session and connection context, user identity, and profile option values.
• GL_SETS_OF_BOOKS — Supplies ledger context for financial document numbering.
• AD_DDL and DBMS_SQL — Used to execute dynamic DDL for creating database sequences.

Usage Notes

FND_SEQNUM is rarely called directly by end users. It is invoked programmatically by EBS forms and concurrent programs during document entry and posting, where the calling product requests the next sequence value after confirming the applicable assignment via a system or manual sequence definition. Custom code may call GET_NEXT_SEQUENCE and ASSIGN_DOC_SEQ when extending EBS functionality with new document types. Administrative setup, including DEFINE_DOC_SEQ and ASSIGN_DOC_SEQ, is normally performed through the Document Sequences responsibility rather than direct API invocation. Because the package creates and consumes database sequences and writes audit records, deployments that customise numbering should account for the transactional behaviour of gapless versus automatic sequences.