Search Results fnd_doc_sequence_audit




Overview
Explore in AI Chat

Overview

The FND_DOC_SEQUENCE_AUDIT table is a core Application Object Library table within Oracle E-Business Suite (EBS) that serves as a detailed audit log for document sequence number generation. Its primary role is to persistently track every instance where a document sequence number is assigned to a transaction, such as an invoice, journal, or purchase order. This auditing mechanism is critical for maintaining data integrity, ensuring non-repudiation, and providing a verifiable audit trail for compliance with financial and regulatory standards. The table operates in conjunction with the document sequencing functionality, which guarantees unique, gapless, and auditable numbering for key business documents.

Key Information Stored

The table records essential metadata for each sequence number assignment. While the full column list is not detailed in the provided metadata, the documented primary and foreign keys reveal its core structure. The primary key is a composite of DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE, ensuring each generated sequence number for a specific sequence definition is uniquely recorded. The DOC_SEQUENCE_ID is a foreign key linking to FND_DOCUMENT_SEQUENCES, identifying the sequence definition used. The DOC_SEQUENCE_VALUE stores the actual generated number (e.g., INV-10001). The DOC_SEQUENCE_ASSIGNMENT_ID is a foreign key linking to FND_DOC_SEQUENCE_ASSIGNMENTS, recording the specific assignment rule that triggered the number generation. Typical audit columns like CREATED_BY and CREATION_DATE are also expected to be present, capturing who generated the number and when.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting document numbering. Administrators query this table to verify sequence usage, investigate missing numbers, or reconcile transactions. A common reporting query involves joining to related tables to get a human-readable audit trail. For example, to audit invoice numbering:

  • SELECT fds.name AS seq_name, fdsa.application_table_name, fdss.doc_sequence_value, fdss.creation_date
  • FROM fnd_doc_sequence_audit fdss
  • JOIN fnd_document_sequences fds ON fdss.doc_sequence_id = fds.doc_sequence_id
  • JOIN fnd_doc_sequence_assignments fdsa ON fdss.doc_sequence_assignment_id = fdsa.doc_sequence_assignment_id
  • WHERE fds.name = 'INVOICE_NUM_SEQ' ORDER BY fdss.creation_date DESC;

This helps confirm that every sequenced transaction has a corresponding audited record, which is vital for financial audits.

Related Objects

FND_DOC_SEQUENCE_AUDIT has defined foreign key relationships with two key tables in the document sequencing architecture, as per the provided metadata:

  • FND_DOCUMENT_SEQUENCES: The relationship is via the DOC_SEQUENCE_ID column. This table stores the master definition of the document sequence, including its name, type (e.g., Gapless), and start number.
  • FND_DOC_SEQUENCE_ASSIGNMENTS: The relationship is via the DOC_SEQUENCE_ASSIGNMENT_ID column. This table defines the rules that determine when and where a specific document sequence is applied, linking the sequence to an application, table, and set of books.

These relationships form the backbone of the document sequencing system, where assignments define the rule, sequences define the number range, and the audit table logs every individual generation event.