MTL_UNITS_OF_MEASURE_TL
Schema: INVmasterLanguage-stripedThe unit-of-measure master — both the 3-char UOM code and the 25-char unit name, the UOM class, and the base-unit flag, one row per unit per language
Unusual MLS pattern: there is NO _B base table — every attribute, not just descriptions, lives on the TL table, so even structural reads must filter LANGUAGE. The bare MTL_UNITS_OF_MEASURE name resolves only as a compatibility object. UOMs are global (no org column).
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
8 fields · 2 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | UOM_CODE | The 3-char UOM code transaction and balance columns carry — the practical join key | VARCHAR2 | Primary-key field |
| 2 | LANGUAGE | Language of this row — the whole table is language-striped, structural columns included | VARCHAR2 | Primary-key field |
| 3 | UNIT_OF_MEASURE | The 25-char unit name — also unique per language; purchasing documents historically carry this form | VARCHAR2 | |
| 4 | SOURCE_LANG | The language this row was translated from | VARCHAR2 | |
| 5 | UOM_CLASS | The UOM class (weight, volume, quantity…) conversions stay within | VARCHAR2 | |
| 6 | BASE_UOM_FLAG | Whether this unit is its class's base unit — conversion rates are expressed against it | VARCHAR2 | |
| 7 | DESCRIPTION | Unit description in this row's language | VARCHAR2 | |
| 8 | DISABLE_DATE | When the unit was disabled — NULL while active | DATE |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading MTL_UNITS_OF_MEASURE_TL on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <language>, <UOM_CODE>, <watermark>
-- ============================================================
-- Table : MTL_UNITS_OF_MEASURE_TL — The unit-of-measure master — both the 3-char UOM code and the 25-char unit name, the UOM class, and the base-unit flag, one row per unit per language
-- Purpose: Column-selected read of MTL_UNITS_OF_MEASURE_TL — auto-generated from field metadata
-- Grain : One row per 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.UOM_CODE AS "The 3-char UOM code transaction and balance columns carry — the practical join key",
t.LANGUAGE AS "Language of this row — the whole table is language-striped, structural columns included",
t.UNIT_OF_MEASURE AS "The 25-char unit name — also unique per language; purchasing documents historically carry this form",
t.SOURCE_LANG AS "The language this row was translated from",
t.UOM_CLASS AS "The UOM class (weight, volume, quantity…) conversions stay within",
t.BASE_UOM_FLAG AS "Whether this unit is its class's base unit — conversion rates are expressed against it",
t.DESCRIPTION AS "Unit description in this row's language",
t.DISABLE_DATE AS "When the unit was disabled — NULL while active"
FROM <catalog>.<schema>.MTL_UNITS_OF_MEASURE_TL t
WHERE
t.LANGUAGE = '<language>' -- one language or rows multiply; translations fall back to SOURCE_LANG
-- 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.UOM_CODE;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MTL_SYSTEM_ITEMS_B.PRIMARY_UOM_CODE = MTL_UNITS_OF_MEASURE_TL.UOM_CODEON MTL_UOM_CONVERSIONS.UOM_CODE = MTL_UNITS_OF_MEASURE_TL.UOM_CODE
More Item & Product Master tables
- MTL_UOM_CONVERSIONSIntra-class UOM conversion rates to each class's base unit — both standard conversions and item-specific overrides, distinguished by the item id
- MTL_CATEGORIES_BThe category master — one row per category code combination, with the SEGMENTn flexfield columns the category name concatenates from, keyed by the flexfield structure
- MTL_CATEGORY_SETS_BCategory set definitions — validation rules, control level (master-org vs org-level), the multiple-assignments flag, and the default category new items inherit
- MTL_CROSS_REFERENCES_BItem cross-references — maps items to external identifiers (GTINs, superseded part numbers, customer and supplier part numbers) by cross-reference type, either per organization or org-independent
- MTL_ITEM_CATEGORIESThe item-to-category assignment — one row per item, organization, category set, and category; the bridge every category rollup crosses
- MTL_ITEM_REVISIONS_BItem revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change notice that introduced it