Skip to content
M3 Reference

CRS610MI

API

Customer 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

Verified transactions include GetBasicData, ChgBasicData, AddAddress, ChgAddress, GetOrderInfo, and ChgFinancial, named in Infor's published M3 Cross-BOD mapping. Search-query (SQRY) transactions also exist; the API exposes more than these.

Boilerplate SQL

Databricks SQL

Starting 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

3 parameters not filled: <catalog>, <schema>, <company>

-- ============================================================
-- 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 a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline; 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.OKSTAT AS "Customer status — whether the customer is active for new business",  -- status: decode c.OKSTAT against your configuration — see quirks guide #statuses
  c.OKCUNM AS "Customer name"
FROM <catalog>.<schema>.OCUSMA c
WHERE
  c.OKCONO = <company>
ORDER BY c.OKCUNO;

Backing Tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

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.