Search Results uom_class




Overview
Explore in AI Chat

Overview

APPS.MSC_UOM_CONVERSIONS_VIEW is a reporting view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema, owned by the APPS account. It exposes unit-of-measure (UOM) conversion relationships for planning items, resolving each inventory item's source UOM against target UOMs and cross-class conversions into a single, query-ready result set. Its principal purpose is to present a computed conversion rate between a base unit of measure and an alternate unit of measure for a given item and organization, calculated dynamically from the underlying conversion definitions rather than being stored as a static value.

Because the view joins item definitions, UOM definitions, item-level conversions, and class-level conversions, it abstracts the considerable complexity of UOM resolution logic. This makes it suitable for planning reports, integration extracts, and diagnostic queries where the effective conversion factor between two UOMs must be determined for a specific item. The presence of the UOM_CODE column — the term the user searched for — places this view squarely in the category of objects used to translate quantities between planning and inventory units.

Underlying Base Objects

The ETRM metadata documents the following base objects, all referenced through synonyms in the APPS schema:

The view therefore sits one layer above the core planning conversion tables, combining item-scoped and class-scoped conversion data. The multiple outer joins and inline subqueries reflect the fallback hierarchy: item-level conversion first, then intra-class and inter-class conversion definitions.

Key Columns

  • INVENTORY_ITEM_ID — Identifier of the planning item for which the conversion applies.
  • ORGANIZATION_ID — The organization context of the item.
  • UOM_CODE — The item's source (base) unit of measure code, taken from MSC_SYSTEM_ITEMS.
  • SR_INSTANCE_ID — Source instance identifier from the system items record, used to distinguish data originating from different source systems.
  • UOM_CLASS — The UOM class associated with the source unit of measure.
  • UNIT_OF_MEASURE — The target unit of measure description/name from the second UOM join.
  • UOM_CODE (UOM2) — The target unit of measure code.
  • UOM_CLASS (CONV2) — The conversion class associated with the target conversion record.
  • Computed conversion rate — A derived expression combining class conversion rate, item conversion rate, and the effective (non-disabled) conversion rate, yielding the factor to convert between the source UOM and target UOM.

Common Use Cases and Queries

Typical uses include validating the effective conversion factor for an item, auditing which target UOMs are available for planning calculations, and joining to planning demand or supply tables to normalize quantities. Because UOM_CODE was the searched term, queries frequently filter or join on it.

A representative query to list conversions for a given item and UOM:

SELECT inventory_item_id, organization_id, uom_code,
       unit_of_measure, uom_class
  FROM apps.msc_uom_conversions_view
 WHERE inventory_item_id = :item_id
   AND uom_code = :uom_code;

A second pattern retrieves all target units available for an item, useful for populating conversion lookups in a planning extract:

SELECT DISTINCT uom_code, unit_of_measure
  FROM apps.msc_uom_conversions_view
 WHERE inventory_item_id = :item_id
   AND organization_id = :org_id;

Because the view applies DISABLE_DATE logic and nested fallback subqueries, results reflect only currently effective conversions. Queries should therefore avoid reimplementing conversion logic and instead rely on the view for consistent, planning-standard conversion rates.