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)
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide). - master
- Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
- Shared across companies
- The table carries no
CONO— rows aren’t partitioned per company (see the quirks guide). - Division-level
- The table carries
DIVI— rows are scoped below company to a division, one layer more granular thanCONOalone (see the quirks guide).
In field listings, K marks a primary-key field.
Used in the library
KPI definitions
Dashboard patterns
Fields
4 fields · 2 key
4 fields.
| 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 CIDMAS on 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
4 parameters not filled: <catalog>, <schema>, <company>, <SUNO>
-- ============================================================
-- 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 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. 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;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITBAL.MBSUNO = CIDMAS.IDSUNO AND MITBAL.MBCONO = CIDMAS.IDCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MPHEAD.IASUNO = CIDMAS.IDSUNO AND MPHEAD.IACONO = CIDMAS.IDCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MPAGRH.AHSUNO = CIDMAS.IDSUNO AND MPAGRH.AHCONO = CIDMAS.IDCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON FPLEDG.EPSUNO = CIDMAS.IDSUNO AND FPLEDG.EPCONO = CIDMAS.IDCONO
Programs That Use This Table
More Purchasing tables
- MPAGRHThe purchase agreement header — one row per supplier purchase agreement (agreement number), the negotiated terms record purchase-order pricing draws from
- MPHEADThe purchase order header — one row per order, carrying the supplier, order date, currency, receiving warehouse, and the lowest/highest line status pair mirroring the customer-order pattern
- MPLINEThe purchase order line — one row per ordered item with quantity, price, planned delivery date, and the lowest/highest line-status pair; the core buy-side transaction, joined to its header by PUNO