MTL_LOT_NUMBERS
Schema: INVmasterPer inventory orgThe lot master — definition, genealogy (parent lot), status, grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
Lot definitions are per item per org — the same lot number can legitimately exist under different items or orgs, so lot joins always carry item and org alongside the lot number. DISABLE_FLAG is a NUMBER, not a Y/N character flag.
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
11 fields · 3 key
11 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVENTORY_ITEM_ID | Item id — lots are defined per item | NUMBER | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization — lots are defined per org too | NUMBER | Primary-key field |
| 3 | LOT_NUMBER | The lot number — only meaningful together with item and org | VARCHAR2 | Primary-key field |
| 4 | PARENT_LOT_NUMBER | Parent lot for split/merge genealogy | VARCHAR2 | |
| 5 | ORIGINATION_DATE | When the lot came into existence | DATE | |
| 6 | EXPIRATION_DATE | When the lot expires — the shelf-life analysis date | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 7 | RETEST_DATE | When the lot is due for retest | DATE | |
| 8 | STATUS_ID | Material status of the lot | NUMBER | |
| 9 | GRADE_CODE | Quality grade of the lot | VARCHAR2 | |
| 10 | DISABLE_FLAG | Whether the lot is disabled — a NUMBER, not a Y/N character flag | NUMBER | |
| 11 | SUPPLIER_LOT_NUMBER | The supplier's own lot number, kept for traceability | VARCHAR2 |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading MTL_LOT_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.
8 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <INVENTORY_ITEM_ID>, <LOT_NUMBER>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : MTL_LOT_NUMBERS — The lot master — definition, genealogy (parent lot), status, grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
-- Purpose: Column-selected read of MTL_LOT_NUMBERS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + INVENTORY_ITEM_ID + LOT_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 — lots are defined per item",
t.ORGANIZATION_ID AS "Inventory organization — lots are defined per org too",
t.LOT_NUMBER AS "The lot number — only meaningful together with item and org",
t.PARENT_LOT_NUMBER AS "Parent lot for split/merge genealogy",
t.ORIGINATION_DATE AS "When the lot came into existence",
t.EXPIRATION_DATE AS "When the lot expires — the shelf-life analysis date",
t.RETEST_DATE AS "When the lot is due for retest",
t.STATUS_ID AS "Material status of the lot",
t.GRADE_CODE AS "Quality grade of the lot",
t.DISABLE_FLAG AS "Whether the lot is disabled — a NUMBER, not a Y/N character flag",
t.SUPPLIER_LOT_NUMBER AS "The supplier's own lot number, kept for traceability"
FROM <catalog>.<schema>.MTL_LOT_NUMBERS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- AND t.LOT_NUMBER = '<LOT_NUMBER>'
-- AND t.EXPIRATION_DATE >= DATE '<DATE_FROM>'
-- AND t.EXPIRATION_DATE <= DATE '<DATE_TO>'
-- 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
ON MTL_ONHAND_QUANTITIES_DETAIL.LOT_NUMBER = MTL_LOT_NUMBERS.LOT_NUMBER AND MTL_ONHAND_QUANTITIES_DETAIL.INVENTORY_ITEM_ID = MTL_LOT_NUMBERS.INVENTORY_ITEM_ID AND MTL_ONHAND_QUANTITIES_DETAIL.ORGANIZATION_ID = MTL_LOT_NUMBERS.ORGANIZATION_IDON MTL_TRANSACTION_LOT_NUMBERS.LOT_NUMBER = MTL_LOT_NUMBERS.LOT_NUMBER AND MTL_TRANSACTION_LOT_NUMBERS.INVENTORY_ITEM_ID = MTL_LOT_NUMBERS.INVENTORY_ITEM_ID AND MTL_TRANSACTION_LOT_NUMBERS.ORGANIZATION_ID = MTL_LOT_NUMBERS.ORGANIZATION_IDON MTL_LOT_NUMBERS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_LOT_NUMBERS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON 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
More Inventory tables
- MTL_MATERIAL_TRANSACTIONSThe material transaction ledger — one row per inventory movement or cost update, classified by transaction type, action, and source type, with quantity, date, and the document reference that caused it; the reconciliation backbone for every stock question
- MTL_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, lot, and revision, consumed in FIFO order as material issues
- MTL_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the master org it points to, and the org's costing method and locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves against
- MTL_RESERVATIONSFirm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lot
- MTL_SECONDARY_INVENTORIESThe subinventory master — each row a named section of stock within an organization (stores, staging, WIP, rejects) with its asset/expense nature, tracking and reservability controls, and default accounts
- MTL_SERIAL_NUMBERSThe 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