Results for “jai_rgm_doc_seq_dtls”

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

Overview

JAI_RGM_DOC_SEQ_DTLS is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product family. It stores the document-level detail rows that drive generation of VAT invoice numbers for Document Setup configurations. In practice, this table acts as the working ledger for number sequences assigned to specific document classes, holding the running current number alongside the configured prefix, start number, and end number for each sequence line.

The table is a child of JAI_RGM_DOC_SEQ_HDRS through the foreign key column RGM_DOCUMENT_SEQ_ID, meaning each detail row belongs to a single sequence header. The documented unique index JAI_RGM_DOC_SEQ_DTLS_PK on RGM_DOCUMENT_SEQ_DTL_ID establishes the surrogate primary key. Under a Data Vault modeling heuristic, this object is classified as satellite-leaning: it carries descriptive and state-bearing attributes (numbers, prefixes, class identifiers) attached to a parent header key, rather than introducing new independent business entities or many-to-many relationships. This classification is offered as a modeling suggestion, not as a statement of Oracle's internal design intent.

Key Information Stored

The documented physical schema exposes 14 columns in Oracle EBS 12.2.2. The columns most relevant to functional and reporting work are:

• RGM_DOCUMENT_SEQ_DTL_ID — surrogate primary key of the row, defined by the unique index JAI_RGM_DOC_SEQ_DTLS_PK.
• RGM_DOCUMENT_SEQ_ID — foreign key to JAI_RGM_DOC_SEQ_HDRS, linking the detail line to its owning sequence header.
• DOCUMENT_CLASS — the document class the sequence applies to, distinguishing the type of VAT document being numbered.
• DOCUMENT_CLASS_TYPE_ID — identifier qualifying the document class type associated with the sequence line.
• START_NUMBER — the configured starting value for the sequence.
• CURRENT_NUMBER — the current position of the sequence, representing the last or next number issued depending on processing logic; this is the most operationally sensitive column.
• END_NUMBER — the configured upper bound of the sequence range.
• PREFIX — the alphanumeric prefix prepended to the generated document number.

Standard EBS audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the last supporting optimistic locking in the OAF framework. The business-key candidates documented are limited to the primary key column; no additional unique index is recorded in the supplied metadata, so DOCUMENT_CLASS and DOCUMENT_CLASS_TYPE_ID should be treated as descriptive qualifiers rather than guaranteed unique keys.

Common Use Cases and Queries

The principal use case is auditing and troubleshooting VAT invoice number allocation. Because CURRENT_NUMBER advances as invoices are generated, reconciling gaps or duplicates between the sequence configuration and issued documents is a frequent activity. A typical query joins the detail table to its header to retrieve the full sequence definition for a given document class:

• Reporting the current sequence position per document class by selecting DOCUMENT_CLASS, PREFIX, START_NUMBER, CURRENT_NUMBER, and END_NUMBER.
• Detecting sequences approaching exhaustion by comparing CURRENT_NUMBER against END_NUMBER.
• Reconciling invoice numbers issued against the sequence table during period-close or statutory audit, joining the parent header on RGM_DOCUMENT_SEQ_ID.
• Reviewing configuration changes via LAST_UPDATE_DATE and LAST_UPDATED_BY to establish an audit trail of who adjusted sequence parameters.

Queries should generally filter on RGM_DOCUMENT_SEQ_ID or DOCUMENT_CLASS to avoid full scans, since the documented access path centers on the primary key and the header foreign key.

Related Objects

The most significant related object is the parent header table, which owns the detail rows:

• JAI_RGM_DOC_SEQ_HDRS — joined via JAI_RGM_DOC_SEQ_DTLS.RGM_DOCUMENT_SEQ_ID = JAI_RGM_DOC_SEQ_HDRS.RGM_DOCUMENT_SEQ_ID; this is the only foreign key relationship documented for this table.
• JA schema localization setup and VAT invoicing components — the Document Setup configuration layer and invoice number generation logic that consume the prefix, start, current, and end number values held here.
• JAI_RGM_DOC_SEQ_DTLS_PK — the unique index enforcing row identity on RGM_DOCUMENT_SEQ_DTL_ID.

Because the supplied metadata documents a single foreign key, the relationship surface is narrow; consumers outside the JA localization number-sequence setup are not directly evidenced. Reports or extracts that enumerate document sequences should therefore be built on the header-to-detail join described above, treating the detail table as the attribute-bearing satellite of the header key.