MDKP table — MRP List Header Table

MDKP stores the header of an MRP list result for a material within a plant, optionally scoped to an MRP area and a planning scenario. One row represents one planning evaluation result header, the outcome of an MRP run or of opening the stock/requirements list for a given material and plant at a point in time, holding the identifying keys and control indicators needed to link to the detailed line items stored separately in MDTB. It does not carry requirement quantities, dates, or order references itself, those belong to MDTB. The record functions as a pointer or session header for the current planning view rather than as durable master data, and it is overwritten each time the material is re-evaluated or re-planned, so it should never be read as a history of past MRP runs.

MDKP is client-dependent like every table here, but the effective filter always has to be material plus plant, and MRP area if that is in use; scanning the table without those restrictions returns whatever happens to be cached at that moment and means nothing as a report. Because the table is regenerated on every MRP run or every fresh MD04 call, there is no reliable time dimension to select on, so date-range queries against it are not meaningful. Treat it strictly as a lookup keyed to one material and plant combination, read together with MDTB, never as a standalone analytical source.

To check whether a stated MD04 result reflects an actual cached evaluation for material X in plant Y, select MDKP where MATNR = X and WERKS = Y, including BERID if the material is MRP-area managed. If no row exists, no MRP list has been cached for that combination and the next MD04 call will trigger a fresh live calculation rather than display a stored result, which explains discrepancies between what two users see at slightly different times.

MDKP continues to exist in S/4HANA in the same technical shape and is still populated by the classical MRP list mechanism underneath transactions like MD04, MD05, and MD06. There is no widely published CDS-based replacement specifically for MDKP, but newer S/4HANA planning and MRP monitoring Fiori apps generally read current planning data through their own services rather than through this table directly. It is best treated as legacy plumbing that still works, not as the primary interface into current planning results in an S/4HANA context.

Questions about MDKP content belong to PP or PP-MRP functional consultants, since the table is populated purely as a side effect of the MRP run and of MRP list display transactions. Missing or stale rows are investigated through MRP run configuration and scope of planning, not through direct table maintenance. Basis involvement is limited to locking or table growth concerns, not data content.

MDTB carries the actual list line items that sit under an MDKP header, keyed by the same material and plant. PLAF, AFKO and AFPO, RESB, and PBIM and PBED represent the real underlying objects, planned orders, production orders, reservations, and planning independent requirements, that MDTB lines point to in abstract form. MD04, MD05, MD06 and the MRP run transactions MD01, MD02, and MD03 are what generate or refresh the MDKP snapshot.