Search Results jai_rgm_doc_seq_dtls




Overview
Explore in AI Chat

Overview

The table JAI_RGM_DOC_SEQ_DTLS is a core data object within the JA (Asia/Pacific Localizations) product of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is specifically designed to support localized regulatory requirements for Value Added Tax (VAT) invoicing. As indicated by its description, this table stores document details that are essential for generating the VAT invoice number as part of the Document Setup functionality. It operates as a detail table, storing specific configuration rules or parameters that are governed by a higher-level header record. Its primary role is to ensure that generated tax invoice numbers comply with regional statutory formats and sequencing rules mandated in various Asia/Pacific jurisdictions.

Key Information Stored

The table's structure is centered around storing configuration details for document sequencing. The primary key is the column RGM_DOCUMENT_SEQ_DTL_ID, which uniquely identifies each detail record. A critical foreign key column is RGM_DOCUMENT_SEQ_ID, which links each detail line to its parent header configuration in the JAI_RGM_DOC_SEQ_HDRS table. While the full column list is not provided in the metadata, typical data stored in such a detail table would include elements like sequence prefixes, suffixes, starting numbers, reset rules (e.g., yearly, monthly), applicable document types (like Commercial Invoice, Debit Memo), and potentially the specific segments of the invoice number format controlled by that detail line. This data collectively defines the algorithm for generating sequential, compliant VAT invoice numbers.

Common Use Cases and Queries

The primary use case is the background generation of a VAT invoice number during transaction posting, such as the completion of an invoice in Receivables or a transaction in Order Management. System administrators may query this table to audit or troubleshoot document sequencing setup. A common reporting query would join the detail lines to their header to review the complete setup for a specific document type or legal entity. For example:

  • Identifying all detail rules for a specific header: SELECT * FROM jai_rgm_doc_seq_dtls dtls WHERE dtls.rgm_document_seq_id = <HEADER_ID> ORDER BY dtls.rgm_document_seq_dtl_id;
  • Analyzing the full document sequence setup: SELECT hdr.document_sequence_name, dtls.* FROM jai_rgm_doc_seq_hdrs hdr, jai_rgm_doc_seq_dtls dtls WHERE hdr.rgm_document_seq_id = dtls.rgm_document_seq_id;

Direct data manipulation in this table by users is uncommon, as setup is typically performed via the EBS application's dedicated localization forms.

Related Objects

JAI_RGM_DOC_SEQ_DTLS has a direct and dependent relationship with the JAI_RGM_DOC_SEQ_HDRS table, which stores the master definition for a document sequence rule. The relationship is enforced by a foreign key constraint where JAI_RGM_DOC_SEQ_DTLS.RGM_DOCUMENT_SEQ_ID references the primary key of JAI_RGM_DOC_SEQ_HDRS. This establishes a one-to-many relationship, where one header record governs multiple detail lines. The table is also intrinsically linked to the core EBS document sequencing engine and the transactional modules (like AR, OE) that consume the generated VAT invoice numbers, though these are typically accessed via public APIs rather than direct table references.