Results for “ar_doc_sequence_audit”

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

Overview

The AR_DOC_SEQUENCE_AUDIT table, owned by the AR (Receivables) schema, records a historical audit trail for every document number generated by the Oracle E-Business Suite document sequencing framework. Each row captures the issuance of a single sequential document number, tying that number back to the sequence definition and to the specific assignment through which it was consumed. The table is a core compliance object in Receivables, since it provides the forensic evidence required for legal numbering audits, tax authority reporting, and gap analysis across invoices, credit memos, debit memos, and other numbered AR documents.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is best modeled as a link. It does not function as a hub of a business entity in its own right; instead it records the association between a document sequence definition (FND_DOCUMENT_SEQUENCES) and a document sequence assignment (FND_DOC_SEQUENCE_ASSIGNMENTS), with the assigned numeric value as the descriptive payload. In Data Vault terms, the sequence value and timestamps behave as link-level descriptive attributes rather than as an independent satellite business key.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains five columns. The principal column is DOC_SEQUENCE_ID, a foreign key that identifies which document sequence definition was used to produce the number. DOC_SEQUENCE_ASSIGNMENT_ID is a foreign key to FND_DOC_SEQUENCE_ASSIGNMENTS and identifies the assignment — that is, the combination of sequence, application, category/type, and, where applicable, ledger or operating unit — that consumed the number. DOC_SEQUENCE_VALUE stores the actual numeric value assigned to the document, the column most frequently queried in numbering audits.

The primary key, AR_DOC_SEQUENCE_AUDIT_PK, is a composite surrogate over (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE), meaning a given sequence cannot legitimately issue the same value twice. A unique index, AR_DOC_SEQUENCE_AUDIT_U1, reinforces this same business-key candidate pair at the database level, making (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE) the definitive uniqueness constraint for the audit record. The remaining columns, CREATION_DATE and CREATED_BY, are standard WHO columns that record the timestamp and the user or process that generated the number, enabling chronological reconstruction of numbering activity.

Common Use Cases and Queries

The most common scenario is gap detection, in which an auditor verifies that no document number was skipped within a given sequence. A typical query pattern groups the audit table by sequence and orders by value:

• Sequence consumption report: SELECT DOC_SEQUENCE_ID, COUNT(*), MIN(DOC_SEQUENCE_VALUE), MAX(DOC_SEQUENCE_VALUE) FROM AR.AR_DOC_SEQUENCE_AUDIT GROUP BY DOC_SEQUENCE_ID;
• Gap analysis: SELECT DOC_SEQUENCE_VALUE + 1 AS gap_start FROM AR.AR_DOC_SEQUENCE_AUDIT a WHERE NOT EXISTS (SELECT 1 FROM AR.AR_DOC_SEQUENCE_AUDIT b WHERE b.DOC_SEQUENCE_ID = a.DOC_SEQUENCE_ID AND b.DOC_SEQUENCE_VALUE = a.DOC_SEQUENCE_VALUE + 1);
• Assignment tracing: joining to FND_DOC_SEQUENCE_ASSIGNMENTS on DOC_SEQUENCE_ASSIGNMENT_ID to determine which application, category, and ledger produced a given number, which the user's search term fnd_doc_sequence_assignments directly anticipates.
• Reconciliation against AR_INVOICE_HEADERS or AR_CASH_RECEIPTS to confirm that each posted document corresponds to a recorded audit number.

Related Objects

The following objects are most significant to AR_DOC_SEQUENCE_AUDIT based on the documented foreign key relationships:

• FND_DOCUMENT_SEQUENCES — joined via DOC_SEQUENCE_ID; defines the sequence itself, including its initial value, table, and type.
• FND_DOC_SEQUENCE_ASSIGNMENTS — joined via DOC_SEQUENCE_ASSIGNMENT_ID; the assignment that scopes a sequence to an application and category.
• FND_DOC_SEQUENCE_CATEGORIES — reached indirectly through the assignment; identifies the document category being numbered.
• AR_INVOICE_HEADERS_ALL and AR_CASH_RECEIPTS_ALL — the principal AR documents whose numbering is audited here.
• AR_DOC_SEQUENCE_AUDIT_PK and AR_DOC_SEQUENCE_AUDIT_U1 — the primary key and unique index that enforce numbering uniqueness.