M3 Reference
PDS001
InteractiveProduct structure maintenance — where the MPDHED design-time recipes are opened and created
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 PDS001 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: PDS001 — Product structure maintenance — where the MPDHED design-time recipes are opened and created
-- Purpose: Read the tables behind program PDS001 — auto-generated from program-table-map
-- Grain : One row per MPDHED record
-- Tables : 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.PHCONO AS "Company",
h.PHFACI AS "Facility the structure is defined for",
h.PHPRNO AS "Product the structure builds — joins to the item master on ITNO",
h.PHSTRT AS "Structure type — distinguishes parallel recipes for the same product"
FROM <catalog>.<schema>.MPDHED h
WHERE
h.PHCONO = <company>
ORDER BY h.PHFACI;3 parameters not filled: <catalog>, <schema>, <company>