M3 Reference
PDS002
InteractiveProduct structure materials and operations — connects components to a structure, writing the MPDMAT lines under their MPDHED header
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 PDS002 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.
Query parameters
-- ============================================================
-- Program: PDS002 — Product structure materials and operations — connects components to a structure, writing the MPDMAT lines under their MPDHED header
-- Purpose: Read the tables behind program PDS002 — auto-generated from program-table-map
-- Grain : MPDMAT × MPDHED — 1:N joins yield one row per line
-- Tables : MPDMAT, MPDHED
-- 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; 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
h.PMCONO AS "Company",
h.PMFACI AS "Facility",
h.PMPRNO AS "Product the structure builds",
h.PMSTRT AS "Structure type",
h.PMMSEQ AS "Material sequence number within the structure",
h.PMMTNO AS "Component item — joins to the item master on ITNO"
FROM <catalog>.<schema>.MPDMAT h
LEFT JOIN <catalog>.<schema>.MPDHED m
ON m.PHPRNO = h.PMPRNO
AND m.PHFACI = h.PMFACI
AND m.PHSTRT = h.PMSTRT
AND m.PHCONO = h.PMCONO
WHERE
h.PMCONO = <company>
ORDER BY h.PMFACI;3 parameters not filled: <catalog>, <schema>, <company>
Backing Tables
How these tables connect. Nodes are clickable.