Search Results ar_doc_sequence_audit




Overview
Explore in AI Chat

Overview

The AR_DOC_SEQUENCE_AUDIT table is a core audit and tracking entity within the Oracle E-Business Suite Receivables (AR) module. Its primary function is to serve as a permanent, granular log for every document number generated by the system. This is critical for ensuring transactional integrity, auditability, and the prevention of duplicate document numbers, which are fundamental requirements for financial reporting and compliance. The table operates in conjunction with the Oracle Application Object Library's (FND) document sequence engine, providing a Receivables-specific audit trail that links generated numbers to their source assignments and sequences.

Key Information Stored

The table's structure is designed to capture the essential elements of a document number generation event. Its composite primary key, AR_DOC_SEQUENCE_AUDIT_PK, consists of DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE, which together uniquely identify each audit record. The DOC_SEQUENCE_ID is a foreign key to FND_DOCUMENT_SEQUENCES, identifying the master sequence definition used. The DOC_SEQUENCE_VALUE stores the actual generated number (e.g., an invoice number, receipt number, or credit memo number). A critical foreign key, DOC_SEQUENCE_ASSIGNMENT_ID, links to FND_DOC_SEQUENCE_ASSIGNMENTS, recording the specific application and category assignment that triggered the number generation. While the provided metadata focuses on keys, typical audit tables in this context also include columns such as CREATION_DATE, CREATED_BY, and possibly the associated transaction identifier (e.g., CUSTOMER_TRX_ID for invoices).

Common Use Cases and Queries

The primary use case is troubleshooting and auditing document numbering. Analysts use this table to trace the origin of a specific document number, verify the sequence used, or investigate gaps or duplicates in numbering. Common queries include identifying all numbers generated for a specific sequence assignment or finding the audit trail for a particular transaction. For example, to find the audit record for a specific invoice number, a query would join to the transaction table:

  • SELECT aud.* FROM ar_doc_sequence_audit aud JOIN ra_customer_trx trx ON aud.doc_sequence_value = trx.trx_number WHERE trx.trx_number = 'INV-123456';

Another critical reporting use case is analyzing sequence usage and consumption over time to forecast when a sequence range will be exhausted.

Related Objects

The AR_DOC_SEQUENCE_AUDIT table has defined dependencies on two fundamental Application Object Library tables, as per the provided relationship data:

  • FND_DOCUMENT_SEQUENCES: Joined via AR_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ID. This table holds the master definition of the document sequence, including its name, type, start/end numbers, and other control attributes.
  • FND_DOC_SEQUENCE_ASSIGNMENTS: Joined via AR_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ASSIGNMENT_ID. This table defines where and how a sequence is applied—specifying the application (e.g., Receivables), document category (e.g., Invoice), and the assigned set of books or operating unit.

While not listed in the provided foreign keys, this audit table is inherently related to core Receivables transaction tables like RA_CUSTOMER_TRX (Invoices) and AR_CASH_RECEIPTS_ALL (Receipts), where the generated DOC_SEQUENCE_VALUE is typically stored as the transaction number.