ODHEAD
Prefix: UAtransactionThe 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
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — 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 thanCONOalone (see the quirks guide).
Header & line
ODHEAD is the header for its lines in ODLINE.
Fields
10 fields · 4 key
10 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | UACONO | CONO | Company | numeric | ||
| Key | UAORNO | ORNO | Customer order number | alphanumeric | ||
| Key | UADLIX | DLIX | Delivery index the invoiced delivery corresponds to | numeric | ||
| Key | UATEPY | TEPY | Payment terms — part of the key, so one delivery can settle under more than one term | alphanumeric | ||
| UAIVNO | IVNO | Invoice number the delivery was billed on | numeric | |||
| UAIVDT | IVDT | Invoice date | numeric | |||
| UACUNO | CUNO | Customer the delivery was made to | alphanumeric | |||
| UAPYNO | PYNO | Payer — the customer billed, when different from the receiver | alphanumeric | |||
| UACUCD | CUCD | Invoice currency | alphanumeric | |||
| UAWHLO | WHLO | Warehouse the delivery shipped from | alphanumeric |
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.
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
-- 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-- 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-- 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-- 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
- 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 term
- 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 alone
- 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 DLIX