M3 Reference
PPS535
InteractivePurchase agreement maintenance — the agreement-creation flow, where supplier purchase agreements are opened and maintained, writing the MPAGRH header; agreement lines (MPAGRL) are not yet cataloged
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 PPS535 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: PPS535 — Purchase agreement maintenance — the agreement-creation flow, where supplier purchase agreements are opened and maintained, writing the MPAGRH header; agreement lines (MPAGRL) are not yet cataloged
-- Purpose: Read the tables behind program PPS535 — auto-generated from program-table-map
-- Grain : One row per MPAGRH record
-- Tables : MPAGRH
-- 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.AHCONO AS "Company",
h.AHAGNB AS "Agreement number — the purchase agreement's identity",
h.AHSUNO AS "Supplier the agreement is held with — the join to CIDMAS"
FROM <catalog>.<schema>.MPAGRH h
WHERE
h.AHCONO = <company>
ORDER BY h.AHAGNB;3 parameters not filled: <catalog>, <schema>, <company>