Results for “uom_code”

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

Overview

The JAI_CMN_UOM_DTLS_V view is a public Oracle EBS database object owned by the APPS schema and defined within the JA — Asia/Pacific Localizations product family. It exposes a consolidated list of valid units of measure (UoM) as they apply to inventory items, mapping each item's alternate and primary UoMs into a single reporting surface. In Oracle EBS 12.1.1 and 12.2.2 the view carries a status of VALID, meaning it is compiled and available for downstream use by localization logic and custom reporting.

The view is primarily leveraged by Asia/Pacific localization features that require a normalized enumeration of item-to-UoM relationships, including transactional forms, GST/regional reporting extracts, and integration interfaces. Because it merges UoM data across item-level conversions, class-level conversions and the item master itself, it removes the need for report authors and interface developers to re-implement that consolidation logic themselves.

Underlying Base Objects

The view is defined over three documented base objects, each accessed through APPS synonyms:

• MTL_UOM_CONVERSIONS — provides item-specific alternate UoM definitions. Only rows where DISABLE_DATE IS NULL or DISABLE_DATE+1 > SYSDATE are included, filtering out inactive conversions.
• MTL_UOM_CLASS_CONVERSIONS — supplies class-level UoM conversions, subjected to the same disable-date filter, with TO_UNIT_OF_MEASURE and TO_UOM_CODE projected as the UoM output.
• MTL_SYSTEM_ITEMS — contributes the item's PRIMARY_UNIT_OF_MEASURE and PRIMARY_UOM_CODE, in this case carrying a concrete ORGANIZATION_ID.

The first two sources are combined via UNION ALL, with ORGANIZATION_ID set to TO_NUMBER(NULL) because conversions at that level are not organization-qualified. That intermediate result is then unioned with the MTL_SYSTEM_ITEMS query, and the whole statement is wrapped in an outer SELECT DISTINCT to eliminate duplicate UoM/ item combinations.

Key Columns

• UNIT_OF_MEASURE — the unit of measure name (for example Each, Kilograms), either the conversion UoM or the item primary UoM.
• UOM_CODE — the short internal code corresponding to the unit of measure, used as the stable key in interfaces.
• INVENTORY_ITEM_ID — the item for which the UoM applies; the primary join key back to MTL_SYSTEM_ITEMS.
• ORGANIZATION_ID — populated only for primary item records sourced from MTL_SYSTEM_ITEMS; it is NULL for rows derived from the two conversion tables, signalling a non-organization-specific conversion.

Common Use Cases and Queries

Typical uses include validating the set of UoMs available to an item before an order or receipt, populating LOVs in localization forms, and driving conversion lookups in APAC reporting extracts. The NULL ORGANIZATION_ID on conversion rows is important: consumers should treat such rows as globally applicable rather than organization-neutral duplicates.

A representative query returning all valid UoMs for a specific item is:

• SELECT UNIT_OF_MEASURE, UOM_CODE, ORGANIZATION_ID FROM JAI_CMN_UOM_DTLS_V WHERE INVENTORY_ITEM_ID = :item_id ORDER BY UOM_CODE;
• SELECT DISTINCT UOM_CODE, UNIT_OF_MEASURE FROM JAI_CMN_UOM_DTLS_V ORDER BY UOM_CODE; — used to build a UoM LOV across all items.
• SELECT v.INVENTORY_ITEM_ID, v.UOM_CODE FROM JAI_CMN_UOM_DTLS_V v WHERE v.ORGANIZATION_ID = :org_id; — restricted to primary item UoMs for a given organization.

Because the view applies a live SYSDATE filter against disable dates, results are time-sensitive and should not be cached across long-running sessions.