ME51N — Create Purchase Requisition
ME51N is used to create purchase requisitions for materials, services or consumables with quantity, delivery date and account assignment. It is most useful when a business requirement must enter the procurement pipeline before source determination and purchase-order creation. 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 ME51N — Create Purchase Requisition — 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
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
create purchase requisitions for materials, services or consumables with quantity, delivery date and account assignment. The key is to treat ME51N 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
ME51N is typically used when a business requirement must enter the procurement pipeline before source determination and purchase-order creation. 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
- Choose the requisition document type and item category appropriate to the requirement.
- Enter material or descriptive item, quantity, plant and realistic delivery date.
- Maintain account assignment for consumable/service purchases.
- Check source-of-supply and valuation information where relevant.
- Save and capture the requisition number for release and conversion.
Key data objects
These fields and business objects usually explain the result in ME51N. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- document type — verify the exact value, status, organizational context and date relevance.
- material/short text — verify the exact value, status, organizational context and date relevance.
- plant — verify the exact value, status, organizational context and date relevance.
- quantity and delivery date — verify the exact value, status, organizational context and date relevance.
- account assignment/source — 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
ME51N remains common in S/4HANA, with Fiori requisition apps offering a newer self-service experience while the same procurement controls apply. 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
- Creating a requisition with unrealistic delivery dates just to satisfy a mandatory field. Check the complete document flow before applying a workaround.
- Using the wrong account assignment and pushing the error into PO/invoice processing. Check the complete document flow before applying a workaround.
- Creating a duplicate requisition when MRP or another request already exists. 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/me51nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.