ME2K — Purchase Orders by Account Assignment
ME2K is used to list purchasing documents by account-assignment objects and related selection criteria. It is most useful when controlling or procurement needs POs tied to cost centers, orders, WBS elements, assets or other account assignments. 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 ME2K — Purchase Orders by Account Assignment. 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· 583 words
Esta página aún no está disponible en español.
Purpose
list purchasing documents by account-assignment objects and related selection criteria. Treat ME2K 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
ME2K is typically used when controlling or procurement needs POs tied to cost centers, orders, WBS elements, assets or other account assignments. 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 account-assignment scope and organization.
- Restrict document date/status as needed.
- Add account assignment and open quantity/value fields to the layout.
- Drill to ME23N for document history.
- Reconcile commitments or actual follow-on postings where required.
Key data objects
These are the fields and business objects that most often explain the result in ME2K. Record them in support evidence so the next person can reproduce the same outcome.
- account assignment category — verify the exact value, validity/date context and relationship to the source document.
- cost object — verify the exact value, validity/date context and relationship to the source document.
- purchasing document — verify the exact value, validity/date context and relationship to the source document.
- plant/purchasing organization — verify the exact value, validity/date context and relationship to the source document.
- open/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 ME2K 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
ME2K remains a common SAP purchasing list transaction for account-assigned purchase orders. 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
- Using the wrong scope-of-list and comparing inconsistent extracts. Reconcile the exact business document and date before applying a workaround.
- Assuming PO commitment equals actual cost. Reconcile the exact business document and date before applying a workaround.
- Ignoring split account assignments. 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/me2kERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.