M3 Reference
MNS100
InteractiveCompany — connect division: where the CMNDIV divisions under a company are created and maintained
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 MNS100 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: MNS100 — Company — connect division: where the CMNDIV divisions under a company are created and maintained
-- Purpose: Read the tables behind program MNS100 — auto-generated from program-table-map
-- Grain : One row per CMNDIV record
-- Tables : CMNDIV
-- 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
h.CCCONO AS "Company",
h.CCDIVI AS "Division — the code divisional and financial tables carry",
h.CCTX40 AS "Division name"
FROM <catalog>.<schema>.CMNDIV h
WHERE
h.CCCONO = <company>
ORDER BY h.CCCONO;3 parameters not filled: <catalog>, <schema>, <company>