Results for “term_assignment_id”

10 results




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

Overview

JAI_RGM_TERM_ASSIGNS is a transaction and reference intersection table owned by the JA schema and delivered as part of the Oracle E-Business Suite Asia/Pacific Localizations module. Its purpose, per the ETRM documentation, is to store term assignments that default at various hierarchical levels within a regime framework. The table acts as the operational link that binds a defined term to a specific registration, organization, location, or regime context, allowing the localization engine to resolve which term should apply to a given transaction or item classification.

The relationship metadata classifies this object heuristically as a link table within a Data Vault modeling scheme. Consistent with that classification, the table contains no natural descriptive payload of its own beyond assignment metadata; instead it holds a set of foreign key references that connect independent hubs such as regimes, registrations, terms, organizations, and locations. This makes it a pure association object whose grain is one assignment row per term-to-context combination.

Key Information Stored

The table is documented with 14 physical columns. The surrogate primary key is TERM_ASSIGNMENT_ID, enforced through the JAI_RGM_TERM_ASSIGNS_PK index. This identifier is system-generated and carries no business meaning; it exists solely to give each assignment row a stable unique handle.

The business-key candidates are captured by the unique index JAI_RGM_TERM_ASSIGNS_UK1, which is composed of REGIME_ID, REGIME_ITEM_CLASS, REGIME_REGNO, ORGANIZATION_ID, ORGANIZATION_TYPE, and LOCATION_ID. Together these columns define the hierarchical context in which an assignment is valid — the regime, the item classification within that regime, the registration number, and the organization or location to which the assignment defaults.

Common Use Cases and Queries

Typical scenarios involve resolving the default term for a transaction based on registration, organization, and location. A reporting query might join assignments to terms and registrations to present a complete view of which term applies where:

SELECT a.term_assignment_id,
       t.term_name,
       a.regime_regno,
       a.regime_item_class,
       a.organization_id,
       a.location_id
FROM   ja.jai_rgm_term_assigns a,
       ja.jai_rgm_terms t
WHERE  a.term_id = t.term_id
AND    a.regime_regno = :regime_regno;

Filtering by REGIME_ID and ORGANIZATION_TYPE supports hierarchy-driven lookups, while joins to HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL produce human-readable organization and location names for reporting. Audit queries using LAST_UPDATE_DATE are common when reconciling configuration changes.

Related Objects

  • JAI_RGM_TERMS — joined on TERM_ID; provides the term definition.
  • JAI_RGM_DEFINITIONS — joined on REGIME_ID; provides the regime definition.
  • JAI_RGM_REGISTRATIONS — joined on REGIME_REGNO; provides registration details.
  • HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID; provides organization hierarchy.
  • HR_LOCATIONS_ALL — joined on LOCATION_ID; provides location details.