M3 Reference

ODLINE

Prefix: UBtransaction

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

Module: DeliveriesCompany-partitioned (CONO)Header: ODHEAD

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

Key	Field	Alias	Description	Type
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 ODLINEon 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

CatalogSchemaCompany (CONO)Customer order (ORNO)

Include optional filters (1)

-- ============================================================
-- 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 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
  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;

4 parameters not filled: <catalog>, <schema>, <company>, <ORNO>

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

ODHEADODLINEheader line · 1:N
ON ODHEAD.UAORNO = ODLINE.UBORNO AND ODHEAD.UADLIX = ODLINE.UBDLIX AND ODHEAD.UATEPY = ODLINE.UBTEPY AND ODHEAD.UACONO = ODLINE.UBCONO
ODLINEMITMASforeign key · N:1
ON ODLINE.UBITNO = MITMAS.MMITNO AND ODLINE.UBCONO = MITMAS.MMCONO

Programs That Use This Table

No program mappings populated for this table yet.