Results for “fnd_doc_sequence_audit_pk”

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

Overview

FND_DOC_SEQUENCE_AUDIT is a table owned by the APPLSYS schema in the Oracle E-Business Suite Application Object Library (FND) product. Its documented purpose is to "keep track of documents" — specifically, it records the individual sequence values that have been consumed by each sequential document numbering scheme configured in EBS. In Oracle EBS 12.1.1 and 12.2.2, sequential numbering is the mechanism that assigns gapless or auditable numbers to documents such as journals, invoices, payments, requisitions, purchase orders, and receiving transactions. FND_DOC_SEQUENCE_AUDIT is the persistent audit trail that maps a generated number (DOC_SEQUENCE_VALUE) back to the sequence definition (DOC_SEQUENCE_ID) and the assignment that links the sequence to a specific application, category, and document type.

From a data-modeling perspective, the mined relationship classification for this object is link. This is a heuristic suggestion rather than a physical constraint: the table sits between the sequence definition and the assignment definition, resolving the many-to-many relationship between a numbering scheme and the sequence values actually issued under it.

Key Information Stored

The documented physical schema for this table in 12.2.2 contains five columns. The most significant are:

• DOC_SEQUENCE_ID — Identifies the document sequence definition that produced the value. Part of the primary key and a foreign key to FND_DOCUMENT_SEQUENCES.
• DOC_SEQUENCE_VALUE — The actual sequential number assigned to a document. Part of the primary key.
• DOC_SEQUENCE_ASSIGNMENT_ID — Identifies the assignment record that binds a sequence to an application/document context. Foreign key to FND_DOC_SEQUENCE_ASSIGNMENTS.
• CREATION_DATE — Standard EBS audit column recording when the sequence value row was inserted.
• CREATED_BY — Standard EBS audit column identifying the user or process that inserted the row.

The surrogate primary key is FND_DOC_SEQUENCE_AUDIT_PK, defined over (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE). A separate unique index, FND_DOC_SEQUENCE_AUDIT_U1, is defined over the identical column pair (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE); this effectively enforces that no sequence value can be reused within a given sequence, which is the core business-key guarantee of sequential numbering. Note that DOC_SEQUENCE_ASSIGNMENT_ID is not part of the primary key, reinforcing that the binding constraint is the (sequence, value) pair itself.

Common Use Cases and Queries

Auditors and controllers use this table to verify that no gaps exist in a numbered document stream, or to explain gaps when they do occur. A typical reconciliation joins the audit table to the sequence definition to detect missing values:

• Gap analysis: select DOC_SEQUENCE_VALUE ordered by value for a given DOC_SEQUENCE_ID and compare against the expected contiguous range.
• Document traceability: given a document number, join back through DOC_SEQUENCE_ASSIGNMENT_ID to determine which assignment and application issued it.
• Consumption reporting: aggregate counts of DOC_SEQUENCE_VALUE by DOC_SEQUENCE_ID and CREATION_DATE to report daily volumes.
• Assignment audit: joining FND_DOC_SEQUENCE_AUDIT to FND_DOC_SEQUENCE_ASSIGNMENTS to confirm that values were issued only against valid assignments.

A representative query pattern is a three-way join between the audit table, FND_DOCUMENT_SEQUENCES, and FND_DOC_SEQUENCE_ASSIGNMENTS using the documented foreign key columns, filtered by application and date range.

Related Objects

• FND_DOCUMENT_SEQUENCES — The parent definition table; joined on DOC_SEQUENCE_ID.
• FND_DOC_SEQUENCE_ASSIGNMENTS — Links sequences to application/document contexts; joined on DOC_SEQUENCE_ASSIGNMENT_ID.
• FND_DOC_SEQUENCE_CATEGORIES — Defines document categories referenced by assignments.
• FND_SEQUENCES / database sequences — Backend mechanisms that generate values audited here.
• Document-owning application tables (e.g., GL_JE_HEADERS, AP_INVOICES_ALL, PO_HEADERS_ALL) — Consume sequence values recorded in this table.
• FND_DOC_SEQUENCE_AUDIT_PK / _U1 indexes — Enforce uniqueness of (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE).

Together these objects form the sequential numbering and audit framework that underpins legal and regulatory numbering requirements across EBS modules.