Search Results jai_rgm_doc_seq_hdrs




Overview
Explore in AI Chat

Overview

The JAI_RGM_DOC_SEQ_HDRS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the header or master table for configuring document sequencing rules specific to various tax or regulatory regimes. The table's primary role is to establish the foundational link between a specific regime, an organization (party), and a physical location (party site), thereby defining the scope for which a unique set of document numbering sequences will be applied. This setup is critical for compliance with regional statutory requirements that mandate specific formats and sequences for documents like tax invoices.

Key Information Stored

The table stores the key identifiers that define the context for a document sequence setup. Its primary column is RGM_DOCUMENT_SEQ_ID, which is the unique system-generated primary key for each header record. The REGIME_ID is a foreign key that links to the JAI_RGM_DEFINITIONS table, identifying the specific tax or legal regime for which the sequencing rules are defined. The PARTY_ID, typically referencing HR_ALL_ORGANIZATION_UNITS, identifies the legal entity or organization unit. The PARTY_SITE_ID, referencing HR_LOCATIONS_ALL, pinpoints the specific operational or legal address of the party. Together, these columns create a unique combination that determines the applicable document sequencing rules for a given regime, organization, and location.

Common Use Cases and Queries

A primary use case is the setup and maintenance of compliant document numbering for transactional documents like invoices within a specific country's localization. Administrators use this table to define which sequence applies to a given entity at a specific site. Common reporting and validation queries involve joining this header table with its detail lines (JAI_RGM_DOC_SEQ_DTLS) to review all configured sequences. For instance, to audit all document sequence setups for a particular regime, a query would join on REGIME_ID to JAI_RGM_DEFINITIONS and to the detail table. Troubleshooting often involves a SQL check to ensure a header record exists for a given combination of organization, location, and regime before transactions can be successfully completed.

Related Objects

The JAI_RGM_DOC_SEQ_HDRS table is central to a tightly defined relational structure within the JA module. Its documented relationships are as follows:

  • Referenced by Foreign Key: The table JAI_RGM_DOC_SEQ_DTLS references this header via the column JAI_RGM_DOC_SEQ_DTLS.RGM_DOCUMENT_SEQ_ID, creating a master-detail relationship where the details store the actual sequence definitions (e.g., type, format, next number).
  • References Foreign Tables: This table itself references three key master tables:
    • JAI_RGM_DEFINITIONS via JAI_RGM_DOC_SEQ_HDRS.REGIME_ID
    • HR_ALL_ORGANIZATION_UNITS via JAI_RGM_DOC_SEQ_HDRS.PARTY_ID
    • HR_LOCATIONS_ALL via JAI_RGM_DOC_SEQ_HDRS.PARTY_SITE_ID
    These relationships ensure data integrity by tying the document sequence setup to valid regimes, organizations, and addresses within the EBS system.