Search Results doc_sequence_assignment_id

Overview

The GL_DOC_SEQUENCE_AUDIT table is a core audit and control table within the Oracle E-Business Suite General Ledger module. Its primary role is to provide a permanent, granular audit trail for the sequential numbering of accounting documents, such as journals and invoices. This ensures the integrity and non-repudiation of financial transactions by logging every number generated by the system's document sequencing engine. The table is critical for compliance, financial reporting accuracy, and troubleshooting numbering issues, as it records the exact assignment of sequence values to specific document sequence definitions and their assignments within the application.

Key Information Stored

The table's structure is defined by its composite primary key, which captures the essential components of a numbered event. The key columns are DOC_SEQUENCE_ID, which links to the master definition in FND_DOCUMENT_SEQUENCES; DOC_SEQUENCE_ASSIGNMENT_ID, which identifies the specific application context or assignment rule for that sequence; and DOC_SEQUENCE_VALUE, which is the actual generated number (e.g., 'JRNL-2024-10001'). Together, these columns create a unique record for every sequence number issued. The audit nature of the table suggests it likely includes additional standard audit columns (such as CREATION_DATE, CREATED_BY) to track when and by whom a number was generated, though these are not explicitly detailed in the provided metadata.

Common Use Cases and Queries

This table is primarily queried for audit, reconciliation, and diagnostic purposes. A common scenario involves investigating missing or duplicate journal batch numbers. An auditor or system administrator can query the audit trail to verify the sequence of numbers generated for a specific ledger or period. Another key use case is during period-end closing, to ensure all journal entries have been properly numbered before finalizing the books. A typical diagnostic query would join to the document sequences master table to get a human-readable name.

• Identifying all numbers generated for a specific sequence assignment:

  SELECT doc_sequence_value, creation_date
  FROM gl_doc_sequence_audit
  WHERE doc_sequence_assignment_id = :assignment_id
  ORDER BY creation_date;

• Auditing sequence usage by joining to the master definition:

  SELECT fds.name, gdsa.doc_sequence_value, gdsa.creation_date
  FROM gl_doc_sequence_audit gdsa,
       fnd_document_sequences fds
  WHERE gdsa.doc_sequence_id = fds.doc_sequence_id
  AND fds.application_id = 101 -- GL Application
  ORDER BY gdsa.creation_date DESC;

Related Objects

The GL_DOC_SEQUENCE_AUDIT table has a direct and critical relationship with the foundational Oracle EBS table FND_DOCUMENT_SEQUENCES. As documented in the foreign key relationship, GL_DOC_SEQUENCE_AUDIT.DOC_SEQUENCE_ID references FND_DOCUMENT_SEQUENCES. This join is essential for translating the internal sequence identifier into a meaningful sequence name used within the application. The table's primary key constraint, GL_DOC_SEQUENCE_AUDIT_UK1, enforces the uniqueness of the logged event. While not listed in the provided metadata, this audit table is inherently related to transactional tables like GL_JE_BATCHES, which would store the generated DOC_SEQUENCE_VALUE against the actual journal batch record.