The PO Confirmation Control Key in
SAP: A Deep Dive Explained Simply
ERP SAP ==>
SAP
Material Managment
Imagine you're a procurement specialist juggling dozens
of POs. Now imagine not knowing *when* goods will arrive. That’s where
the Confirmation Control Key steps in — acting like a smart GPS signal
for your incoming deliveries.
What Is a PO Confirmation Control Key?
At its core, the Confirmation Control Key is a setting in
SAP used within the Confirmations tab of a Purchase Order (PO) item. It
tells the system what kind of delivery confirmations are expected from
the vendor — such as:
-
Order Acknowledgment
-
Shipping Notification
-
Inbound Delivery
-
GR (Goods Receipt) relevance
This setup ensures better tracking, planning, and inventory
management. It basically answers the question: “Do we need a heads-up
from the vendor before they ship, and should we rely on it to process goods
receipt?”
Why Use It? Real-World Scenario
Let’s say you’re ordering expensive turbine parts from
an overseas vendor with a 12-week lead time. You don’t want to guess
the arrival date. Instead, by setting a confirmation control key, you:
-
Request a shipping notice or inbound delivery in advance
-
Get the ETA into your availability check
-
Prevent premature GR postings (no more “we thought it arrived”
situations)
This gives better visibility, tighter inventory control,
and cleaner MIGO transactions.
How It Works Behind the Scenes (SAP Behavior)
Once a confirmation control key is set:
-
GR posting in MIGO is blocked until confirmation (like inbound
delivery) is received.
-
MIGO will only allow GR for the quantity that’s been confirmed.
-
It prevents guessing or misposting of received goods.
In other words, it adds a layer of validation between the
PO and warehouse operations.
Where and How to Set It Up
SAP Configuration Path:
SPRO -> Materials Management -> Purchasing -> Confirmations
-> Setup Confirmation Control
OR use TCode: OMGZ Here’s what
you can do there:
-
Define custom confirmation control keys
-
Assign different confirmation categories (like order acknowledgment,
shipping notification)
-
Set relevance to GR or planning
Assigning It to a Vendor:
Once created, assign it in vendor master:
-
TCode: MK01 / MK02 -> Purchasing View
-
From there, it auto-populates into the PO when you create
it.
Do You Always Need to Fill This?
Short answer: No. But…
In Normal POs:
It’s common to use confirmation control keys when:
-
The material is critical or expensive
-
Lead times are long
-
You're working with EDI/IDoc-based processes
If you don’t use it, the PO can still go through, but you’ll
lose the system-enforced visibility. GR will be based on faith rather than
confirmed shipping data.
In STOs (Stock Transport Orders):
Usually not used, but:
-
If filled, inbound delivery becomes mandatory
-
Without it, GR can be done manually
-
With it, VL31N (Inbound Delivery) must be used or configured
IDoc will automate it
So if you're just moving stock between plants, it's overkill
unless you need tight shipping control.
What Happens If You Try to Change It Later?
Here’s a common pain point:
You realize later you need to change the confirmation
control key in ME23N, but there's already a partial GR. SAP
says nope — once a GR exists, the confirmation key becomes locked.
Your Options?
-
Reverse the GR, change the confirmation key, then post the
GR again.
-
Short-close the existing line, and create a new line item
with the updated confirmation key.
SAP protects data integrity by freezing the key once logistics
movements are recorded.
EDI & IDoc Integration
When integrated with EDI (Electronic Data Interchange):
-
Vendors can send confirmation data automatically
-
System creates inbound deliveries or shipping notifications
-
Whole process becomes hands-free and audit-ready
This is a best practice for large-scale, recurring procurement
processes.
Summary: When to Use Confirmation Control Keys
Situation |
Use Confirmation Control? |
Why? |
Critical or long-lead materials |
Yes |
Ensures accurate delivery planning |
Internal stock transfers (STOs) |
Usually No |
Manual GR is faster unless inbound delivery is used |
EDI/automated vendor communications |
Yes |
Enables auto-updates and tight control |
Routine office supplies |
No |
Too much overhead for low-value items |
Pro Tips
-
Always test your confirmation control in sandbox before rolling
out
-
Use custom confirmation keys for specific vendors or material
types
-
Train your GR and planning teams on how MIGO behaves when
confirmations are active
-
Document every inbound delivery step to avoid GR posting
issues
Final Thoughts
The Confirmation Control Key isn’t just an SAP checkbox
— it’s a visibility lever. When used strategically, it improves planning,
reduces surprises, and enhances vendor accountability. Think of it as your
way to say: "If it’s not confirmed, it’s not received."
Get help for your SAP MM problems
SAP MM Forums
- Do you have a SAP MM Question?
SAP MM Books
SAP Material
Management Certification, Interview and Configuration Reference Books
SAP Material 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.
|