Skip to content
M3 Reference

MPDMAT

Prefix: PMmaster

Product structure materials — one row per component in a product structure, with the quantity consumed per unit produced; the design-time counterpart of MWOMAT, joined to its header by PRNO + STRT

Module: ManufacturingCompany-partitioned (CONO)Header: MPDHED
Notes

Operations live in MPDOPE, whose column prefix is not yet verified — it joins the catalog in a later wave.

Header & line

MPDMAT lines join back to their header MPDHED — and the CONO — so a line never fans out across companies.

Fields

7 fields · 5 key

KeyFieldAliasDescriptionTypeLengthFlags
KeyPMCONOCONOCompanynumeric
KeyPMFACIFACIFacilityalphanumeric
KeyPMPRNOPRNOProduct the structure buildsalphanumeric
KeyPMSTRTSTRTStructure typealphanumeric
KeyPMMSEQMSEQMaterial sequence number within the structurenumeric
PMMTNOMTNOComponent item — joins to the item master on ITNOalphanumeric
PMCNQTCNQTQuantity of the component consumed per unit producednumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MPDMATon 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  : MPDMAT — Product structure materials — one row per component in a product structure, with the quantity consumed per unit produced; the design-time counterpart of MWOMAT, joined to its header by PRNO + STRT
-- Purpose: Column-selected read of MPDMAT — auto-generated from field metadata
-- Grain  : One row per company (CONO) + PMFACI + PMPRNO + PMSTRT + PMMSEQ
-- 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
  m.PMCONO AS "Company",
  m.PMFACI AS "Facility",
  m.PMPRNO AS "Product the structure builds",
  m.PMSTRT AS "Structure type",
  m.PMMSEQ AS "Material sequence number within the structure",
  m.PMMTNO AS "Component item — joins to the item master on ITNO",
  m.PMCNQT AS "Quantity of the component consumed per unit produced"
FROM <catalog>.<schema>.MPDMAT m
WHERE
  m.PMCONO = <company>
  -- AND m.PMFACI = '<FACI>'
ORDER BY m.PMFACI;

4 parameters not filled: <catalog>, <schema>, <company>, <FACI>

Relationships

1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MPDHEDMPDMATheader line · 1:N
    ON MPDHED.PHPRNO = MPDMAT.PMPRNO AND MPDHED.PHFACI = MPDMAT.PMFACI AND MPDHED.PHSTRT = MPDMAT.PMSTRT AND MPDHED.PHCONO = MPDMAT.PMCONO

Programs That Use This Table

No program mappings populated for this table yet.

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

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.