M3 Reference
CRS620
InteractiveSupplier maintenance — where suppliers are created and their CIDMAS identity managed
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 CRS620 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: CRS620 — Supplier maintenance — where suppliers are created and their CIDMAS identity managed
-- Purpose: Read the tables behind program CRS620 — auto-generated from program-table-map
-- Grain : One row per CIDMAS record
-- Tables : CIDMAS
-- 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
s.IDCONO AS "Company",
s.IDSUNO AS "Supplier number — the natural key purchase orders join on",
s.IDSTAT AS "Supplier status — whether the supplier is active for new business", -- status: decode s.IDSTAT against your configuration — see quirks guide #statuses
s.IDSUNM AS "Supplier name"
FROM <catalog>.<schema>.CIDMAS s
WHERE
s.IDCONO = <company>
ORDER BY s.IDSUNO;