SAP TCodes · LessonBy Arjun, SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels
ME23N
ME23N is the SAP transaction code for Display Purchase Order (MM). It displays a purchase order read-only, for reviewing details, status, history and related documents without risk of changing anything.
Quick answer
ME23N displays a purchase order read-only, for reviewing details, status, history and related documents without risk of changing anything.
Key takeaways
- Item and header data (read-only).
- Status tab (GR/IR, release, delivery).
- Document flow / related documents (GR, invoices).
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It displays a purchase order read-only, for reviewing details, status, history and related documents without risk of changing anything.
Key fields and screen
- PO number.
- Item and header data (read-only).
- Status tab (GR/IR, release, delivery).
- Document flow / related documents (GR, invoices).
Tips
- Use it to investigate a PO safely (no accidental changes).
- Check the status and history to answer "what happened".
- From here, drill into goods receipts and invoices.
Common errors
- (Display only, so no posting errors.)
- "PO does not exist", wrong number/plant.
- Missing authorization to display the PO.
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 of these does this lesson focus on?
Frequently asked questions
What does ME23N stand for in SAP?
ME23N is the SAP transaction code for Display Purchase Order (MM). It displays a purchase order read-only, for reviewing details, status, history and related documents without risk of changing anything.
What is another point to note about ME23N?
Item and header data (read-only). Status tab (GR/IR, release, delivery). Document flow / related documents (GR, invoices).
What else is worth knowing about ME23N?
Use it to investigate a PO safely (no accidental changes). Check the status and history to answer "what happened". From here, drill into goods receipts and invoices.
What tends to go wrong with ME23N?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.