MBST — Cancel Material Document
MBST cancels a previously posted material document by generating a reversal posting with the opposite quantity and movement type. It does not delete the original document. Both the original and the reversal remain in the system, linked by reference, and both update stock quantities, valuation and any FI/CO documents that followed from the original posting.
MBST is the transaction used to reverse a goods movement that was posted incorrectly, by creating a linked cancellation document rather than deleting the original. The page covers the entry sequence, the tables the reversal writes to, and the recurring reasons cancellation gets blocked or produces an unexpected value.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,280 words
Purpose
MBST cancels a material document that was posted through a prior goods movement (goods receipt, goods issue, transfer posting, and so on). The structural fact that explains most of the confusion around it: MBST never deletes the original document. It posts a new material document with the reversed quantity and an offsetting movement type, cross-referenced to the original, and flags the original as cancelled. Stock quantities, valuation, and any accounting document generated by the original posting are all updated by this new reversal document, not by editing history. Anyone querying stock movements after a cancellation will see two documents for what looks like one physical event, and reports that do not account for the reversal will overstate movement counts.
When it is used
MBST is reached for after a goods movement has already posted with a wrong quantity, wrong plant or storage location, wrong movement type, or wrong material, and the correction cannot be done by simply posting an adjusting entry because the movement affects stock value, PO history, or order confirmation. It is the standard tool for a single-document, full or line-item reversal. It is not the right tool for partial quantity corrections that are better handled inside MIGO's own cancel function at the time of entry, and it is not used when the error is purely in a purchase order or reservation with no goods movement yet posted - that is corrected directly on the PO or reservation instead.
How to use it in practice
- Open MBST and enter the material document number and the material document year - both are required, the year is not defaulted reliably across fiscal years.
- Let the system pull in the document; review the line items and posting date proposed for the reversal.
- Adjust the reversal reason code and posting date if the original posting date falls in a closed period.
- Execute the cancellation; the system creates the reversal document and, where relevant, the corresponding accounting document.
- Check the message returned for the new material document number and confirm the accounting document was generated with the expected value.
- Use MB03 afterward to display both the original and the reversal side by side and confirm the linkage.
Key data objects
- Material document header table - stores the reversal document header, its reference to the original document number and year, and the posting/document dates used for the reversal.
- Material document item table - stores the reversed quantities and movement type per line, and carries the link back to the original document's line items.
- Stock quantity tables at plant and storage location level - updated by the reversal exactly as they would be by any normal goods movement, moving quantity back to where it was before the original posting.
- Accounting document tables - a new FI document is generated for the reversal if the original posting was valuation-relevant; this is where a moving-average price mismatch between the two postings shows up.
- Purchase order history, if the original document was tied to a PO - the reversal writes a new history line rather than removing the original receipt line.
How to prove it in the data
Pull the original material document number and year from the user and look it up in the material document item table by document number and item; the reversal document number is carried as a cross-reference field on that same item. Pull that reversal document and compare posted quantity, movement type and posting date against the original. If the value looks wrong, pull both accounting documents by the material document's reference and compare the amounts line by line rather than assuming the reversal simply negates the original - moving-average valuation can produce a different amount if other movements posted in between.
ECC vs S/4HANA
MBST behaves the same on S/4HANA as on ECC. The underlying material document tables are exposed through the newer consolidated document table structure, but the transaction's screens, entry logic, and the fact that it reverses rather than deletes are unchanged. A Fiori app covering goods movement management exists in some releases, but MBST remains the transaction most consultants still reach for directly, and nothing about diagnosing a blocked cancellation changes between the two.
Common pitfalls and how to diagnose them
- Already cancelled: the system refuses a second cancellation attempt on a document that already carries a reversal reference. Check the material document item table for an existing cross-reference to a reversal document before assuming the cancellation never happened - the original request may already have been actioned by someone else.
- Blocked by downstream postings: if the original document is a goods receipt against a PO and an invoice has already been posted against it, cancellation is refused or, if forced through a workaround, leaves the invoice history inconsistent. Check the PO history for an invoice receipt line before attempting cancellation; the invoice has to be reversed first through the invoice verification transaction.
- Posting period closed: the reversal has to post into an open MM period. The usual error names the period. The wrong fix is changing the system date; the right fix is either using a posting date that falls in the currently open period or having the correct period reopened, which is a controlled action, not something to do unilaterally because a closed period is usually closed for a reconciliation reason.
- Valuation mismatch on moving-average materials: reversing a receipt or issue after other movements have changed the moving average price produces an accounting document with a different value than the original, which is expected behavior, not a bug, but is frequently reported as one. Compare both accounting documents rather than assuming the reversal amount should mirror the original.
- Linked WM transfer order or quality inspection lot: if the original goods movement triggered a warehouse transfer order or a quality inspection lot that has already been processed, MBST is blocked until that linked object is cleared. Check for open transfer orders or inspection lots referencing the material document before escalating as an MBST defect.
- Manual correction instead of proper reversal: posting an opposite movement by hand through a goods movement transaction instead of using MBST breaks the document chain. Both documents then sit in the system with no formal reversal link, which complicates any later audit of quantity and value and should be avoided even when it looks faster.
Whose problem this is
This is a functional MM issue in almost every case - inventory management or invoice verification depending on what is blocking the reversal. ABAP involvement is rare and limited to custom validations or user exits that add extra cancellation checks. A clean handover includes the material document number and year, the reason for reversal, whether a PO and invoice are involved, and whether the posting period in question is still open.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mbstERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.