SAP TCodes · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
ME22N
ME22N is the SAP transaction code for Change Purchase Order (MM). It changes an existing purchase order, quantities, prices, dates or items, subject to what is allowed given the PO’s processing status.
Quick answer
ME22N changes an existing purchase order, quantities, prices, dates or items, subject to what is allowed given the PO’s processing status.
Key takeaways
- PO number (opens the PO for editing).
- Editable item fields (quantity, price, delivery date).
- Header/item conditions and texts.
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It changes an existing purchase order, quantities, prices, dates or items, subject to what is allowed given the PO’s processing status.
Key fields and screen
- PO number (opens the PO for editing).
- Editable item fields (quantity, price, delivery date).
- Header/item conditions and texts.
- Release status (if a strategy applies).
Tips
- Changes may re-trigger the release strategy (re-approval).
- Some fields lock once goods receipt/invoice exist.
- Use the change documents to see the PO’s history.
Common errors
- Field not changeable after GR/IR activity.
- Change resets release, requiring re-approval.
- Quantity below already-received amount rejected.
Common pitfalls
- Using the wrong variant (e.g. create vs change vs display).
- Missing prerequisite master data or config.
- Not checking the resulting document/postings.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which statement is true of ME22N?
Frequently asked questions
What does ME22N stand for in SAP?
ME22N is the SAP transaction code for Change Purchase Order (MM). It changes an existing purchase order, quantities, prices, dates or items, subject to what is allowed given the PO’s processing status.
What else is worth knowing about ME22N?
PO number (opens the PO for editing). Editable item fields (quantity, price, delivery date). Header/item conditions and texts.
What is the practical takeaway on ME22N?
Changes may re-trigger the release strategy (re-approval). Some fields lock once goods receipt/invoice exist. Use the change documents to see the PO’s history.
What tends to go wrong with ME22N?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.