Skip to content
M3 Reference

OOLINE

Prefix: OBtransaction

The customer order line — one row per ordered item with quantities across the ordered/delivered/invoiced flow, price, warehouse, and planned delivery date; the core sell-side transaction, joined to its header by ORNO

Module: Customer OrdersCompany-partitioned (CONO)Header: OOHEAD

Header & line

OOLINE lines join back to their header OOHEAD — and the CONO — so a line never fans out across companies.

Fields

12 fields · 4 key

KeyFieldAliasDescriptionTypeLengthFlags
KeyOBCONOCONOCompanynumeric
KeyOBORNOORNOCustomer order numberalphanumeric
KeyOBPONRPONROrder line numbernumeric
KeyOBPOSXPOSXLine suffix — subdivides a line when it is split (e.g. partial deliveries)numeric
OBORSTORSTLine status — the two-char ladder the line walks from entry through allocation, delivery, and invoicingalphanumeric
OBITNOITNOItem orderedalphanumeric
OBORQTORQTOrdered quantity in the basic unitnumeric
OBDLQTDLQTDelivered quantity so farnumeric
OBIVQTIVQTInvoiced quantity so farnumeric
OBSAPRSAPRSales price per price unit on the linenumeric
OBWHLOWHLOWarehouse the line ships fromalphanumeric
OBDWDTDWDTPlanned delivery date for the linenumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading OOLINEon 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
-- ============================================================
-- Table  : OOLINE — The customer order line — one row per ordered item with quantities across the ordered/delivered/invoiced flow, price, warehouse, and planned delivery date; the core sell-side transaction, joined to its header by ORNO
-- Purpose: Column-selected read of OOLINE — auto-generated from field metadata
-- Grain  : One row per company (CONO) + OBORNO + OBPONR + OBPOSX
-- 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
  ol.OBCONO AS "Company",
  ol.OBORNO AS "Customer order number",
  ol.OBPONR AS "Order line number",
  ol.OBPOSX AS "Line suffix — subdivides a line when it is split (e.g. partial deliveries)",
  CASE ol.OBORST WHEN '10' THEN 'Preliminary' WHEN '20' THEN 'Final (entered)' WHEN '22' THEN 'Not allocated' WHEN '23' THEN 'Partially allocated' WHEN '33' THEN 'Allocated' WHEN '44' THEN 'Picking list printed' WHEN '66' THEN 'Delivered' WHEN '77' THEN 'Invoiced' ELSE ol.OBORST END AS "Line status — the two-char ladder the line walks from entry through allocation, delivery, and invoicing",  -- status: ORST
  ol.OBITNO AS "Item ordered",
  ol.OBORQT AS "Ordered quantity in the basic unit",
  ol.OBDLQT AS "Delivered quantity so far",
  ol.OBIVQT AS "Invoiced quantity so far",
  ol.OBSAPR AS "Sales price per price unit on the line",
  ol.OBWHLO AS "Warehouse the line ships from",
  CASE WHEN ol.OBDWDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(ol.OBDWDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Planned delivery date for the line"  -- YYYYMMDD, 0 → NULL
FROM <catalog>.<schema>.OOLINE ol
WHERE
  ol.OBCONO = <company>
  -- AND ol.OBORNO = '<ORNO>'
  -- AND ol.OBDWDT >= <DATE_FROM>  -- yyyyMMdd numeric
  -- AND ol.OBDWDT <= <DATE_TO>  -- yyyyMMdd numeric
ORDER BY ol.OBORNO;

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

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

  • OOHEADOOLINEheader line · 1:N
    ON OOHEAD.OAORNO = OOLINE.OBORNO AND OOHEAD.OACONO = OOLINE.OBCONO
  • OOLINEMITMASforeign key · N:1
    ON OOLINE.OBITNO = MITMAS.MMITNO AND OOLINE.OBCONO = MITMAS.MMCONO
  • OOLINEMITWHLforeign key · N:1
    ON OOLINE.OBWHLO = MITWHL.MWWHLO AND OOLINE.OBCONO = MITWHL.MWCONO

Programs That Use This Table

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

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.