MPAGRH
Prefix: AHmasterThe purchase agreement header — one row per supplier purchase agreement (agreement number), the negotiated terms record purchase-order pricing draws from
Infor documents this table's name but none of its field names, and the prefix is absent from the Cross-BOD mapping material, so the AH prefix behind every field row below rests on practitioner sources alone — confirm the AH* column names against your landed schema before building on them. The header's grain is unverified too: whether the supplier (AHSUNO) belongs to the key, or the agreement number alone is unique per company, is not established. Agreement lines live in MPAGRL, whose column prefix is not yet verified from a second source — it joins the catalog in a later wave.
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — 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 thanCONOalone (see the quirks guide).
Fields
3 fields · 3 key
3 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | AHCONO | CONO | Company | numeric | ||
| Key | AHAGNB | AGNB | Agreement number — the purchase agreement's identity | alphanumeric | ||
| Key | AHSUNO | SUNO | Supplier the agreement is held with — the join to CIDMAS | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MPAGRH 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.
5 parameters not filled: <catalog>, <schema>, <company>, <AGNB>, <SUNO>
-- ============================================================
-- Table : MPAGRH — The purchase agreement header — one row per supplier purchase agreement (agreement number), the negotiated terms record purchase-order pricing draws from
-- Purpose: Column-selected read of MPAGRH — auto-generated from field metadata
-- Grain : Key columns as cataloged: company (CONO) + AHAGNB + AHSUNO — not primary-source verified as the row key (see the table notes)
-- 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.AHCONO AS "Company",
m.AHAGNB AS "Agreement number — the purchase agreement's identity",
m.AHSUNO AS "Supplier the agreement is held with — the join to CIDMAS"
FROM <catalog>.<schema>.MPAGRH m
WHERE
m.AHCONO = <company>
-- AND m.AHAGNB = '<AGNB>'
-- AND m.AHSUNO = '<SUNO>'
ORDER BY m.AHAGNB;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
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MPAGRH.AHSUNO = CIDMAS.IDSUNO AND MPAGRH.AHCONO = CIDMAS.IDCONO
Programs That Use This Table
- PPS100 — Purchase agreement maintenance — 'Purchase Agreement. Open', where supplier purchase agreements are created and maintained; the agreement file set is MPAGRH (header), MPAGRL (lines) and MPAGRP (prices), of which only MPAGRH is catalogedPrimary sourceInteractive
- PPS535 — Purchase agreement print report — 'Purchase Agreement. Print Report', a report writer that prints agreement-line data from the agreements held in MPAGRH; the maintenance program is PPS100Primary sourceInteractive
More Purchasing tables
- MPHEADThe purchase order header — one row per order, carrying the supplier, order date, currency, receiving warehouse, and the lowest/highest line status pair mirroring the customer-order pattern
- MPLINEThe purchase order line — one row per ordered item with quantity, price, planned delivery date, and the lowest/highest line-status pair; the core buy-side transaction, joined to its header by PUNO
- CIDMASThe supplier master — one row per supplier per company with identity, status, and name; purchasing and supplier-ledger records join back to it on SUNO