OOLINE
Prefix: OBtransactionThe 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
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
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | OBCONO | CONO | Company | numeric | ||
| Key | OBORNO | ORNO | Customer order number | alphanumeric | ||
| Key | OBPONR | PONR | Order line number | numeric | ||
| Key | OBPOSX | POSX | Line suffix — subdivides a line when it is split (e.g. partial deliveries) | numeric | ||
| OBORST | ORST | Line status — the two-char ladder the line walks from entry through allocation, delivery, and invoicing | alphanumeric | |||
| OBITNO | ITNO | Item ordered | alphanumeric | |||
| OBORQT | ORQT | Ordered quantity in the basic unit | numeric | |||
| OBDLQT | DLQT | Delivered quantity so far | numeric | |||
| OBIVQT | IVQT | Invoiced quantity so far | numeric | |||
| OBSAPR | SAPR | Sales price per price unit on the line | numeric | |||
| OBWHLO | WHLO | Warehouse the line ships from | alphanumeric | |||
| OBDWDT | DWDT | Planned delivery date for the line | numeric |
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.
-- ============================================================
-- 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.
Programs That Use This Table
- OIS100Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pairInteractive
- OIS100MICustomer order API — creates, reads, and maintains customer orders programmaticallyAPI
- OIS300Customer order overview — the order-book view planners and customer service work fromInteractive