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

Module: DeliveriesCompany-partitioned (CONO)

Header & line

MHDISH is the header for its lines in MHDISL.

Fields

5 fields · 3 key

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

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MHDISHon 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
-- ============================================================
-- 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
-- Purpose: Column-selected read of MHDISH — auto-generated from field metadata
-- Grain  : One row per company (CONO) + OQINOU + OQDLIX
-- 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.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"
FROM <catalog>.<schema>.MHDISH m
WHERE
  m.OQCONO = <company>
ORDER BY m.OQINOU;

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

  • MHDISHMITWHLforeign key · N:1
    ON MHDISH.OQWHLO = MITWHL.MWWHLO AND MHDISH.OQCONO = MITWHL.MWCONO
  • MHDISHMHDISLheader line · 1:N
    ON MHDISH.OQDLIX = MHDISL.URDLIX AND MHDISH.OQINOU = MHDISL.URINOU AND MHDISH.OQCONO = MHDISL.URCONO
  • ODHEADMHDISHforeign key · N:1
    ON ODHEAD.UADLIX = MHDISH.OQDLIX AND ODHEAD.UACONO = MHDISH.OQCONO

Programs That Use This Table

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

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.