ME2N — Purchase Orders by PO Number
ME2N is used to list purchase orders with flexible selection, status and item information for operational and support analysis. It is most useful when buyers or consultants need a broad PO worklist not limited to one supplier or material. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains ME2N — Purchase Orders by PO Number — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 589 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
list purchase orders with flexible selection, status and item information for operational and support analysis. The key is to treat ME2N as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
ME2N is typically used when buyers or consultants need a broad PO worklist not limited to one supplier or material. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Restrict organizational and date scope first.
- Select the list scope that matches open, delivered or invoiced items.
- Expose PO history/status fields in the layout.
- Drill into ME23N for document details.
- Reconcile open quantities with MIGO/MIRO where status is disputed.
Key data objects
These fields and business objects usually explain the result in ME2N. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- purchase order/item — verify the exact value, status, organizational context and date relevance.
- company/purchasing organization — verify the exact value, status, organizational context and date relevance.
- plant — verify the exact value, status, organizational context and date relevance.
- delivery/invoice status — verify the exact value, status, organizational context and date relevance.
- document date — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
ME2N remains widely used on S/4HANA; Fiori analytical apps complement it but do not remove its value as a flexible SAP GUI worklist. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Comparing two ME2N extracts with different scope-of-list settings. Check the complete document flow before applying a workaround.
- Calling a PO open because delivery-completed/invoice-completed indicators are hidden. Check the complete document flow before applying a workaround.
- Using a huge unrestricted list for reconciliation instead of targeted selection. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me2nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.