M3 Reference
OIS101
InteractiveCustomer order line entry — the line-level screen reached from OIS100, where the OOLINE rows under an OOHEAD header are entered and changed
Tables vs APIs
This program works over the tables below. For analytics at scale, land the raw tables — the SQL further down reads them directly, joined on their keys and CONO. When to land tables vs call MI APIs →
Boilerplate SQL
Databricks SQLStarting point for reading the tables behind OIS101 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.
Query parameters
-- ============================================================
-- Program: OIS101 — Customer order line entry — the line-level screen reached from OIS100, where the OOLINE rows under an OOHEAD header are entered and changed
-- Purpose: Read the tables behind program OIS101 — auto-generated from program-table-map
-- Grain : OOLINE × OOHEAD — 1:N joins yield one row per line
-- Tables : OOLINE, OOHEAD
-- 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; company-partitioned tables are joined on CONO to prevent cross-company fan-out. 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)",
ol.OBITNO AS "Item ordered",
ol.OBORQT AS "Ordered quantity in the basic unit"
FROM <catalog>.<schema>.OOLINE ol
LEFT JOIN <catalog>.<schema>.OOHEAD oh
ON oh.OAORNO = ol.OBORNO
AND oh.OACONO = ol.OBCONO
WHERE
ol.OBCONO = <company>
ORDER BY ol.OBORNO;3 parameters not filled: <catalog>, <schema>, <company>
Backing Tables
How these tables connect. Nodes are clickable.