M3 Reference
CIDMAS
Prefix: IDmasterThe supplier master — one row per supplier per company with identity, status, and name; purchasing and supplier-ledger records join back to it on SUNO
Module: PurchasingCompany-partitioned (CONO)
Fields
4 fields · 2 key
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | IDCONO | CONO | Company | numeric | ||
| Key | IDSUNO | SUNO | Supplier number — the natural key purchase orders join on | alphanumeric | ||
| IDSTAT | STAT | Supplier status — whether the supplier is active for new business | alphanumeric | |||
| IDSUNM | SUNM | Supplier name | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading CIDMASon Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
Query parameters
-- ============================================================
-- Table : CIDMAS — The supplier master — one row per supplier per company with identity, status, and name; purchasing and supplier-ledger records join back to it on SUNO
-- Purpose: Column-selected read of CIDMAS — auto-generated from field metadata
-- Grain : One row per company (CONO) + IDSUNO
-- 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. 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>
-- AND s.IDSUNO = '<SUNO>'
ORDER BY s.IDSUNO;4 parameters not filled: <catalog>, <schema>, <company>, <SUNO>
Relationships
1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.