MITTRA
Prefix: MTtransactionThe stock transaction ledger — one row per inventory movement (receipt, issue, transfer, adjustment) with its transaction type, quantity, date, and the order reference that caused it
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide). - master
- Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
- Shared across companies
- The table carries no
CONO— rows aren’t partitioned per company (see the quirks guide). - Division-level
- The table carries
DIVI— rows are scoped below company to a division, one layer more granular thanCONOalone (see the quirks guide).
Fields
10 fields · 3 key
10 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | MTCONO | CONO | Company | numeric | ||
| Key | MTWHLO | WHLO | Warehouse | alphanumeric | ||
| Key | MTITNO | ITNO | Item number | alphanumeric | ||
| MTTRDT | TRDT | Transaction date | numeric | |||
| MTTRTP | TRTP | Transaction type — the code classifying the movement (receipt, issue, transfer, adjustment…) | alphanumeric | |||
| MTTRQT | TRQT | Transaction quantity in the basic unit, signed by direction | numeric | |||
| MTRIDN | RIDN | Order number of the document that caused the movement (customer order, purchase order, manufacturing order…) | alphanumeric | |||
| MTRIDL | RIDL | Order line number within the referenced document | numeric | |||
| MTWHSL | WHSL | Stock location the movement touched | alphanumeric | |||
| MTBANO | BANO | Lot (batch) number the movement touched | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MITTRA on Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <company>, <WHLO>, <ITNO>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : MITTRA — The stock transaction ledger — one row per inventory movement (receipt, issue, transfer, adjustment) with its transaction type, quantity, date, and the order reference that caused it
-- Purpose: Column-selected read of MITTRA — auto-generated from field metadata
-- Grain : Transaction-grain — finer than company (CONO) + MTWHLO + MTITNO; the full row key is not yet cataloged (see the table description)
-- Notes : Auto-generated skeleton for a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
t.MTCONO AS "Company",
t.MTWHLO AS "Warehouse",
t.MTITNO AS "Item number",
CASE WHEN t.MTTRDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(t.MTTRDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Transaction date", -- YYYYMMDD, 0 → NULL
t.MTTRTP AS "Transaction type — the code classifying the movement (receipt, issue, transfer, adjustment…)",
t.MTTRQT AS "Transaction quantity in the basic unit, signed by direction",
t.MTRIDN AS "Order number of the document that caused the movement (customer order, purchase order, manufacturing order…)",
t.MTRIDL AS "Order line number within the referenced document",
t.MTWHSL AS "Stock location the movement touched",
t.MTBANO AS "Lot (batch) number the movement touched"
FROM <catalog>.<schema>.MITTRA t
WHERE
t.MTCONO = <company>
-- AND t.MTWHLO = '<WHLO>'
-- AND t.MTITNO = '<ITNO>'
-- AND t.MTTRDT >= <DATE_FROM> -- yyyyMMdd numeric
-- AND t.MTTRDT <= <DATE_TO> -- yyyyMMdd numeric
ORDER BY t.MTWHLO;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITTRA.MTITNO = MITMAS.MMITNO AND MITTRA.MTCONO = MITMAS.MMCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITTRA.MTWHLO = MITWHL.MWWHLO AND MITTRA.MTCONO = MITWHL.MWCONO
Programs That Use This Table
More Inventory & Warehouse tables
- MITWHLThe warehouse master — one row per warehouse with its name, facility, and warehouse type; the WHLO every balance and movement carries resolves here
- MILOMAThe lot master — one row per item and lot (batch) number, carrying the lot's identity and life-cycle dates; location balances and allocations reference it by BANO
- MITALOAllocations — one row per item, location, and lot allocated to a specific order line, connecting demand (the order reference) to the exact stock that will fill it; the bridge between order lines and MITLOC balances
- MITBALThe item/warehouse record — one row per item and warehouse, pairing planning policy (safety stock, reorder point, lead time, main supplier) with the warehouse-level on-hand and allocated balances
- MITLOCThe location-level balance — one row per item, warehouse, location, lot, and receipt, holding the physical on-hand at the finest grain M3 tracks stock; warehouse-level figures in MITBAL are the roll-up of these rows