M3 Reference

MPDHED

Prefix: PHmaster

The product structure header — one row per product and structure type per facility, the design-time recipe that manufacturing orders are created from

Module: ManufacturingCompany-partitioned (CONO)

What the badges mean

Prefix: MM: Prefix: the table’s 2-character physical-column prefix (e.g. MM on MITMAS) — 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 than CONO alone (see the quirks guide).

Header & line

MPDHED is the header for its lines in MPDMAT.

Fields

4 fields · 4 key

4 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 4 fields.
Key	Field	Alias	Description	Type
Key	PHCONO	CONO	Company	numeric
Key	PHFACI	FACI	Facility the structure is defined for	alphanumeric
Key	PHPRNO	PRNO	Product the structure builds — joins to the item master on ITNO	alphanumeric
Key	PHSTRT	STRT	Structure type — distinguishes parallel recipes for the same product	alphanumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MPDHED 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

CatalogSchemaCompany (CONO)Facility (FACI)

Include optional filters (1)

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

-- ============================================================
-- Table  : MPDHED — The product structure header — one row per product and structure type per facility, the design-time recipe that manufacturing orders are created from
-- Purpose: Column-selected read of MPDHED — auto-generated from field metadata
-- Grain  : One row per company (CONO) + PHFACI + PHPRNO + PHSTRT
-- 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
  m.PHCONO AS "Company",
  m.PHFACI AS "Facility the structure is defined for",
  m.PHPRNO AS "Product the structure builds — joins to the item master on ITNO",
  m.PHSTRT AS "Structure type — distinguishes parallel recipes for the same product"
FROM <catalog>.<schema>.MPDHED m
WHERE
  m.PHCONO = <company>
  -- AND m.PHFACI = '<FACI>'
ORDER BY m.PHFACI;

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

MPDHEDMPDMATheader line · 1:N
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MPDHED.PHPRNO = MPDMAT.PMPRNO AND MPDHED.PHFACI = MPDMAT.PMFACI AND MPDHED.PHSTRT = MPDMAT.PMSTRT AND MPDHED.PHCONO = MPDMAT.PMCONO