M3 Reference
OIS100MI
APICustomer order API — creates, reads, and maintains customer orders programmatically
Tables vs APIs
This MI API 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 →
Notes
Get/List and search-query (SQRY) transactions confirmed to exist; the full transaction list is verified in Phase 2.
Boilerplate SQL
Databricks SQLStarting point for reading the tables behind OIS100MI 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: OIS100MI — Customer order API — creates, reads, and maintains customer orders programmatically
-- Purpose: Read the tables behind API program OIS100MI — auto-generated from program-table-map
-- Grain : OOHEAD × OOLINE — 1:N joins yield one row per line
-- Tables : OOHEAD, OOLINE
-- 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
oh.OACONO AS "Company",
oh.OAORNO AS "Customer order number — the key order lines join on",
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>.OOHEAD oh
LEFT JOIN <catalog>.<schema>.OOLINE ol
ON ol.OBORNO = oh.OAORNO
AND ol.OBCONO = oh.OACONO
WHERE
oh.OACONO = <company>
ORDER BY oh.OAORNO;3 parameters not filled: <catalog>, <schema>, <company>
Backing Tables
How these tables connect. Nodes are clickable.