M3 Reference
MWS410
InteractiveDelivery toolbox — the delivery workbench where MHDISH deliveries are monitored and driven through picking and dispatch
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 MWS410 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.
Query parameters
-- ============================================================
-- Program: MWS410 — Delivery toolbox — the delivery workbench where MHDISH deliveries are monitored and driven through picking and dispatch
-- Purpose: Read the tables behind program MWS410 — auto-generated from program-table-map
-- Grain : MHDISH × MHDISL — 1:N joins yield one row per line
-- Tables : MHDISH, MHDISL
-- 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; 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
h.OQCONO AS "Company",
h.OQINOU AS "Direction — inbound or outbound delivery",
h.OQDLIX AS "Delivery index — the delivery's identity, carried by every line and document that rides on it",
m.URRIDN AS "Order number of the line being delivered",
m.URRIDL AS "Order line number being delivered",
m.URTRQT AS "Quantity moving on this delivery line"
FROM <catalog>.<schema>.MHDISH h
LEFT JOIN <catalog>.<schema>.MHDISL m
ON m.URDLIX = h.OQDLIX
AND m.URINOU = h.OQINOU
AND m.URCONO = h.OQCONO
WHERE
h.OQCONO = <company>
ORDER BY h.OQINOU;3 parameters not filled: <catalog>, <schema>, <company>
Backing Tables
How these tables connect. Nodes are clickable.