MITPLO

-- ============================================================
-- Table  : MITPLO — The material plan — one row per planned transaction (demand or supply) per item and warehouse, ordered by planning date; the table behind M3's material plan view and the starting point for supply/demand pegging analysis
-- Purpose: Column-selected read of MITPLO — auto-generated from field metadata
-- Grain  : Transaction-grain — finer than company (CONO) + MOWHLO + MOITNO + MOPLDT; 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
  m.MOCONO AS "Company",
  m.MOWHLO AS "Warehouse",
  m.MOITNO AS "Item number",
  CASE WHEN m.MOPLDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(m.MOPLDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Planning date the transaction is scheduled on",  -- YYYYMMDD, 0 → NULL
  m.MOORCA AS "Order category of the planned transaction (customer order, purchase order, manufacturing order…)",
  m.MORIDN AS "Order number behind the planned transaction",
  m.MORIDL AS "Order line number behind the planned transaction",
  m.MOTRQT AS "Planned quantity, signed by direction (demand negative, supply positive)"
FROM <catalog>.<schema>.MITPLO m
WHERE
  m.MOCONO = <company>
  -- AND m.MOWHLO = '<WHLO>'
  -- AND m.MOITNO = '<ITNO>'
  -- AND m.MOPLDT >= <DATE_FROM>  -- yyyyMMdd numeric
  -- AND m.MOPLDT <= <DATE_TO>  -- yyyyMMdd numeric
ORDER BY m.MOWHLO;