MATDOC table — MATDOC Material Document Table in S/4HANA

One row in MATDOC represents one item of one material document, carrying both the header attributes that used to sit in MKPF (posting date, document date, entry user, entry timestamp) and the item attributes that used to sit in MSEG (material, plant, storage location, movement type, quantity, value). It is the single source of truth for every goods movement posted through goods receipt, goods issue, transfer posting, or physical inventory adjustment. Because it was built for the merged finance and material ledger data model, it also carries parallel currency and quantity fields that MSEG never had, so a document that touches multiple valuation views or ledgers can populate several extension columns for the same movement.

Always restrict on MANDT implicitly and never select the whole table without a plant, material, or date range. MATDOC is one of the largest tables in an S/4HANA system because every goods movement of every company posts a row here, so a query without WERKS or a BUDAT range will scan far more than intended even with HANA underneath. The most selective single restriction is MBLNR plus MJAHR when a specific document is known. For a period or material analysis, restrict on MATNR, WERKS, and a BUDAT range before adding movement type filters. Do not assume the extension fields for parallel currency and quantity are always populated, since data migrated from a classic system before conversion may leave some of them blank.

Symptom: stock for a material in a plant changed unexpectedly on a given day. Select MATDOC with MATNR equal to the material, WERKS equal to the plant, and BUDAT equal to the date in question. Read BWART to identify the movement type, MENGE and SHKZG together to get the signed quantity delta, and EBELN/EBELP if the row should be tied to a purchase order. If several rows appear under the same MBLNR and MJAHR, the document had multiple items, often from batch split or account assignment split, and each must be summed separately before comparing to the stock overview.

MATDOC was introduced as part of the S/4HANA simplification of inventory management and material ledger, replacing the physical storage of MKPF and MSEG with one wide table. MSEG and MKPF remain available as compatibility views built on top of MATDOC, so existing custom reports and interfaces that read them continue to function without change. New fields, particularly the parallel currency and additional valuation quantity columns needed for the merged material ledger, exist only in MATDOC and are not exposed through the classic views, so any development that needs that data has to query MATDOC or a released CDS view directly rather than MSEG.

The MM or inventory management functional consultant owns questions about whether a movement type, quantity, or valuation on a given document is correct. Custom code that queries MATDOC directly, or that breaks because it assumed MSEG structure, is a technical or Basis-adjacent problem for the ABAP team. During an S/4HANA conversion, the migration or data validation workstream owns reconciling that stock quantities and values carried over correctly from the old MSEG-based data into MATDOC.

MSEG and MKPF are the classic tables now implemented as compatibility views reading from MATDOC. EKPO supplies the purchase order line referenced by a goods movement, and MBEW and MARD hold the resulting valuation and storage location stock that a MATDOC posting updates. The primary transaction writing to MATDOC is MIGO, along with the older movement-specific transactions such as goods issue and transfer posting screens, all of which post through the same underlying goods movement function rather than any direct table update.