Skip to content
M3 Reference

MHDISH

Prefix: OQtransaction

The delivery header — one row per delivery (inbound or outbound, discriminated by INOU) identified by the delivery index DLIX, carrying the warehouse and the shipment it rides on; the unit picking and dispatch work against. DLIX is scoped by direction — inbound and outbound deliveries share the number space, so the key is CONO + INOU + DLIX, and a join from an order table that carries no direction column matches on DLIX alone

Module: DeliveriesCompany-partitioned (CONO)
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).
In field listings, K marks a primary-key field.
Used in the library
KPI definitions
Dashboard patterns

Header & line

MHDISH is the header for its lines in MHDISL.

Fields

7 fields · 3 key

7 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 7 fields.
KeyFieldAliasDescriptionTypeLengthFlags
KeyOQCONOCONOCompanynumeric
KeyOQINOUINOUDirection — inbound or outbound deliverynumeric
KeyOQDLIXDLIXDelivery index — the delivery's identity, carried by every line and document that rides on itnumeric
OQWHLOWHLOWarehouse the delivery ships from or arrives atalphanumeric
OQCONNCONNShipment the delivery is grouped ontonumeric
OQPGRSPGRSProgress status — release, picking and reporting progress; the ladder is direction-scoped by INOU, so it is not decoded here — see the quirks guidealphanumeric
OQPISTPISTPacking status — whether packing is unused, not started, started, or completed for the deliveryalphanumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MHDISH 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

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

-- ============================================================
-- Table  : MHDISH — The delivery header — one row per delivery (inbound or outbound, discriminated by INOU) identified by the delivery index DLIX, carrying the warehouse and the shipment it rides on; the unit picking and dispatch work against. DLIX is scoped by direction — inbound and outbound deliveries share the number space, so the key is CONO + INOU + DLIX, and a join from an order table that carries no direction column matches on DLIX alone
-- Purpose: Column-selected read of MHDISH — auto-generated from field metadata
-- Grain  : One row per company (CONO) + OQINOU + OQDLIX
-- 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.OQCONO AS "Company",
  m.OQINOU AS "Direction — inbound or outbound delivery",
  m.OQDLIX AS "Delivery index — the delivery's identity, carried by every line and document that rides on it",
  m.OQWHLO AS "Warehouse the delivery ships from or arrives at",
  m.OQCONN AS "Shipment the delivery is grouped onto",
  m.OQPGRS AS "Progress status — release, picking and reporting progress; the ladder is direction-scoped by INOU, so it is not decoded here — see the quirks guide",  -- status: decode m.OQPGRS against your configuration — see quirks guide #statuses
  CASE m.OQPIST WHEN '00' THEN 'Packing not used' WHEN '10' THEN 'Packing not started' WHEN '20' THEN 'Packing started but not completed' WHEN '30' THEN 'Packing completed' ELSE m.OQPIST END AS "Packing status — whether packing is unused, not started, started, or completed for the delivery"  -- status: PIST_DISH (all 4 curated values)
FROM <catalog>.<schema>.MHDISH m
WHERE
  m.OQCONO = <company>
ORDER BY m.OQINOU;

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

  • MHDISHMITWHLforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MHDISH.OQWHLO = MITWHL.MWWHLO AND MHDISH.OQCONO = MITWHL.MWCONO
  • 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
  • ODHEADMHDISHforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODHEAD.UADLIX = MHDISH.OQDLIX AND ODHEAD.UACONO = MHDISH.OQCONO

Programs That Use This Table

More Deliveries tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Infor. Infor, Infor M3, and Infor CloudSuite are trademarks of Infor and/or its affiliates.