What’s the Difference Between Cancellation and Reversal in SAP MM?

Let’s get this straight upfront, cancellation and reversal might seem like techy twins in SAP, but they play two totally different roles depending on *when* and *why* you’re making changes to a purchase order. Think of it like this: cancellation is backing out before the goods show up at your door, while reversal is about sending something back *after* it’s already arrived. Let’s break it down with real-world context, practical SAP know-how, and a bit of coffee-shop-style clarity.

So, What Actually Is a Cancellation?

Imagine you ordered 100 chairs for your office. Before they even leave the vendor’s warehouse, you realize you only need 50. No harm done, you cancel the rest.

In SAP terms:

  • Cancellation happens before the goods are received.
  • You're telling the system: “Forget this transaction. We’re not moving forward with it.”
  • No material has entered your inventory yet.
This is common when:
  • A department changes their mind.
  • A vendor delays too long.
  • There was a mistake in the purchase order.
You’re essentially stopping a process before it impacts stock. Clean, simple, and (hopefully) painless.

Reversal: When Things Don’t Go as Planned *After* Receipt

Now let’s say those chairs *did* arrive, but half of them are scratched up. You’ve already received them into inventory via MIGO, but now you need to undo that transaction. That’s where reversal comes in.

In SAP speak:

  • Reversal happens after a goods receipt has been posted.
  • You're removing items from inventory to correct or return them.
  • This could be due to damage, wrong delivery, or internal posting errors.
This action updates the stock and financial documents to reflect the correction. It’s like hitting the "undo" button, but with real inventory consequences.

Key SAP Movement Types: Explained Simply

Alright, this is where most folks start to get a little cross-eyed. SAP uses movement types to tell the system *what’s actually happening* with stock. Here’s the essential cheat sheet:

Movement Type 102: Reversal of Goods Receipt

  • Used when you need to reverse a 101 (Goods Receipt).
  • Can be triggered by mistake postings, wrong deliveries, or other corrections.
  • Works for both cancellation and reversal scenarios in MIGO depending on context.

Movement Type 122: Return Delivery to Vendor

  • Used when goods are physically sent back to the vendor.
  • Doesn’t fall under cancellation or basic reversal, it’s a separate return process.

Movement Type 161: Goods Issue for Returns PO

  • Used for returns purchase orders (POs marked with the “Returns” flag).
  • Physically removes stock and creates a return delivery document.
  • Useful when you’ve agreed with the vendor to send goods back.

Movement Type 162: Reversal of 161

  • Basically a “whoops” undo if you post a 161 return by mistake.

Here’s the Thing: The Meaning vs the Mechanics

You might be wondering, “If both cancellation and reversal use 102 sometimes, what’s the actual difference?” Great question. It’s not about the how, it’s about the why and when.
 
Aspect Cancellation Reversal
When It Happens Before goods receipt is finalized After goods receipt is posted
Reason Change of plan, error before delivery Quality issue, wrong item, posted in error
System Action Stops the process, no stock impact Adjusts stock, corrects financial posting
Movement Type Often 102 102, 122, 161 depending on case
Vendor Involved? Usually not Often, especially with returns

A Real-World SAP MM Scenario

Let’s say you're managing procurement for a retail chain. You ordered 500 light fixtures:
  • Day 1: You realize you only need 300 → Cancel 200 before GR
  • Day 5: You receive all 500, but 100 are defective → Reverse 100 using 102
  • Day 7: You arrange a return to the vendor → Use 122 or create returns PO with 161
Same items. Three different processes. This is why SAP pros get paid well, it’s all about knowing the right tool for the job.

Quick Tips to Remember

  • Always check whether the goods have been posted into inventory. That’s your decision trigger.
  • 102 is versatile, don’t assume it only means one thing.
  • Use 161 for structured returns with vendor documentation.
  • Use 122 when there’s physical movement back to vendor but no returns PO.

Final Thought

The difference between cancellation and reversal in SAP isn’t just semantic, it’s operational. Getting this right means cleaner records, fewer reconciliation headaches, and smoother supply chain workflows. So next time someone asks, “Should we cancel or reverse this PO?”, you’ll know exactly how to respond (and maybe even impress your team a little).

Related:

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP Material Management Books
SAP MM Books - Certification, Interview Questions and Configuration

SAP Materials Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.