Search Results jai_rgm_party_regns




Overview
Explore in AI Chat

Overview

The JAI_RGM_PARTY_REGNS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the JA (Asia/Pacific Localizations) product module. It functions as a junction or detail table within the regime management framework, designed to store organization-specific registration details for a given tax or regulatory regime. As the official description states, it holds "Only Organization specific registrations for regime." Its primary role is to link a party (an organization) defined in the JAI_RGM_PARTIES table with one or more specific registration records from the JAI_RGM_REGISTRATIONS table, thereby establishing which registrations are applicable to a particular legal entity or operating unit under a defined regime.

Key Information Stored

The table's structure centers on foreign key relationships that define its purpose. The primary key is REGIME_ORG_DET_ID, a unique identifier for each record. The two critical foreign key columns establish the essential links: REGIME_ORG_ID references the JAI_RGM_PARTIES table to identify the specific organization or party within the regime, and REGISTRATION_ID references the JAI_RGM_REGISTRATIONS table to specify the exact registration detail applicable to that party. While the provided metadata does not list all columns, this design implies the table likely stores attributes pertinent to the association itself, such as effective start and end dates for the registration's applicability to the party, status flags, and potentially override attributes. The data is fundamental for determining the precise regulatory obligations and identifiers (like tax registration numbers) for each legal entity.

Common Use Cases and Queries

This table is central to localization reports and processes that require a clear view of an organization's legal registrations. A common use case is generating a compliance report listing all active registrations for a specific legal entity. Another is during transaction tax calculation, where the system may reference this table to validate if a party has the proper registration for a given tax regime. A typical analytical query would join this table to its parent tables to retrieve a comprehensive registration summary.

  • Sample Query for Party Registration Details:
    SELECT pr.regime_org_det_id, p.party_name, r.registration_number, r.registration_type
    FROM jai_rgm_party_regns pr,
    jai_rgm_parties p,
    jai_rgm_registrations r
    WHERE pr.regime_org_id = p.regime_org_id
    AND pr.registration_id = r.registration_id
    AND p.party_id = :p_legal_entity_id;
  • Data Validation: SQL scripts may check for orphaned records or validate the integrity of the regime-party-registration relationships.

Related Objects

JAI_RGM_PARTY_REGNS is a dependent table with strong referential integrity ties to two primary master tables, as defined by its foreign keys.

  • JAI_RGM_PARTIES: This is the parent table for the REGIME_ORG_ID foreign key. It defines the organizations or parties that exist within a regime.
  • JAI_RGM_REGISTRATIONS: This is the parent table for the REGISTRATION_ID foreign key. It serves as the master list of all possible registration types and details within the localization setup.

Given its function, this table is also likely referenced by various localization-specific views, forms, and APIs (potentially within the JAI or JA* prefixes) that handle tax registration, regulatory reporting, and entity compliance data for Asia/Pacific countries.