Results for “fnd_document_sequences”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPLSYS.FND_DOCUMENT_SEQUENCES is the Oracle Application Object Library (FND) registration table for document sequences in Oracle E-Business Suite 12.1.1 and 12.2.2. A document sequence is an Oracle EBS construct that assigns unique, gapless, or auditable numbers to business documents — invoices, payments, journal entries, receipts, statements, and similar artifacts — in order to satisfy legal and statutory numbering requirements. Every sequence used by an EBS application is first defined and registered in this table, and the transactional tables of the subledgers and general ledger then reference the registered sequence through a DOC_SEQUENCE_ID foreign key column.

The table functions as a control-plane or configuration object rather than a transactional one. Its rows are created through the Document Sequences form (System Administrator responsibility), and the sequence definition drives runtime behavior such as numbering method (Automatic, Gapless, or Manual), database sequence name used for number generation, and audit table name where used numbers are recorded. Under the heuristic Data Vault classification supplied in the metadata, FND_DOCUMENT_SEQUENCES is identified as a hub: it holds a durable, uniquely identified business entity (the document sequence) whose key is referenced by a large community of surrounding tables.

Key Information Stored

The table is documented with 32 columns. The most significant are:

• DOC_SEQUENCE_ID — surrogate primary key, enforced by FND_DOCUMENT_SEQUENCES_PK and also carried by the unique index FND_DOCUMENT_SEQUENCES_U1. This is the value propagated into all downstream DOC_SEQUENCE_ID columns.
• NAME — the user-visible sequence name; the business-key candidate, enforced by the unique index FND_DOCUMENT_SEQUENCES_U2.
• APPLICATION_ID — the owning application (AP, AR, GL, CE, and so on) that registered the sequence.
• TYPE — the numbering method (for example Automatic, Gapless, or Manual), which determines whether gaps are tolerated and whether an audit trail is written.
• DB_SEQUENCE_NAME — the underlying database sequence used to generate the next number.
• INITIAL_VALUE — the starting value for the sequence.
• TABLE_NAME and AUDIT_TABLE_NAME — the transactional table that consumes the sequence and the audit table that stores issued numbers, respectively.
• START_DATE and END_DATE — the effective window during which the sequence may be used.
• MESSAGE_FLAG — controls whether a warning is raised when numbering is consumed out of the expected order.
• Standard WHO audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include identifying which sequence assigned a document number, confirming the numbering method and audit configuration for a sequence, and resolving the sequence behind a transactional row when reconciling documents in AP, AR, GL, or CE. Because AP_HISTORY_CHECKS_ALL.DOC_SEQUENCE_ID and AP_HISTORY_INVOICES_ALL.DOC_SEQUENCE_ID are both foreign keys to this table, a query that joins an archived payment or invoice to its sequence definition is a common reporting pattern:

• Look up a sequence by name: SELECT doc_sequence_id, name, type, application_id FROM applsys.fnd_document_sequences WHERE name = :seq_name;
• Find the sequence used by a specific check: SELECT h.check_id, h.doc_sequence_id, s.name, s.type FROM ap.ap_history_checks_all h JOIN applsys.fnd_document_sequences s ON s.doc_sequence_id = h.doc_sequence_id WHERE h.check_id = :check_id;
• List all sequences owned by an application: SELECT name, type, db_sequence_name, table_name, audit_table_name FROM applsys.fnd_document_sequences WHERE application_id = :app_id ORDER BY name;
• Audit readiness check: compare TABLE_NAME and AUDIT_TABLE_NAME to confirm which sequences are configured as audited versus gapless.

Reporting against this table supports period-end reconciliation, statutory audits, and investigation of gap or duplicate number issues in subledger documents.

Related Objects

The table is a hub referenced by a very large set of EBS tables. The most significant relationships, using the documented join columns, include:

• AP_CHECKS_ALL.DOC_SEQUENCE_ID and AP_HISTORY_CHECKS_ALL.DOC_SEQUENCE_ID — payments and archived payments.
• AP_INVOICES_ALL.DOC_SEQUENCE_ID and AP_HISTORY_INVOICES_ALL.DOC_SEQUENCE_ID — invoices and archived invoices.
• GL_JE_HEADERS.DOC_SEQUENCE_ID — journal entry headers.
• RA_CUSTOMER_TRX_ALL.DOC_SEQUENCE_ID and AR_CASH_RECEIPTS_ALL.DOC_SEQUENCE_ID — AR transactions and receipts.
• FND_DOC_SEQUENCE_ASSIGNMENTS.DOC_SEQUENCE_ID — the assignment of a sequence to a specific application and category of document.
• FND_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ID — the FND audit table recording numbers already issued.
• FND_DOC_SEQUENCE_ACCESS.DOC_SEQUENCE_ID and FND_DOC_SEQUENCE_USERS.DOC_SEQUENCE_ID — security and runtime access control for sequence consumption.
• XLA_AE_HEADERS.DOC_SEQUENCE_ID — subledger accounting entry headers.
• CE_STATEMENT_HEADERS_ALL.DOC_SEQUENCE_ID and CE_PAYMENT_TRANSACTIONS.DOC_SEQUENCE_ID — cash management statements and transactions.

Together, these relationships confirm the table's role as the central registration point from which numbering is governed across the EBS financials and accounting modules.