MB03 — Display Material Document

MB03 shows a material document that already exists in the system: header data (document number, fiscal year, posting date, document date, entering user, header text) and the line items belonging to it (material, plant, storage location, batch, movement type, quantity, purchase order reference where relevant). The structural fact that explains almost all confusion around this transaction is that a material document, once posted, is immutable. There is no update path inside MB03. Every apparent need to fix a wrong quantity, wrong plant, or wrong movement type actually requires either a reversal transaction or a brand new movement that offsets the original. MB03 is purely diagnostic: it tells a consultant what happened, not how to undo it.

MB03 gets used whenever someone needs to confirm what a goods movement actually recorded, independent of what the purchase order or the stock overview currently shows. Typical triggers: an invoice verification in MIR7 is blocking on a quantity or price variance and the consultant needs to see the exact GR quantity and value; a stock discrepancy surfaces in MB52 and the history of movements against that material needs tracing; a user disputes that a goods issue happened; or an accounting entry in FI needs to be traced back to its originating logistics document. In S/4HANA the Fiori app for material document display covers the same need with a friendlier list and drilldown, but MB03 remains faster for a consultant who already has the document number in hand.

Take the document number and fiscal year shown on the MB03 header and query MSEG in SE16 filtered on MBLNR and MJAHR to see the raw line items, including BWART, EBELN, EBELP and the reversal-link field. Cross-check EKBE on the same PO and item to confirm the purchase order history was actually updated. If a reversal is suspected, filter MSEG or MKPF for the SMBLN field pointing back to the original document number.

MB03 still runs on S/4HANA and reads the same underlying data model, now consolidated into the MATDOC table with compatibility views feeding MKPF and MSEG for older transactions. SAP's preferred entry point going forward is the Fiori app for managing material documents, which offers list-based search and multi-document comparison, but MB03 has not been withdrawn and remains reliable for single-document lookups.

Functional MM issue in almost every case, since the transaction is display-only and any downstream problem is a process or master data question, not a technical one. A clean handover to a functional consultant includes the material document number and fiscal year, the movement type, and whether the discrepancy is against the PO history, the accounting document, or the physical stock count.

MB1A, MB1B and MB1C are the posting transactions that create the documents MB03 displays; understanding one clarifies the other. MBST is the reversal counterpart, needed whenever MB03 reveals a movement that must be undone rather than merely explained. MB52 and MB5L are the stock-overview and valuation reports consultants typically consult before or after tracing a specific document in MB03. MIR7 depends on the same GR data when an invoice is being parked or verified against a receipt.