ODLINE
Prefix: UBtransactionThe 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
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
ODLINE lines join back to their header ODHEAD — and the CONO — so a line never fans out across companies.
Fields
9 fields · 6 key
9 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | UBCONO | CONO | Company | numeric | ||
| Key | UBORNO | ORNO | Customer order number | alphanumeric | ||
| Key | UBPONR | PONR | Order line number | numeric | ||
| Key | UBPOSX | POSX | Line suffix | numeric | ||
| Key | UBDLIX | DLIX | Delivery index the line was invoiced under | numeric | ||
| Key | UBTEPY | TEPY | Payment terms — part of the key, mirroring the header | alphanumeric | ||
| UBITNO | ITNO | Item invoiced | alphanumeric | |||
| UBIVQT | IVQT | Invoiced quantity on this delivery line | numeric | |||
| UBSAPR | SAPR | Sales price the line was invoiced at | numeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading ODLINE 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.
4 parameters not filled: <catalog>, <schema>, <company>, <ORNO>
-- ============================================================
-- Table : ODLINE — The 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
-- Purpose: Column-selected read of ODLINE — auto-generated from field metadata
-- Grain : One row per company (CONO) + UBORNO + UBPONR + UBPOSX + UBDLIX + UBTEPY
-- 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.UBCONO AS "Company",
o.UBORNO AS "Customer order number",
o.UBPONR AS "Order line number",
o.UBPOSX AS "Line suffix",
o.UBDLIX AS "Delivery index the line was invoiced under",
o.UBTEPY AS "Payment terms — part of the key, mirroring the header",
o.UBITNO AS "Item invoiced",
o.UBIVQT AS "Invoiced quantity on this delivery line",
o.UBSAPR AS "Sales price the line was invoiced at"
FROM <catalog>.<schema>.ODLINE o
WHERE
o.UBCONO = <company>
-- AND o.UBORNO = '<ORNO>'
ORDER BY o.UBORNO;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 = ODLINE.UBORNO AND ODHEAD.UADLIX = ODLINE.UBDLIX AND ODHEAD.UATEPY = ODLINE.UBTEPY AND ODHEAD.UACONO = ODLINE.UBCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODLINE.UBITNO = MITMAS.MMITNO AND ODLINE.UBCONO = MITMAS.MMCONO
Programs That Use This Table
More Deliveries tables
- 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
- 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 alone