M3 Reference
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
Module: Inventory & WarehouseCompany-partitioned (CONO)
Fields
10 fields · 3 key
| 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 MITTRAon 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.
Query parameters
-- ============================================================
-- 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 Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified. 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;7 parameters not filled: <catalog>, <schema>, <company>, <WHLO>, <ITNO>, <DATE_FROM>, <DATE_TO>
Relationships
1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Programs That Use This Table
No program mappings populated for this table yet.