Skip to content
M3 Reference

ODHEAD

Prefix: UAtransaction

The 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 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

Header & line

ODHEAD is the header for its lines in ODLINE.

Fields

10 fields · 4 key

10 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 10 fields.
KeyFieldAliasDescriptionTypeLengthFlags
KeyUACONOCONOCompanynumeric
KeyUAORNOORNOCustomer order numberalphanumeric
KeyUADLIXDLIXDelivery index the invoiced delivery corresponds tonumeric
KeyUATEPYTEPYPayment terms — part of the key, so one delivery can settle under more than one termalphanumeric
UAIVNOIVNOInvoice number the delivery was billed onnumeric
UAIVDTIVDTInvoice datenumeric
UACUNOCUNOCustomer the delivery was made toalphanumeric
UAPYNOPYNOPayer — the customer billed, when different from the receiveralphanumeric
UACUCDCUCDInvoice currencyalphanumeric
UAWHLOWHLOWarehouse the delivery shipped fromalphanumeric

Field provenance: hand-curated.

Boilerplate SQL

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

6 parameters not filled: <catalog>, <schema>, <company>, <ORNO>, <DATE_FROM>, <DATE_TO>

-- ============================================================
-- Table  : ODHEAD — The 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 alone
-- Purpose: Column-selected read of ODHEAD — auto-generated from field metadata
-- Grain  : One row per company (CONO) + UAORNO + UADLIX + UATEPY
-- 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
  o.UACONO AS "Company",
  o.UAORNO AS "Customer order number",
  o.UADLIX AS "Delivery index the invoiced delivery corresponds to",
  o.UATEPY AS "Payment terms — part of the key, so one delivery can settle under more than one term",
  o.UAIVNO AS "Invoice number the delivery was billed on",
  CASE WHEN o.UAIVDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(o.UAIVDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Invoice date",  -- YYYYMMDD, 0 → NULL
  o.UACUNO AS "Customer the delivery was made to",
  o.UAPYNO AS "Payer — the customer billed, when different from the receiver",
  o.UACUCD AS "Invoice currency",
  o.UAWHLO AS "Warehouse the delivery shipped from"
FROM <catalog>.<schema>.ODHEAD o
WHERE
  o.UACONO = <company>
  -- AND o.UAORNO = '<ORNO>'
  -- AND o.UAIVDT >= <DATE_FROM>  -- yyyyMMdd numeric
  -- AND o.UAIVDT <= <DATE_TO>  -- yyyyMMdd numeric
ORDER BY o.UAORNO;

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

  • ODHEADOOHEADforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODHEAD.UAORNO = OOHEAD.OAORNO AND ODHEAD.UACONO = OOHEAD.OACONO
  • ODHEADOCUSMAforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODHEAD.UACUNO = OCUSMA.OKCUNO AND ODHEAD.UACONO = OCUSMA.OKCONO
  • 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
  • ODHEADODLINEheader line · 1:N
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODHEAD.UAORNO = ODLINE.UBORNO AND ODHEAD.UADLIX = ODLINE.UBDLIX AND ODHEAD.UATEPY = ODLINE.UBTEPY AND ODHEAD.UACONO = ODLINE.UBCONO

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.