MTL_CROSS_REFERENCES_B
Schema: INVmasterItem 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
Restructured at R12.1 from the old MTL_CROSS_REFERENCES (which survives as a compatibility object — legacy queries still run). ORGANIZATION_ID is NULLABLE here: org-independent references (ORG_INDEPENDENT_FLAG = 'Y') carry NULL, so this catalog deliberately does not anchor the table on an inventory org — an ORGANIZATION_ID filter silently drops the org-independent rows.
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
10 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CROSS_REFERENCE_ID | Surrogate key of the cross-reference (added by the R12.1 restructure) | NUMBER | Key |
| 2 | INVENTORY_ITEM_ID | The item the external identifier maps to | NUMBER | |
| 3 | ORGANIZATION_ID | Inventory organization — NULL for org-independent references, so don't blanket-filter on it | NUMBER | |
| 4 | CROSS_REFERENCE_TYPE | The cross-reference type (GTIN, old part number, customer part number…) | VARCHAR2 | |
| 5 | CROSS_REFERENCE | The external identifier itself | VARCHAR2 | |
| 6 | ORG_INDEPENDENT_FLAG | Whether the reference applies across all orgs (ORGANIZATION_ID is NULL on those rows) | VARCHAR2 | |
| 7 | DESCRIPTION | Description — untranslated copy; translated on the TL companion | VARCHAR2 | |
| 8 | START_DATE_ACTIVE | Effectivity start date (new in the R12.1 restructure) | DATE | |
| 9 | END_DATE_ACTIVE | Effectivity end date | DATE | |
| 10 | EPC_GTIN_SERIAL | GTIN serial component for EPC-style references | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading MTL_CROSS_REFERENCES_Bon 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_CROSS_REFERENCES_B — Item 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
-- Purpose: Column-selected read of MTL_CROSS_REFERENCES_B — auto-generated from field metadata
-- Grain : One row per CROSS_REFERENCE_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.CROSS_REFERENCE_ID AS "Surrogate key of the cross-reference (added by the R12.1 restructure)",
t.INVENTORY_ITEM_ID AS "The item the external identifier maps to",
t.ORGANIZATION_ID AS "Inventory organization — NULL for org-independent references, so don't blanket-filter on it",
t.CROSS_REFERENCE_TYPE AS "The cross-reference type (GTIN, old part number, customer part number…)",
t.CROSS_REFERENCE AS "The external identifier itself",
t.ORG_INDEPENDENT_FLAG AS "Whether the reference applies across all orgs (ORGANIZATION_ID is NULL on those rows)",
t.DESCRIPTION AS "Description — untranslated copy; translated on the TL companion",
t.START_DATE_ACTIVE AS "Effectivity start date (new in the R12.1 restructure)",
t.END_DATE_ACTIVE AS "Effectivity end date",
t.EPC_GTIN_SERIAL AS "GTIN serial component for EPC-style references"
FROM <catalog>.<schema>.MTL_CROSS_REFERENCES_B t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CROSS_REFERENCE_ID;3 parameters not filled: <catalog>, <schema>, <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_CROSS_REFERENCES_B.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID