Search Results jai_rgm_registrations

Overview

The JAI_RGM_REGISTRATIONS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Asia/Pacific Localizations (product JA). It functions as the central repository for storing detailed registration information pertaining to various tax or regulatory regimes. A "regime" represents a specific set of legal or fiscal rules, such as Goods and Services Tax (GST) in India or Value-Added Tax (VAT) in other jurisdictions. This table holds the specific attribute data for each registration instance, enabling businesses to manage and report according to multiple, often hierarchical, regulatory requirements. Its role is critical for ensuring compliance within the localized legal frameworks supported by the JA module.

Key Information Stored

While the provided metadata does not list specific columns beyond key identifiers, the table's structure and relationships indicate the type of critical information it contains. The primary key, REGISTRATION_ID, uniquely identifies each registration record. The REGIME_ID foreign key links the registration to its governing rule set defined in the JAI_RGM_DEFINITIONS table. The PARENT_REGISTRATION_ID column establishes a self-referential hierarchical relationship, allowing for parent-child registration structures (e.g., a central company registration with subordinate branch registrations). Typically, such a table would also store attributes like the registration number, effective dates, status, jurisdiction details, and other regime-specific parameters mandated by local legislation.

Common Use Cases and Queries

This table is central to localization compliance processes. Common use cases include generating tax registration reports for authorities, determining the applicable tax rules for a transaction based on the party and site's registration, and managing the lifecycle of registrations (creation, amendment, inactivation). A frequent reporting requirement is to list all active registrations for a legal entity. A sample SQL pattern to achieve this, joining to the regime definitions for context, would be:

• SELECT r.registration_id, r.registration_number, d.regime_code, d.regime_name FROM jai_rgm_registrations r, jai_rgm_definitions d WHERE r.regime_id = d.regime_id AND r.status = 'ACTIVE' AND SYSDATE BETWEEN r.start_date AND NVL(r.end_date, SYSDATE);

Another common query involves traversing the registration hierarchy to find the ultimate parent registration for a given branch, which can be accomplished using a CONNECT BY query on the PARENT_REGISTRATION_ID column.

Related Objects

The JAI_RGM_REGISTRATIONS table is a nexus within the regime management schema, with documented relationships to several key objects:

• JAI_RGM_DEFINITIONS: The foundational table for regime rules. Joined via JAI_RGM_REGISTRATIONS.REGIME_ID = JAI_RGM_DEFINITIONS.REGIME_ID.
• JAI_RGM_PARTY_REGNS: Links parties (legal entities) to their specific registrations. This table references JAI_RGM_REGISTRATIONS via JAI_RGM_PARTY_REGNS.REGISTRATION_ID.
• JAI_RGM_TERM_ASSIGNS: Associates tax terms or conditions with a registration. References this table via JAI_RGM_TERM_ASSIGNS.REGIME_REGNO = JAI_RGM_REGISTRATIONS.REGISTRATION_ID.
• Self-Referential Hierarchy: The table references itself to model parent-child registration relationships via JAI_RGM_REGISTRATIONS.PARENT_REGISTRATION_ID = JAI_RGM_REGISTRATIONS.REGISTRATION_ID.