Skip to content
EBS Reference

MTL_SERIAL_NUMBERS

Schema: INVmaster

The serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit; a serial is unique per item, not per org

Identity
Module: InventoryNot org-partitioned
Fusion equivalents (1)
Notes

The org column is CURRENT_ORGANIZATION_ID — where the unit sits now, an attribute rather than part of the key — so this catalog does not give the table the inventory-org anchor; filter CURRENT_ORGANIZATION_ID explicitly when you mean one org's serials.

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 · 2 key

10 fields.

Table fields: position, field name, description, data type, and flags. 10 fields.
#FieldDescriptionTypeFlags
1INVENTORY_ITEM_IDItem id — a serial is unique per item, across all orgsNUMBER
Primary-key field
2SERIAL_NUMBERThe serial numberVARCHAR2
Primary-key field
3CURRENT_ORGANIZATION_IDWhere the unit sits now — an attribute, not part of the key; filter it when you mean one org's serialsNUMBER
4CURRENT_STATUSLifecycle state — defined-not-used, in stores, issued, in transitNUMBER
5CURRENT_SUBINVENTORY_CODEThe subinventory the unit currently sits inVARCHAR2
6CURRENT_LOCATOR_IDThe locator the unit currently sits inNUMBER
7LOT_NUMBERThe lot the unit belongs to, for lot-and-serial itemsVARCHAR2
8INITIALIZATION_DATEWhen the serial was first usedDATE
9SHIP_DATEWhen the unit shippedDATE
10ORIGINAL_WIP_ENTITY_IDThe job that built the unit, when WIP-sourcedNUMBER

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

5 parameters not filled: <catalog>, <schema>, <INVENTORY_ITEM_ID>, <SERIAL_NUMBER>, <watermark>

-- ============================================================
-- Table  : MTL_SERIAL_NUMBERS — The serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit; a serial is unique per item, not per org
-- Purpose: Column-selected read of MTL_SERIAL_NUMBERS — auto-generated from field metadata
-- Grain  : One row per INVENTORY_ITEM_ID + SERIAL_NUMBER
-- 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 — a serial is unique per item, across all orgs",
  t.SERIAL_NUMBER AS "The serial number",
  t.CURRENT_ORGANIZATION_ID AS "Where the unit sits now — an attribute, not part of the key; filter it when you mean one org's serials",
  t.CURRENT_STATUS AS "Lifecycle state — defined-not-used, in stores, issued, in transit",
  t.CURRENT_SUBINVENTORY_CODE AS "The subinventory the unit currently sits in",
  t.CURRENT_LOCATOR_ID AS "The locator the unit currently sits in",
  t.LOT_NUMBER AS "The lot the unit belongs to, for lot-and-serial items",
  t.INITIALIZATION_DATE AS "When the serial was first used",
  t.SHIP_DATE AS "When the unit shipped",
  t.ORIGINAL_WIP_ENTITY_ID AS "The job that built the unit, when WIP-sourced"
FROM <catalog>.<schema>.MTL_SERIAL_NUMBERS 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.SERIAL_NUMBER = '<SERIAL_NUMBER>'
  -- 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;

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_SERIAL_NUMBERSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON MTL_SERIAL_NUMBERS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_SERIAL_NUMBERS.CURRENT_ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • MTL_SERIAL_NUMBERSMTL_LOT_NUMBERSforeign key · N:1
    ON MTL_SERIAL_NUMBERS.LOT_NUMBER = MTL_LOT_NUMBERS.LOT_NUMBER AND MTL_SERIAL_NUMBERS.INVENTORY_ITEM_ID = MTL_LOT_NUMBERS.INVENTORY_ITEM_ID AND MTL_SERIAL_NUMBERS.CURRENT_ORGANIZATION_ID = MTL_LOT_NUMBERS.ORGANIZATION_ID

Browse more Inventory tables

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