Search Results conv1_2

Overview

APPS.MTL_UOM_CONVERSIONS_VIEW is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that resolves the effective unit-of-measure (UOM) conversion factor between an item's primary unit of measure and any other unit of measure within the same or a related UOM class. Rather than relying on a single conversion row, the view synthesizes conversions from item-specific definitions, global (item-agnostic) definitions, and UOM class conversions, applying date-based enablement and disablement logic to determine the currently valid rate.

The view is commonly used by inventory, order management, purchasing, and manufacturing reporting where quantities entered in an alternate UOM must be normalized to the item primary UOM (or vice versa). It is also referenced by integrations and custom concurrent programs that require a reliable, item-level UOM conversion table without duplicating the intricate prioritization rules hard-coded in Oracle's UOM conversion engine.

Underlying Base Objects

The view is defined over the following documented base objects:

• MTL_SYSTEM_ITEMS_B (SYNONYM) – Supplies INVENTORY_ITEM_ID, ORGANIZATION_ID, PRIMARY_UNIT_OF_MEASURE, and PRIMARY_UOM_CODE, anchoring each row to a specific item and organization.
• MTL_UNITS_OF_MEASURE_VL (VIEW) – Joined twice as UOM and UOM2 to retrieve the UOM_CLASS and UOM_CODE for the source (primary) and target units of measure.
• MTL_UOM_CLASS_CONVERSIONS (SYNONYM) – Referenced as CLASS; provides the class-to-class conversion rate when the item and target UOMs reside in different UOM classes. Its DISABLE_DATE participates in the validity check.
• MTL_UOM_CONVERSIONS (SYNONYM) – Referenced three times as CONV1, CONV2, and CONV1_2. CONV1 and CONV1_2 hold item-specific conversions for the primary UOM; CONV2 holds the conversion for the target UOM. The pseudo-key inventory_item_id = 0 on CONV1_2 designates the global, item-independent conversion.

The joins use outer-join syntax (+) and DECODE expressions to select item-specific conversions when present, falling back to global conversions when an item-level row does not exist or is disabled.

Key Columns

• INVENTORY_ITEM_ID – Identifier of the item to which the conversion applies.
• ORGANIZATION_ID – Organization context for the item definition.
• PRIMARY_UNIT_OF_MEASURE / PRIMARY_UOM_CODE – The item's primary UOM and its internal code.
• UOM_CLASS – UOM class of the primary unit of measure (from UOM).
• UNIT_OF_MEASURE / UOM_CODE (UOM2) – The target (alternate) unit of measure and its code.
• CONV2.UOM_CLASS – UOM class of the target unit of measure.
• Conversion rate (expression) – The computed factor derived from CONV1/CONV1_2/CONV2 and, when classes differ, the CLASS.CONVERSION_RATE. The final column is the effective rate that converts between the primary and target UOMs.

Common Use Cases and Queries

Typical scenarios include converting on-hand quantities, order quantities, or transaction quantities from the item primary UOM to a reporting UOM, or validating that a requested conversion exists for a given item and organization.

Sample query:

SELECT inventory_item_id,
       organization_id,
       primary_uom_code,
       uom_code,
       conversion_rate
FROM   apps.mtl_uom_conversions_view
WHERE  inventory_item_id = :p_item_id
AND    organization_id   = :p_org_id;

Integration programs frequently join this view to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID, restricting to a specific UOM_CODE to retrieve a single, deterministic rate. Because the view resolves both item-specific and global conversions with date validity, it is the preferred source over querying MTL_UOM_CONVERSIONS directly when consistent, effective conversion factors are required.