ME5A — Purchase Requisition List
ME5A is used to list and analyze purchase requisitions by material, plant, requester, release status and processing state. It is most useful when buyers need a worklist of open requisitions or support must prove why a requirement has not become a purchase order. 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 ME5A — Purchase Requisition List — 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· 599 words
Esta página aún no está disponible en español.
Purpose
list and analyze purchase requisitions by material, plant, requester, release status and processing state. The key is to treat ME5A 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
ME5A is typically used when buyers need a worklist of open requisitions or support must prove why a requirement has not become a purchase order. 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 by plant, purchasing group and date before widening the list.
- Add release and processing-status fields to the layout.
- Drill into ME53N/ME52N for a specific requisition.
- Check source assignment and follow-on PO number for stuck items.
- Reconcile list selections with any automated ME59N conversion process.
Key data objects
These fields and business objects usually explain the result in ME5A. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- requisition/item — verify the exact value, status, organizational context and date relevance.
- plant — verify the exact value, status, organizational context and date relevance.
- processing/release status — verify the exact value, status, organizational context and date relevance.
- source assignment — verify the exact value, status, organizational context and date relevance.
- PO conversion status — 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
ME5A remains a useful buyer/support worklist on S/4HANA, even where Fiori apps provide role-based requisition monitoring. 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
- Assuming a missing item was deleted when the selection simply excludes its status. Check the complete document flow before applying a workaround.
- Reading an already-converted requisition as still open because follow-on fields are hidden. Check the complete document flow before applying a workaround.
- Ignoring release status when troubleshooting automatic PO creation. 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/me5aERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.