Search Results mtl_uom_class_conversions_u1

Overview

INV.MTL_UOM_CLASS_CONVERSIONS is a core Oracle E-Business Suite inventory table that stores unit-of-measure (UOM) conversion definitions between the base unit of an item's base UOM class and the base unit of a secondary UOM class. Because an item can be transacted in units belonging to different classes (for example, weight, volume, or count), this table provides the master conversion factor that allows Oracle Inventory to translate quantities from the item's primary base UOM into the base unit of any other class, and vice versa. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the INV schema, exposed at design time as FND Design Data INV.MTL_UOM_CLASS_CONVERSIONS.

The documented, mined relationship data classifies this object heuristically as standalone in a Data Vault sense—meaning it functions largely independently as a reference/conversion table rather than participating in a natural hub-link-satellite chain with an obvious business hub. Its primary key, MTL_UOM_CLASS_CONVERSIONS_PK, is composed of (INVENTORY_ITEM_ID, FROM_UNIT_OF_MEASURE, TO_UNIT_OF_MEASURE).

Key Information Stored

The table contains 18 documented columns. The most significant include:

• INVENTORY_ITEM_ID — Inventory item identifier; part of the composite primary key and of every unique index. It ties each conversion to a specific item, meaning conversions are item-specific rather than global.
• FROM_UNIT_OF_MEASURE and FROM_UOM_CODE — The base UOM of the item's base class and its short code; FROM_UNIT_OF_MEASURE is part of the primary key.
• FROM_UOM_CLASS — The item's base class, derived from MTL_UNITS_OF_MEASURE.
• TO_UNIT_OF_MEASURE and TO_UOM_CODE — The base unit (and short code) of the target class to which the conversion is defined; TO_UNIT_OF_MEASURE completes the primary key.
• TO_UOM_CLASS — The class to which the conversion is defined, also derived from MTL_UNITS_OF_MEASURE.
• CONVERSION_RATE — The numeric rate converting the item's class base unit into the target class base unit; this is the operative factor used in quantity calculations.
• DISABLE_DATE — The date after which the defined inter-class conversion can no longer be used, enabling time-bounded conversion validity.

Regarding business-key candidates, three unique indexes are documented. MTL_UOM_CLASS_CONVERSIONS_U1 enforces uniqueness on (INVENTORY_ITEM_ID, TO_UNIT_OF_MEASURE), U2 on (INVENTORY_ITEM_ID, TO_UOM_CODE), and U3 on (TO_UOM_CLASS, INVENTORY_ITEM_ID). Standard Who columns—LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE—provide audit trail and concurrent-program provenance.

Common Use Cases and Queries

Typical scenarios include resolving a quantity entered in a non-base class UOM into the item's primary UOM, validating that a desired conversion exists and is not expired, and reporting the conversion matrix per item. A representative query retrieves active conversions for an item:

• SELECT inventory_item_id, from_unit_of_measure, to_unit_of_measure, conversion_rate FROM mtl_uom_class_conversions WHERE inventory_item_id = :item AND (disable_date IS NULL OR disable_date > SYSDATE);

Reporting use cases include auditing which items carry inter-class conversions, detecting conversions approaching or past their DISABLE_DATE, and joining conversion rates to on-hand or transaction data to normalize mixed-class quantities for analytical reporting. Because U1 and U2 enforce uniqueness on INVENTORY_ITEM_ID paired with TO_UNIT_OF_MEASURE and TO_UOM_CODE respectively, queries filtering by those combinations benefit from index range scans on APPS_TS_TX_IDX.

Related Objects

The table depends conceptually and via derivation on UOM master data and integrates with item and transaction entities. The most significant related objects include:

• MTL_UNITS_OF_MEASURE — The source of FROM_UOM_CLASS and TO_UOM_CLASS; join on UOM_CODE/UOM_CLASS to resolve class descriptions.
• MTL_SYSTEM_ITEMS_B — The item definition master; join on INVENTORY_ITEM_ID to obtain the item's primary UOM and attributes.
• MTL_UOM_CONVERSIONS — Stores standard intra-class UOM conversions, complementing the inter-class conversions held here.
• MTL_TRANSACTIONS and transaction interfaces — Consumption points where conversion rates are applied to normalize transaction quantities.
• MTL_ONHAND_QUANTITIES — Reporting joins that translate on-hand balances recorded in the base UOM into alternate classes.
• INV_UOM_PUB / UOM conversion APIs — Programmatic entry points (such as INV_UOM_PUB) that read and apply conversion rates at runtime.