Skip to content
M3 Reference

OIS100

Interactive

Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pair

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 SQL

Starting point for reading the tables behind OIS100 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: OIS100 — Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pair
-- Purpose: Read the tables behind program OIS100 — auto-generated from program-table-map
-- Grain  : OOHEAD × OOLINE, OCUSMA — 1:N joins yield one row per line
-- Tables : OOHEAD, OOLINE, OCUSMA
-- 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",
  c.OKCUNM AS "Customer name"
FROM <catalog>.<schema>.OOHEAD oh
LEFT JOIN <catalog>.<schema>.OOLINE ol
  ON ol.OBORNO = oh.OAORNO
 AND ol.OBCONO = oh.OACONO
LEFT JOIN <catalog>.<schema>.OCUSMA c
  ON c.OKCUNO = oh.OACUNO
 AND c.OKCONO = 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.

Join details

  • OOHEADOOLINEheader line · 1:N
    ON OOHEAD.OAORNO = OOLINE.OBORNO AND OOHEAD.OACONO = OOLINE.OBCONO
  • OOHEADOCUSMAforeign key · N:1
    ON OOHEAD.OACUNO = OCUSMA.OKCUNO AND OOHEAD.OACONO = OCUSMA.OKCONO

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.