Search Results from_uom_code




Overview
Explore in AI Chat

Overview

APPS.MSD_SR_UOM_CONVERSIONS_V is a reporting and integration view in Oracle E-Business Suite that consolidates unit-of-measure (UOM) conversion relationships across item-specific, item-independent, and class-based conversion definitions. In the Oracle EBS 12.1.1 and 12.2.2 environments, this view serves as a normalized source for downstream ETRM (Enterprise Transaction Repository Model) and Supply Chain Intelligence / Demand Planning style extractions that require a unified picture of how quantities convert from one UOM to another.

The defining characteristic of the view is its three-way UNION ALL-style structure, which merges distinct conversion semantics into a single result set. The result is a consolidated dataset exposing the source UOM class (FROM_UOM_CLASS), target UOM class (TO_UOM_CLASS), the corresponding UOM codes, the conversion rate, and a base UOM indicator. Because it unifies conversions that originate from MTL_UOM_CONVERSIONS with those held in MTL_UOM_CLASS_CONVERSIONS, the view is especially valuable where conversion logic spans both intra-class and inter-class definitions.

Underlying Base Objects

The view is defined over four documented base objects:

  • MTL_UNITS_OF_MEASURE (synonym) — provides UOM class and UOM code metadata, including the base_uom_flag used to identify the base UOM within a class.
  • MTL_UOM_CONVERSIONS (synonym) — supplies item-specific and item-independent conversion rates keyed by inventory_item_id and uom_code.
  • MTL_UOM_CLASS_CONVERSIONS (synonym) — supplies conversions that cross UOM class boundaries, including from_uom_class and to_uom_class.
  • MSD_SR_UTIL (package) — supplies the MSD_SR_UTIL.item function used to derive a concatenated item identifier from the inventory item ID.

The first UNION branch joins MTL_UOM_CONVERSIONS to MTL_UNITS_OF_MEASURE on the same UOM class, restricting to item-specific rows (inventory_item_id != 0). The second branch handles item-independent conversions (inventory_item_id = 0) within a class. The third branch reads MTL_UOM_CLASS_CONVERSIONS for item-specific, cross-class conversions, setting base_uom_flag to 'Y'.

Key Columns

  • FROM_UOM_CLASS — the UOM class of the source unit. This is the column most frequently referenced when filtering by from_uom_class.
  • TO_UOM_CLASS — the UOM class of the target unit; equal to FROM_UOM_CLASS for intra-class conversions.
  • FROM_UOM_CODE / TO_UOM_CODE — the specific UOM codes being converted.
  • CONVERSION_RATE — the multiplicative factor to convert the FROM UOM quantity into the TO UOM quantity.
  • BASE_UOM_FLAG — indicates whether the row originates from a base-UOM or class-crossing conversion path.
  • SR_ITEM_PK — the inventory item primary key; zero for item-independent conversions.
  • ITEM — concatenated item descriptor produced by MSD_SR_UTIL.item.

Common Use Cases and Queries

A typical query filters by source UOM class to enumerate all outgoing conversion relationships:

  • SELECT from_uom_class, to_uom_class, from_uom_code, to_uom_code, conversion_rate FROM apps.msd_sr_uom_conversions_v WHERE from_uom_class = 'Weight';
  • Item-specific conversion lookups join on SR_ITEM_PK to isolate conversions applicable to a single item.
  • Cross-class reporting filters WHERE from_uom_class <> to_uom_class to surface only inter-class definitions sourced from MTL_UOM_CLASS_CONVERSIONS.
  • Integration extractors use the view as a staging source when loading conversion dimensions into planning or analytics schemas.

Because the view is a UNION of distinct conversion sources, queries should account for potential duplicate conversion pairs and apply appropriate DISTINCT or aggregation logic where a single authoritative rate per pair is required.