Results for “unit_of_measure_tl”

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

Overview

The MTL_ITEM_UOMS_VIEW view, owned by the APPS schema in Oracle E-Business Suite, resides within the Inventory (INV) product module. Its documented purpose is to hold the valid units of measure (UOMs) available for items, taking into consideration the conversions that are defined. In practice, the view resolves the relationship between an inventory item, its allowed units of measure configuration, and the conversion rules that govern which UOMs may legitimately be transacted against that item.

Because unit-of-measure eligibility on an item is not stored as a single static value but is derived from the item's ALLOWED_UNITS_LOOKUP_CODE combined with class-level and item-level conversion definitions, this view encapsulates that derivation logic. It serves as a consolidated, query-ready source for reporting, validation, and integration scenarios where the set of permissible UOMs for a given item must be determined without re-implementing the underlying conversion rules.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2 environments and is documented as VALID and available in the APPS schema.

Underlying Base Objects

MTL_ITEM_UOMS_VIEW is defined over the following documented base objects:

• MTL_SYSTEM_ITEMS_B (SYNONYM) — the item master and organization item definitions, providing ORGANIZATION_ID, INVENTORY_ITEM_ID, ALLOWED_UNITS_LOOKUP_CODE, and PRIMARY_UOM_CODE.
• MTL_UNITS_OF_MEASURE (SYNONYM) — the units of measure definition, referenced for UOM class resolution against the item's primary UOM.
• MTL_UNITS_OF_MEASURE_VL (VIEW) — the translated units of measure view, supplying UOM_CODE, UNIT_OF_MEASURE, UNIT_OF_MEASURE_TL, DESCRIPTION, UOM_CLASS, and BASE_UOM_FLAG.
• MTL_UOM_CLASS_CONVERSIONS (SYNONYM) — class-level conversions, used to determine eligible TO_UOM_CODE and TO_UOM_CLASS values that remain active.
• MTL_UOM_CONVERSIONS (SYNONYM) — item-level and standard conversions that drive which UOMs are considered valid for the item.

The view joins these objects through a combination of item identifiers, UOM classes, and conversion definitions, filtered by DISABLE_DATE conditions to exclude inactive conversions and UOMs.

Key Columns

• ORGANIZATION_ID — the inventory organization context for the item.
• INVENTORY_ITEM_ID — the unique identifier of the inventory item.
• UOM_TYPE — the allowed-units lookup classification carried through the query.
• UOM_CODE — the unit of measure code considered valid for the item.
• UNIT_OF_MEASURE — the descriptive unit of measure value.
• UNIT_OF_MEASURE_TL — the translated unit of measure value.
• DESCRIPTION — the UOM description.
• UOM_CLASS — the class to which the UOM belongs.

The DISTINCT clause ensures each organization-item-UOM combination appears once, even when multiple conversion paths satisfy the join conditions.

Common Use Cases and Queries

The view is typically used to present the list of valid UOMs for an item during reporting, data validation, or interface load preparation. A representative query is:

• SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, UOM_CODE, UNIT_OF_MEASURE, UOM_CLASS FROM APPS.MTL_ITEM_UOMS_VIEW WHERE ORGANIZATION_ID = :org AND INVENTORY_ITEM_ID = :item;
• Filtering by UOM_CLASS to limit results to a specific measurement family.
• Joining to MTL_SYSTEM_ITEMS_B or MTL_SYSTEM_ITEMS_TL for item descriptions when building pick lists or validation sets.

Typical scenarios include validating a transaction UOM before insert, populating LOVs in custom forms, and feeding downstream systems with the permissible UOM set for an item.