M3 Reference
MWS070
InteractiveStock transaction history — the display over the MITTRA ledger, where M3 stores every physical stock transaction
Tables vs APIs
This program works over the tables below. For analytics at scale, land the raw tables — the SQL further down reads them directly, joined on their keys and CONO. When to land tables vs call MI APIs
Boilerplate SQL
Databricks SQLStarting point for reading the tables behind MWS070 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.
Query parameters
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Program: MWS070 — Stock transaction history — the display over the MITTRA ledger, where M3 stores every physical stock transaction
-- Purpose: Read the tables behind program MWS070 — auto-generated from program-table-map
-- Grain : One row per MITTRA record
-- Tables : MITTRA
-- 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; company-partitioned tables are joined on CONO to prevent cross-company fan-out. 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",
t.MTTRQT AS "Transaction quantity in the basic unit, signed by direction"
FROM <catalog>.<schema>.MITTRA t
WHERE
t.MTCONO = <company>
ORDER BY t.MTWHLO;