M3 Reference
Deliveries
Supply chainDelivery documents and shipment records between order lines and the customer
4 tables3 programs
Verified September 2026
In the business-problem map Customer Service & Fulfillment
Tables
Transaction · 4
- MHDISHThe 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 alonePrefix: OQtransaction
- MHDISLThe 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 DLIXPrefix: URtransaction
- ODHEADThe invoiced-delivery header — one row per delivered and invoiced customer order delivery, carrying the invoice number and date, payer, and currency; the payment term is part of its key, so one delivery can settle under more than one term; it carries no direction column, so its DLIX join to MHDISH matches on the delivery index alonePrefix: UAtransaction
- ODLINEThe invoiced-delivery line — one row per invoiced order line per delivery, with the invoiced quantity and price; the revenue-at-line grain of order-to-cash analytics, joined to its header by ORNO + DLIX + payment termPrefix: UBtransaction
Programs
- MWS410 — Delivery toolbox — the delivery workbench where MHDISH deliveries are monitored and driven through picking and dispatchInteractive
- MWS420 — Picking list report — confirms picking on the MHDISH/MHDISL deliveries and updates the on-hand behind themInteractive
- OIS180 — Customer order invoice print — invoices delivered orders into ODHEAD/ODLINE, and where the invoice date and the accounting date part ways in order-to-cashInteractive