Results for “regime_code”

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

Overview

The view APPS.JAI_RGM_ORGANIZATIONS_V is a reporting object delivered with the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. It consolidates organizational registration data maintained through the EBS Tax Regime functionality, specifically the Registration and Reporting Management model represented by the JAI_RGM_* tables. The view returns operating units that are formally registered under a given tax regime — for example, a VAT regime — and exposes the registration number and registration type associated with each organization.

Functionally, the view flattens a normalized data model spanning organization definitions, organization classifications, regime definitions, party registration records, and registration attribute values. The result is a single, denormalized row per qualifying organization/regime/registration combination. Because the object is defined with Status: VALID in the APPS schema, it can be queried directly from custom reports, concurrent programs, or integration extracts without requiring additional joins in most cases.

A distinguishing characteristic of this view is the explicit filter on ORGANIZATION_TYPE = 'OU', which restricts output to operating units. The view also applies filters on REGISTRATION_TYPE = 'OTHERS' and ATTRIBUTE_TYPE_CODE = 'PRIMARY', and includes conditional logic keyed on the REGIME_CODE and ATTRIBUTE_CODE values. This means the view is not a generic registration extract; it is purpose-built to answer the question, "which operating units have a primary registration under the applicable regime?"

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view references the following base objects, all accessed through synonyms in the APPS schema:

• HR_ALL_ORGANIZATION_UNITS — provides the organization name and identifier (NAME, ORGANIZATION_ID).
• HR_ORGANIZATION_INFORMATION — supplies the organization classification context; the view constrains on ORG_INFORMATION_CONTEXT = 'CLASS', ORG_INFORMATION1 = 'OPERATING_UNIT', and ORG_INFORMATION2 = 'Y'.
• JAI_RGM_DEFINITIONS — the regime master, supplying REGIME_ID and REGIME_CODE.
• JAI_RGM_PARTIES — party-level registration records, supplying LOCATION_ID and ORGANIZATION_TYPE.
• JAI_RGM_REGISTRATIONS — registration attributes, supplying ATTRIBUTE_VALUE, ATTRIBUTE_CODE, ATTRIBUTE_TYPE_CODE, and REGISTRATION_TYPE.
• JAI_RGM_PARTY_REGNS — party-to-registration associations; the inline view uses a NOT EXISTS subquery against this table for the first UNION ALL branch and an inner join for the second branch.

The inline view (aliased JOR) is constructed from a UNION ALL of two queries: the first selects registration attribute values directly from JAI_RGM_REGISTRATIONS where no party-registration association exists, while the second selects values from JAI_RGM_PARTY_REGNS where such an association does exist. The outer query then joins the inline view back to the HR organization tables on ORGANIZATION_ID and applies the operating-unit classification filter.

Key Columns

• NAME — organization name inherited from HR_ALL_ORGANIZATION_UNITS.
• ORGANIZATION_ID — the operating unit identifier; the primary join key back to HR and to EBS operating unit contexts.
• REGIME_CODE, REGIME_ID — the tax regime (for example, VAT) under which the organization is registered.
• ATTRIBUTE_VALUE — the registration attribute value, typically the registration number itself.
• LOCATION_ID — the location tied to the party registration record.

Although the view text carries ORGANIZATION_TYPE, REGISTRATION_TYPE, REGISTRATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_TYPE_CODE inside the inline view for filtering purposes, only the outer projection list — NAME, ORGANIZATION_ID, REGIME_CODE, REGIME_ID, ATTRIBUTE_VALUE, and LOCATION_ID — is exposed to callers in the delivered definition. This distinction is important when building dependent queries: the organization_type predicate is applied internally and is not selectable from the view as shipped.

Common Use Cases and Queries

Typical usage includes tax registration reporting, operating unit validation during setup, and third-party extracts requiring the registered tax identifier for an operating unit. A representative query returning all VAT registrations follows:

• SELECT organization_id, name, regime_code, attribute_value FROM jai_rgm_organizations_v WHERE regime_code = 'VAT';
• SELECT o.name, o.attribute_value FROM jai_rgm_organizations_v o WHERE o.organization_id = :p_org_id AND o.regime_code = 'VAT';

Because the view is already restricted to primary registrations under the 'OTHERS' registration type for operating units, consumers should not reapply those predicates unless they intend to exclude rows. Reports that must surface multiple regimes or non-primary registrations should query the underlying JAI_RGM_* tables directly rather than this view.