Results for “doc_sequence_value”

50+ results




Overview
Explore in AI Chat

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

Overview

GL_DOC_SEQUENCE_AUDIT is a General Ledger (GL) schema table that serves as the sequential numbering audit table within Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to record the assignment of sequential document numbers to accounting transactions and journal entries, providing an auditable trail that supports statutory requirements for gapless, sequential numbering of posted documents. The table captures which document sequence was consumed, under which assignment, and the specific sequence value generated, thereby enabling reconciliation between the numbering infrastructure and the actual documents produced.

From a Data Vault modeling perspective, the heuristic classification of GL_DOC_SEQUENCE_AUDIT is satellite-leaning. This suggests the table behaves as a descriptive, dependent record attached to a parent hub or link rather than as an independent business entity. In practical EBS terms, it operates as a child audit record whose identity is meaningful only in relation to its parent document sequence definition.

Key Information Stored

The documented physical schema contains five columns in the GL schema. The most significant of these are:

  • DOC_SEQUENCE_ID — References the parent document sequence definition in FND_DOCUMENT_SEQUENCES. This is the primary linkage to the numbering configuration.
  • DOC_SEQUENCE_ASSIGNMENT_ID — Identifies the specific assignment that binds a sequence to a document category or ledger context, forming part of the composite unique key.
  • DOC_SEQUENCE_VALUE — The actual sequential number generated and consumed for a document. This is the auditable value of greatest reporting interest.
  • CREATION_DATE — Standard EBS audit column recording when the audit row was created, useful for temporal analysis of sequence consumption.
  • CREATED_BY — Standard EBS audit column capturing the user who generated the audit record.

The primary key, GL_DOC_SEQUENCE_AUDIT_UK1, is a composite business key over DOC_SEQUENCE_ID, DOC_SEQUENCE_ASSIGNMENT_ID, and DOC_SEQUENCE_VALUE. A separate unique index, GL_DOC_SEQUENCE_AUDIT_U1, covers DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE, reinforcing the uniqueness of each sequence value within its parent sequence. No single-column surrogate key is documented; identity is entirely business-key driven.

Common Use Cases and Queries

Typical scenarios include auditing sequence gaps, reconciling posted journals to consumed numbers, and investigating duplicate or missing document numbers.

To trace a sequence value to its parent definition:

  • Join GL_DOC_SEQUENCE_AUDIT to FND_DOCUMENT_SEQUENCES on DOC_SEQUENCE_ID to retrieve the sequence name and type.
  • Filter by DOC_SEQUENCE_ID and order by DOC_SEQUENCE_VALUE to inspect the numbering range.

A gap-detection query compares consecutive DOC_SEQUENCE_VALUE rows within a given sequence to identify breaks. Reporting queries join the audit table to journal sources and categories to confirm that each posted journal carries a valid sequential number. Historical analysis groups rows by CREATION_DATE to trend sequence consumption over accounting periods.

Related Objects

The most significant related objects are:

  • FND_DOCUMENT_SEQUENCES — The parent table referenced by DOC_SEQUENCE_ID; defines each sequence.
  • FND_DOC_SEQUENCE_ASSIGNMENTS — Supplies the assignment context referenced by DOC_SEQUENCE_ASSIGNMENT_ID.
  • GL_JE_HEADERS and GL_JE_BATCHES — Journal headers and batches whose numbering is validated against this audit table.
  • GL_JE_SOURCES — Journal sources that map to assigned document sequences.
  • FND_DOCUMENT_CATEGORIES — Categories under which sequences are assigned to documents.

These relationships make GL_DOC_SEQUENCE_AUDIT a key component of the GL document numbering audit framework.