MTL_SYSTEM_ITEMS_TL
Schema: INVmasterPer inventory orgLanguage-stripedThe item master's translation companion — item description and long description in every installed language, one row per item per organization per language
Filter to one LANGUAGE or item joins multiply by installed languages; SOURCE_LANG marks the row the others were translated from (see quirks #tl-tables).
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Translations
MTL_SYSTEM_ITEMS_TL holds the per-language translation rows for MTL_SYSTEM_ITEMS_B — one row per LANGUAGE. Filter to one LANGUAGE or rows multiply.
Fields
6 fields · 3 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVENTORY_ITEM_ID | Item id | NUMBER | Key |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | Key |
| 3 | LANGUAGE | Language of this row — one row per installed language per item/org | VARCHAR2 | Key |
| 4 | SOURCE_LANG | The language this row's text was translated from | VARCHAR2 | |
| 5 | DESCRIPTION | Item description in this row's language | VARCHAR2 | |
| 6 | LONG_DESCRIPTION | Long item description in this row's language | VARCHAR2 |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading MTL_SYSTEM_ITEMS_TLon 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_SYSTEM_ITEMS_TL — The item master's translation companion — item description and long description in every installed language, one row per item per organization per language
-- Purpose: Column-selected read of MTL_SYSTEM_ITEMS_TL — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + INVENTORY_ITEM_ID
-- 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",
t.ORGANIZATION_ID AS "Inventory organization",
t.LANGUAGE AS "Language of this row — one row per installed language per item/org",
t.SOURCE_LANG AS "The language this row's text was translated from",
t.DESCRIPTION AS "Item description in this row's language",
t.LONG_DESCRIPTION AS "Long item description in this row's language"
FROM <catalog>.<schema>.MTL_SYSTEM_ITEMS_TL t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
AND t.LANGUAGE = '<language>' -- one language or rows multiply; translations fall back to SOURCE_LANG
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- 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;6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <language>, <INVENTORY_ITEM_ID>, <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_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_TL.INVENTORY_ITEM_ID AND MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_TL.ORGANIZATION_ID AND MTL_SYSTEM_ITEMS_TL.LANGUAGE = '<language>'