MHDISL
Prefix: URtransactionThe delivery line — one row per order line placed on a delivery, keyed by the delivery index and the order reference; the quantity actually moving on this delivery, joined to its header by DLIX
Header & line
MHDISL lines join back to their header MHDISH — and the CONO — so a line never fans out across companies.
Fields
6 fields · 5 key
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | URCONO | CONO | Company | numeric | ||
| Key | URINOU | INOU | Direction — inbound or outbound | numeric | ||
| Key | URDLIX | DLIX | Delivery index of the header this line rides on | numeric | ||
| Key | URRIDN | RIDN | Order number of the line being delivered | alphanumeric | ||
| Key | URRIDL | RIDL | Order line number being delivered | numeric | ||
| URTRQT | TRQT | Quantity moving on this delivery line | numeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MHDISLon 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.
-- ============================================================
-- Table : MHDISL — The delivery line — one row per order line placed on a delivery, keyed by the delivery index and the order reference; the quantity actually moving on this delivery, joined to its header by DLIX
-- Purpose: Column-selected read of MHDISL — auto-generated from field metadata
-- Grain : One row per company (CONO) + URINOU + URDLIX + URRIDN + URRIDL
-- 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
m.URCONO AS "Company",
m.URINOU AS "Direction — inbound or outbound",
m.URDLIX AS "Delivery index of the header this line rides on",
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>.MHDISL m
WHERE
m.URCONO = <company>
ORDER BY m.URINOU;3 parameters not filled: <catalog>, <schema>, <company>
Relationships
1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MHDISH.OQDLIX = MHDISL.URDLIX AND MHDISH.OQINOU = MHDISL.URINOU AND MHDISH.OQCONO = MHDISL.URCONO