M3 Reference
CRS610MI
APICustomer API — reads and maintains customers 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 CRS610MI 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: CRS610MI — Customer API — reads and maintains customers programmatically
-- Purpose: Read the tables behind API program CRS610MI — auto-generated from program-table-map
-- Grain : One row per OCUSMA record
-- Tables : 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
c.OKCONO AS "Company",
c.OKCUNO AS "Customer number — the natural key order headers join on",
c.OKCUNM AS "Customer name"
FROM <catalog>.<schema>.OCUSMA c
WHERE
c.OKCONO = <company>
ORDER BY c.OKCUNO;3 parameters not filled: <catalog>, <schema>, <company>