Skip to content
EBS Reference

MTL_CROSS_REFERENCES_B

Schema: INVmaster

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

Identity
Notes

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
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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

10 fields · 1 key

10 fields.

Table fields: position, field name, description, data type, and flags. 10 fields.
#FieldDescriptionTypeFlags
1CROSS_REFERENCE_IDSurrogate key of the cross-reference (added by the R12.1 restructure)NUMBER
Primary-key field
2INVENTORY_ITEM_IDThe item the external identifier maps toNUMBER
3ORGANIZATION_IDInventory organization — NULL for org-independent references, so don't blanket-filter on itNUMBER
4CROSS_REFERENCE_TYPEThe cross-reference type (GTIN, old part number, customer part number…)VARCHAR2
5CROSS_REFERENCEThe external identifier itselfVARCHAR2
6ORG_INDEPENDENT_FLAGWhether the reference applies across all orgs (ORGANIZATION_ID is NULL on those rows)VARCHAR2
7DESCRIPTIONDescription — untranslated copy; translated on the TL companionVARCHAR2
8START_DATE_ACTIVEEffectivity start date (new in the R12.1 restructure)DATE
9END_DATE_ACTIVEEffectivity end dateDATE
10EPC_GTIN_SERIALGTIN serial component for EPC-style referencesNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading MTL_CROSS_REFERENCES_B 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.

Query parameters

3 parameters not filled: <catalog>, <schema>, <watermark>

-- ============================================================
-- 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;

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

  • MTL_CROSS_REFERENCES_BMTL_SYSTEM_ITEMS_Bforeign key · N:M
    ON MTL_CROSS_REFERENCES_B.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID

Browse more Item & Product Master tables

More Item & Product Master tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.