MKPF table — Material Document Header Table MKPF

A row in MKPF represents the header of one material document, the object created every time an MM goods movement is posted, whether through a goods receipt against a purchase order, a goods issue to a cost center or reservation, a transfer posting between plants or storage locations, or a physical inventory difference posting. The header carries information common to the whole document: who posted it, when it was posted, when it was entered into the system, what reference document or external document number was attached, and which transaction or process triggered the posting. It does not carry material, quantity, plant or movement type; those live one level down, in the material document item table. A material document can have many items under one header, so MKPF is always the smaller, coarser-grained table of the pair, and querying it alone tells you a movement happened and who caused it, not what actually moved.

MANDT is always the first restriction. After that, MKPF is only ever usefully queried with a document number and year, or a posting date range plus another restriction such as user or transaction code, because on any live productive system it accumulates one row per goods movement across every plant and every material, which on a mature system means many millions of rows. Never select from MKPF on BUDAT alone across a wide date range without a second filter; it will scan the whole table. If the requirement is to find movements for a given material or plant, that filter exists on MSEG, not MKPF, so start the query there and join up to MKPF for the date and user, rather than starting in MKPF and joining down.

Symptom: a warehouse team claims goods receipt 5000012345 was never posted, but stock on hand looks correct. Selection: read MKPF on MBLNR and MJAHR for the document number quoted; if a row exists, the document was posted, note BUDAT, CPUDT and USNAM. Then join to MSEG on the same key to confirm which plant, storage location and material actually received quantity, since the header alone cannot confirm what moved, only that something was posted and by whom.

MKPF continues to exist as a transparent table in S/4HANA and is still written by standard goods movement postings, so existing reports and joins against it keep working. Under the covers, S/4HANA consolidates material document header and item data into the universal journal-adjacent table MATDOC, and MKPF/MSEG are exposed as compatibility views over that structure for classic ABAP programs and custom code. New developments are generally steered toward MATDOC or the corresponding CDS views rather than direct MKPF/MSEG selects, but nothing in a functional consultant's day-to-day analysis changes.

A question about a specific document header, such as who posted it or on what date, is a functional MM inventory management question, owned by whoever configured goods movement processes. Questions about the underlying table structure, indexing, or migration behavior into MATDOC belong to the technical/Basis or ABAP development side, particularly during an S/4HANA conversion project.

MSEG is the item table that always accompanies MKPF and holds the actual movement data. EKBE records the purchase order history entries that a goods receipt movement generates. EKKO and EKPO are the purchase order header and item behind receipts posted with reference to a PO. Transactions that write MKPF include goods movement postings, goods receipt against purchase order, and physical inventory count postings; reversal and cancellation transactions also write new MKPF rows rather than modifying existing ones.