Results for “oe_doc_sequence_audit”

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

Overview

OE_DOC_SEQUENCE_AUDIT is an Order Management (ONT) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it is used by the FND module for audit purposes when the sequences used to generate order numbers are created. In practice, the table acts as a historical record of document sequence values that have been consumed for order numbering, allowing organizations to trace which order numbers were assigned, when they were generated, and by which user. It sits alongside the FND document sequencing framework, which governs how sequential document numbers are allocated to transactions such as sales orders across multiple operating units and legal entities.

A heuristic Data Vault classification mined from the foreign key structure suggests this object behaves as a link table. It connects the sequence definition and the sequence assignment to a specific generated value. This modeling suggestion reflects the table's role as an associative construct between the FND configuration layer and the transactional order numbering process, rather than a pure descriptive hub or satellite.

The table resides in the ONT schema with five documented columns. Its unique index, OE_DOC_SEQUENCE_AUDIT_U1 (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE), identifies the business-key candidate — the combination that uniquely distinguishes a generated sequence value within a given sequence definition.

Key Information Stored

The documented columns capture the essential audit attributes of order number generation:

• DOC_SEQUENCE_ID — Identifies the document sequence definition in FND_DOCUMENT_SEQUENCES. Also part of the OE_DOC_SEQUENCE_AUDIT_U1 unique index.
• DOC_SEQUENCE_ASSIGNMNET_ID — References the sequence assignment in FND_DOC_SEQUENCE_ASSIGNMENTS, tying the generated value to the assignment configuration. (Note the documented spelling retains a typographical variant, "ASSIGNMNET".)
• DOC_SEQUENCE_VALUE — The actual generated order number value. Together with DOC_SEQUENCE_ID it forms the unique business-key candidate.
• CREATION_DATE — The date the audit record was created, effectively the timestamp of order number generation.
• CREATED_BY — The user who triggered the creation of the audit record, supporting accountability and traceability.

There is no separately documented surrogate primary key column in the metadata beyond the unique index; the documented uniqueness is enforced on the DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE pair. The assignment and sequence identifiers serve as foreign-key references to the FND configuration tables.

Common Use Cases and Queries

Typical scenarios involve auditing order numbering, reconciling gaps or duplicates in sales order numbers, and investigating who generated a given sequence value and when.

• Sequence consumption audit: Join DOC_SEQUENCE_ID to FND_DOCUMENT_SEQUENCES and DOC_SEQUENCE_ASSIGNMNET_ID to FND_DOC_SEQUENCE_ASSIGNMENTS to reconstruct which assignment produced each order number.
• Gap and duplicate detection: Analyze DOC_SEQUENCE_VALUE ranges per sequence to spot missing or repeated order numbers.
• User activity reporting: Aggregate by CREATED_BY and CREATION_DATE to report order number generation activity by user and period.
• Sample SQL: SELECT a.doc_sequence_id, ds.name, a.doc_sequence_value, a.creation_date, a.created_by FROM ont.oe_doc_sequence_audit a, fnd.fnd_document_sequences ds WHERE a.doc_sequence_id = ds.doc_sequence_id ORDER BY a.creation_date DESC;

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign-key relationships:

• FND_DOCUMENT_SEQUENCES — Joined via OE_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ID = FND_DOCUMENT_SEQUENCES.DOC_SEQUENCE_ID; holds the sequence definition.
• FND_DOC_SEQUENCE_ASSIGNMENTS — Joined via OE_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ASSIGNMNET_ID = FND_DOC_SEQUENCE_ASSIGNMENTS.DOC_SEQUENCE_ASSIGNMNET_ID; holds the assignment linking a sequence to an application, category, and method.
• OE_ORDER_HEADERS_ALL — The transactional order header, whose order numbers are ultimately governed by the same document sequencing framework.
• FND_DOCUMENT_CATEGORIES — Defines the document category governing which orders receive sequenced numbers.
• FND_DOC_SEQUENCE_CATEGORIES — Relates categories to sequences and assignments through the FND document sequencing configuration.

Together, these objects form the configuration-and-audit chain that controls and records sales order numbering in Oracle EBS Release 12.1.1 and 12.2.2.