ME2J — Purchase Orders for Project
ME2J is used to list purchasing documents assigned to projects or WBS elements. It is most useful when Project System and procurement teams need to trace project commitments, deliveries and invoice progress from purchasing documents. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for ME2J — Purchase Orders for Project. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 575 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
list purchasing documents assigned to projects or WBS elements. Treat ME2J as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
ME2J is typically used when Project System and procurement teams need to trace project commitments, deliveries and invoice progress from purchasing documents. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Select the project or WBS scope.
- Restrict organizational/date criteria.
- Review account-assigned PO items and status.
- Drill to ME23N and PO history.
- Reconcile procurement commitments with PS cost/commitment reports.
Key data objects
These are the fields and business objects that most often explain the result in ME2J. Record them in support evidence so the next person can reproduce the same outcome.
- project/WBS — verify the exact value, validity/date context and relationship to the source document.
- purchase order/item — verify the exact value, validity/date context and relationship to the source document.
- account assignment — verify the exact value, validity/date context and relationship to the source document.
- plant/vendor — verify the exact value, validity/date context and relationship to the source document.
- delivery/invoice status — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the ME2J document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
ME2J remains a practical integration point between MM Purchasing and Project System in S/4HANA. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Assuming every project cost starts from a PO. Reconcile the exact business document and date before applying a workaround.
- Ignoring split/multiple account assignments. Reconcile the exact business document and date before applying a workaround.
- Comparing project reports and ME2J with different date/status logic. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the MM/P2P team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me2jERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.