Results for “jai_rgm_doc_seq_hdrs”

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

Overview

JAI_RGM_DOC_SEQ_HDRS is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, categorized under the JA - Asia/Pacific Localizations product family. It stores the header-level setup information for the Document Sequence regime, specifically capturing the regimeidentifier, party_id, and party_site_id context required to configure Legal Document Sequences. This configuration is fundamental to the Asia/Pacific localization requirements for statutory document numbering, enabling organizations to satisfy country-specific regulatory mandates for sequential numbering of legal and fiscal documents.

Under a heuristic Data Vault classification derived from its foreign-key topology, the table presents a satellite-leaning profile. It hangs off the primary regime definition (JAI_RGM_DEFINITIONS) and carries descriptive and effective-dated attributes, which is characteristic of satellite behavior rather than serving as an independent hub or associative link. This classification should be treated as a modeling suggestion rather than a canonical designation.

Key Information Stored

The table comprises 15 documented columns. The most operationally significant are summarized below, distinguishing the surrogate primary key from business-key candidates.

• RGM_DOCUMENT_SEQ_ID — Surrogate primary key, enforced via the unique index JAI_RGM_DOC_SEQ_HDRS_PK. This is the sole documented unique index and therefore the only documented business-key candidate.
• REGIME_ID — Foreign key to JAI_RGM_DEFINITIONS; identifies the legal regime under which the document sequence applies.
• REGISTRATION_NUM — Registration number associated with the document sequence setup.
• PARTY_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS; identifies the legal entity or organization party.
• PARTY_SITE_ID — Foreign key to HR_LOCATIONS_ALL; identifies the specific party site or location.
• ORGANIZATION_TYPE — Classifies the organization for which the sequence is defined.
• FIN_YEAR — The fiscal year to which the document sequence configuration pertains.
• EFFECTIVE_FROM / EFFECTIVE_TO — Date-bounded validity window, supporting effective-dated configuration.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER provide standard EBS audit and optimistic-locking support.

Common Use Cases and Queries

Typical scenarios include resolving the document sequence applicable to a given regime, party, and fiscal year; auditing effective-dated configuration; and joining header configuration to its detail lines. A representative query retrieves active header configuration for a party and year:

• SELECT h.rgm_document_seq_id, h.regime_id, h.party_id, h.party_site_id, h.fin_year FROM ja.jai_rgm_doc_seq_hdrs h WHERE h.party_id = :p_party_id AND h.fin_year = :p_fin_year AND TRUNC(SYSDATE) BETWEEN h.effective_from AND NVL(h.effective_to, SYSDATE).
• Join to detail lines for full setup: SELECT d.* FROM ja.jai_rgm_doc_seq_hdrs h, ja.jai_rgm_doc_seq_dtls d WHERE h.rgm_document_seq_id = d.rgm_document_seq_id AND h.rgm_document_seq_id = :p_id.
• Resolve the governing regime name: SELECT g.* FROM ja.jai_rgm_doc_seq_hdrs h, ja.jai_rgm_definitions g WHERE h.regime_id = g.regime_id.

Reporting use cases center on localization compliance audits, verifying that each party and site has a valid sequence for the fiscal year, and reconciling configuration drift across effective-dated versions.

Related Objects

The following objects are most significant by documented relationship.

• JAI_RGM_DOC_SEQ_DTLS — Child detail table; joined via JAI_RGM_DOC_SEQ_DTLS.RGM_DOCUMENT_SEQ_ID = JAI_RGM_DOC_SEQ_HDRS.RGM_DOCUMENT_SEQ_ID.
• JAI_RGM_DEFINITIONS — Parent regime definition; joined via REGIME_ID.
• HR_ALL_ORGANIZATION_UNITS — Party/organization master; joined via PARTY_ID.
• HR_LOCATIONS_ALL — Party site master; joined via PARTY_SITE_ID.

These relationships establish JAI_RGM_DOC_SEQ_HDRS as the configuration anchor between localization regime definitions, HR organizational data, and the document sequencing details used across JA localization processes.