Results for “doc_sequence_id”

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

Overview

The JG_ZZ_VAT_DOC_SEQUENCES table resides in the JG schema, which hosts Oracle E-Business Suite Regional Localizations. It captures the association between a VAT register and the Oracle Applications document sequence assigned to it, providing the sequential numbering backbone required for statutory VAT reporting. Records in this table allow regulatory extracts, audit trails, and fiscal reports to reference gaps-free, auditable document numbers rather than raw transactional identifiers. The table is classified as VALID and is present in both EBS 12.1.1 and 12.2.2, with an eight-column physical schema documented under ETRM 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link table. It resolves a many-to-many style relationship between a VAT register and an Oracle document sequence, and it does not carry the descriptive attributes that would characterize a satellite. The two foreign keys — VAT_REGISTER_ID and DOC_SEQUENCE_ID — form the natural business key of that association.

Key Information Stored

The most significant columns support the identity and traceability of each register-to-sequence assignment:

• VAT_DOC_SEQUENCE_ID — surrogate primary key defined by JG_ZZ_VAT_DOC_SEQUENCES_PK, and also the leading column of the unique index JG_ZZ_VAT_DOC_SEQUENCES_U1.
• VAT_REGISTER_ID — foreign key to JG_ZZ_VAT_REGISTERS_B, identifying the VAT register to which the sequence applies.
• DOC_SEQUENCE_ID — foreign key to FND_DOCUMENT_SEQUENCES, identifying the Oracle document sequence used for numbering.
• VAT_REGISTER_ID + DOC_SEQUENCE_ID — the composite business-key candidate enforced by the unique index JG_ZZ_VAT_DOC_SEQUENCES_U2, guaranteeing that a given register cannot be linked twice to the same sequence.
• CREATED_BY / CREATION_DATE — standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — standard WHO columns recording the last modifying user and timestamp.
• LAST_UPDATE_LOGIN — the login identifier associated with the most recent change.

The surrogate key provides stable row identity for referential use, while the unique composite index expresses the true business rule governing sequence assignment.

Common Use Cases and Queries

Typical use cases center on VAT reporting and document-number audit. A reporting query joins this table to FND_DOCUMENT_SEQUENCES to retrieve the sequence name and current value associated with a register:

• Locating all sequences for a register: SELECT DOC_SEQUENCE_ID FROM JG_ZZ_VAT_DOC_SEQUENCES WHERE VAT_REGISTER_ID = :p_register_id;
• Reverse lookup of the register owning a sequence: SELECT VAT_REGISTER_ID FROM JG_ZZ_VAT_DOC_SEQUENCES WHERE DOC_SEQUENCE_ID = :p_sequence_id;
• Audit extracts joining to JG_ZZ_VAT_REGISTERS_B for register metadata and to FND_DOCUMENT_SEQUENCES for numbering configuration.
• Reconciliation checks confirming every VAT register has at least one assigned sequence, or validating duplicate assignments via the U2 index.

Because document sequences are a controlled, audited numbering mechanism, extraction queries should treat this table as read-only reference data.

Related Objects

• JG_ZZ_VAT_REGISTERS_B — joined via VAT_REGISTER_ID; parent register definition.
• FND_DOCUMENT_SEQUENCES — joined via DOC_SEQUENCE_ID; Oracle Applications document sequence definition.
• JG_ZZ_VAT_DOC_SEQUENCES_PK — primary key constraint on VAT_DOC_SEQUENCE_ID.
• JG_ZZ_VAT_DOC_SEQUENCES_U1 — unique index on VAT_DOC_SEQUENCE_ID.
• JG_ZZ_VAT_DOC_SEQUENCES_U2 — unique business-key index on VAT_REGISTER_ID, DOC_SEQUENCE_ID.
• FND_DOC_SEQUENCE_ASSIGNMENTS — related document-sequence assignment metadata used alongside this link table in sequencing configuration.
• JG_ZZ_VAT_REGISTERS_TL — translated register names usable in joined reporting.