M3 Reference

MHDISL

Prefix: URtransaction

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

Module: DeliveriesCompany-partitioned (CONO)Header: MHDISH

What the badges mean

Prefix: MM: Prefix: the table’s 2-character physical-column prefix (e.g. MM on MITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide).
master: Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
Shared across companies: The table carries no CONO — rows aren’t partitioned per company (see the quirks guide).
Division-level: The table carries DIVI — rows are scoped below company to a division, one layer more granular than CONO alone (see the quirks guide).

Used in the library

KPI definitions

K-01OTIF — On Time In Full

K-07Perfect Order Rate

Dashboard patterns

D-02OTIF / Customer Service

D-05Plan vs Actual

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

6 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 6 fields.
Key	Field	Alias	Description	Type
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 MHDISL on 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

CatalogSchemaCompany (CONO)

3 parameters not filled: <catalog>, <schema>, <company>

-- ============================================================
-- 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 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.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;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

MHDISHMHDISLheader line · 1:N
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MHDISH.OQDLIX = MHDISL.URDLIX AND MHDISH.OQINOU = MHDISL.URINOU AND MHDISH.OQCONO = MHDISL.URCONO