Skip to content
EBS Reference

MTL_TRANSACTION_LOT_NUMBERS

Schema: INVtransactionPer inventory org

Lot-level detail for material transactions — one row per lot consumed or received per material transaction, with the lot's share of the quantity

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

For lot-and-serial-controlled items, SERIAL_TRANSACTION_ID bridges to the serial detail. No physical unique index — the working key is transaction id + lot number.

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

7 fields · 2 key

7 fields.

Table fields: position, field name, description, data type, and flags. 7 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDThe material transaction the lot detail belongs toNUMBER
Primary-key field
2LOT_NUMBERThe lot consumed or receivedVARCHAR2
Primary-key field
3ORGANIZATION_IDInventory organizationNUMBER
4INVENTORY_ITEM_IDItem idNUMBER
5TRANSACTION_QUANTITYThe lot's share of the movement, in the transaction UOMNUMBER
6PRIMARY_QUANTITYThe lot's share in the primary UOMNUMBER
7SERIAL_TRANSACTION_IDBridge to serial detail for lot-and-serial-controlled itemsNUMBER

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

Query parameters

6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <LOT_NUMBER>, <watermark>

-- ============================================================
-- Table  : MTL_TRANSACTION_LOT_NUMBERS — Lot-level detail for material transactions — one row per lot consumed or received per material transaction, with the lot's share of the quantity
-- Purpose: Column-selected read of MTL_TRANSACTION_LOT_NUMBERS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + TRANSACTION_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.TRANSACTION_ID AS "The material transaction the lot detail belongs to",
  t.LOT_NUMBER AS "The lot consumed or received",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.INVENTORY_ITEM_ID AS "Item id",
  t.TRANSACTION_QUANTITY AS "The lot's share of the movement, in the transaction UOM",
  t.PRIMARY_QUANTITY AS "The lot's share in the primary UOM",
  t.SERIAL_TRANSACTION_ID AS "Bridge to serial detail for lot-and-serial-controlled items"
FROM <catalog>.<schema>.MTL_TRANSACTION_LOT_NUMBERS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.TRANSACTION_ID = <TRANSACTION_ID>
  -- AND t.LOT_NUMBER = '<LOT_NUMBER>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRANSACTION_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_TRANSACTION_LOT_NUMBERSMTL_MATERIAL_TRANSACTIONSforeign key · N:1
    ON MTL_TRANSACTION_LOT_NUMBERS.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID AND MTL_TRANSACTION_LOT_NUMBERS.ORGANIZATION_ID = MTL_MATERIAL_TRANSACTIONS.ORGANIZATION_ID
  • MTL_TRANSACTION_LOT_NUMBERSMTL_LOT_NUMBERSforeign key · N:1
    ON 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_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.