MTL_TRANSACTION_LOT_NUMBERS
Schema: INVtransactionPer inventory orgLot-level detail for material transactions — one row per lot consumed or received per material transaction, with the lot's share of the quantity
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
7 fields · 2 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_ID | The material transaction the lot detail belongs to | NUMBER | Key |
| 2 | LOT_NUMBER | The lot consumed or received | VARCHAR2 | Key |
| 3 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 4 | INVENTORY_ITEM_ID | Item id | NUMBER | |
| 5 | TRANSACTION_QUANTITY | The lot's share of the movement, in the transaction UOM | NUMBER | |
| 6 | PRIMARY_QUANTITY | The lot's share in the primary UOM | NUMBER | |
| 7 | SERIAL_TRANSACTION_ID | Bridge to serial detail for lot-and-serial-controlled items | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading MTL_TRANSACTION_LOT_NUMBERSon 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_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;6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <LOT_NUMBER>, <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_TRANSACTION_LOT_NUMBERS.TRANSACTION_ID = MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID AND MTL_TRANSACTION_LOT_NUMBERS.ORGANIZATION_ID = MTL_MATERIAL_TRANSACTIONS.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_ID