MTL_UOM_CONVERSIONS
Schema: INVmasterIntra-class UOM conversion rates to each class's base unit — both standard conversions and item-specific overrides, distinguished by the item id
INVENTORY_ITEM_ID = 0 is the standard (item-independent) conversion row; an item-specific row for the same UOM wins over it — Oracle's own conversion logic reads both and prefers the item row. Cross-class conversions live in MTL_UOM_CLASS_CONVERSIONS (later wave). Conversions are global (no org column).
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
6 fields · 2 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVENTORY_ITEM_ID | Item id — 0 marks the standard (item-independent) conversion; an item-specific row wins over it | NUMBER | Key |
| 2 | UOM_CODE | The unit being converted to its class base unit | VARCHAR2 | Key |
| 3 | UNIT_OF_MEASURE | The unit's 25-char name form | VARCHAR2 | |
| 4 | UOM_CLASS | The class the conversion stays within — cross-class conversions live elsewhere | VARCHAR2 | |
| 5 | CONVERSION_RATE | Multiplier from this unit to the class base unit | NUMBER | |
| 6 | DISABLE_DATE | When the conversion was disabled — NULL while active | DATE |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading MTL_UOM_CONVERSIONSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : MTL_UOM_CONVERSIONS — Intra-class UOM conversion rates to each class's base unit — both standard conversions and item-specific overrides, distinguished by the item id
-- Purpose: Column-selected read of MTL_UOM_CONVERSIONS — auto-generated from field metadata
-- Grain : One row per INVENTORY_ITEM_ID + UOM_CODE
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.INVENTORY_ITEM_ID AS "Item id — 0 marks the standard (item-independent) conversion; an item-specific row wins over it",
t.UOM_CODE AS "The unit being converted to its class base unit",
t.UNIT_OF_MEASURE AS "The unit's 25-char name form",
t.UOM_CLASS AS "The class the conversion stays within — cross-class conversions live elsewhere",
t.CONVERSION_RATE AS "Multiplier from this unit to the class base unit",
t.DISABLE_DATE AS "When the conversion was disabled — NULL while active"
FROM <catalog>.<schema>.MTL_UOM_CONVERSIONS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- AND t.UOM_CODE = '<UOM_CODE>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.INVENTORY_ITEM_ID;5 parameters not filled: <catalog>, <schema>, <INVENTORY_ITEM_ID>, <UOM_CODE>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MTL_UOM_CONVERSIONS.UOM_CODE = MTL_UNITS_OF_MEASURE_TL.UOM_CODEON MTL_UOM_CONVERSIONS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID