Results for “registration_id”

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

Overview

JAI_RGM_REGISTRATIONS is a table in the JA (Asia/Pacific Localizations) product schema, owned by JA and marked VALID in Oracle EBS 12.1.1 and 12.2.2. Its documented description is concise: it "stores the regime attribute information." In practice, this table serves as the central registry of regime-related registrations and their associated attributes, capturing the identifiers, types, coded values, rates, and hierarchical relationships that describe how a party or entity is registered under a given regime. It is a core component of the regime and fiscal localization functionality delivered for Asia/Pacific jurisdictions.

From a dimensional modeling perspective, the heuristic Data Vault classification supplied with the metadata suggests this table is hub-leaning. It carries a single-column surrogate primary key (REGISTRATION_ID) and several foreign key references outward to definition and party-registration tables, which is consistent with a hub entity that anchors related links and satellites. This classification is a modeling suggestion only; the table also contains descriptive attribute columns that in a formal Data Vault design would typically be split into satellites.

Key Information Stored

The table is documented with 15 columns. The most significant are:

• REGISTRATION_ID — the surrogate primary key, enforced by the unique index JAI_RGM_REGISTRATIONS_PK. This is the only documented unique index and therefore the sole business-key candidate, though it functions as a system-generated identifier rather than a natural business key.
• REGIME_ID — foreign key to JAI_RGM_DEFINITIONS, identifying the regime under which the registration is held.
• PARENT_REGISTRATION_ID — self-referencing foreign key to JAI_RGM_REGISTRATIONS, enabling parent/child or hierarchical registration structures.
• REGISTRATION_TYPE — classifies the kind of registration.
• ATTRIBUTE_SEQUENCE — ordinal position for multiple attribute entries.
• ATTRIBUTE_TYPE_CODE and ATTRIBUTE_CODE — coded descriptors for the attribute being recorded.
• ATTRIBUTE_VALUE — the value assigned to the attribute.
• RATE — a numeric rate associated with the registration.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include regime compliance reporting, hierarchy traversal of nested registrations, and joining registrations to party-level registration data for tax and localization reporting. A representative query retrieves all registrations for a regime:

• SELECT r.REGISTRATION_ID, r.REGISTRATION_TYPE, r.ATTRIBUTE_CODE, r.ATTRIBUTE_VALUE, r.RATE FROM JA.JAI_RGM_REGISTRATIONS r WHERE r.REGIME_ID = :regime_id ORDER BY r.ATTRIBUTE_SEQUENCE;
• Hierarchy resolution: SELECT c.REGISTRATION_ID, c.PARENT_REGISTRATION_ID FROM JA.JAI_RGM_REGISTRATIONS c CONNECT BY PRIOR c.REGISTRATION_ID = c.PARENT_REGISTRATION_ID START WITH c.PARENT_REGISTRATION_ID IS NULL;
• Party linkage: SELECT p.REGISTRATION_ID, r.ATTRIBUTE_VALUE FROM JA.JAI_RGM_PARTY_REGNS p JOIN JA.JAI_RGM_REGISTRATIONS r ON p.REGISTRATION_ID = r.REGISTRATION_ID;

Related Objects

The metadata documents the following principal relationships:

• JAI_RGM_DEFINITIONS — referenced via REGIME_ID; supplies the regime definition for each registration.
• JAI_RGM_REGISTRATIONS (self) — referenced via PARENT_REGISTRATION_ID; supports nested hierarchies.
• JAI_RGM_PARTY_REGNS — references this table via REGISTRATION_ID, linking registrations to parties.
• JAI_RGM_TERM_ASSIGNS — references this table via REGIME_REGNO, associating term assignments with registrations.

These four relationships define the object's primary integration surface within the JA regime management model.