SAP MM Order Creation: ME21N Step by Step and the Procure-to-Pay Process
sap mm order creation
Also searched as
- sap mm for procurement process
- how to create purchase order in sap me21n
- sap procure to pay process steps
- sap me21n step by step
Short answer
To create a purchase order in SAP MM, open ME21N, enter the vendor and organizational data in the header, add items with material, quantity, plant and price, then save. The PO sits inside the procure-to-pay flow: purchase requisition (ME51N), PO (ME21N), goods receipt (MIGO), invoice verification (MIRO) and payment (F110).
Applies to: SAP ECC 6.0 and S/4HANA on-premise. S/4HANA also offers Fiori apps for the same steps; the data model is the same.
How to create a purchase order in ME21N
- 1Open ME21N (Logistics > Materials Management > Purchasing > Purchase Order > Create > Vendor/Supplying Plant Known).
- 2Select the order type, normally Standard PO (NB), and enter the vendor number.
- 3In the Org. Data tab of the header, enter purchasing organization, purchasing group and company code.
- 4In the item overview, enter the material (or short text), quantity, plant and, if needed, storage location and delivery date.
- 5Enter or confirm the net price. If an info record or contract exists, the price is proposed automatically.
- 6For account-assigned items (K for cost center), set the account assignment category and fill the cost center and G/L account.
- 7Check for errors with the Check button, review the Conditions tab for freight and discounts, and fix any red messages.
- 8Save. The PO number is issued, and output (print, EDI or email) is triggered per output determination, which you can view in ME9F.
The full procure-to-pay chain
Procure-to-pay starts with a need, entered manually as a purchase requisition (ME51N) or generated by MRP. A buyer may request quotes (ME41), then converts the requisition into a PO (ME21N, or ME58 and ME59N for automatic conversion). The vendor delivers; the warehouse posts a goods receipt in MIGO using movement type 101, which creates the material document and updates stock.
The invoice arrives and is posted in MIRO with reference to the PO. The system performs a three-way match of PO, goods receipt and invoice, and blocks the invoice if price or quantity differs beyond tolerance. Payment follows through the automatic payment program (F110) in Finance.
Where the data lives
The PO header is in EKKO and the items in EKPO, with schedule lines in EKET and account assignment in EKKN. PO history, meaning goods receipts and invoices posted against the item, is in EKBE. Purchase requisitions are in EBAN.
Knowing these tables helps with reports and integrations, but for changes always use the transaction or the BAPI (BAPI_PO_CREATE1), not direct table updates.
ME51N Create purchase requisition
ME41 Request for quotation
ME21N Create purchase order
ME22N Change PO
ME23N Display PO
MIGO Goods receipt (movement type 101)
MIRO Enter incoming invoice
F110 Automatic payment program
Tables: EBAN, EKKO, EKPO, EKET, EKKN, EKBE
Controls that affect PO creation
A release strategy can block a PO until approvers release it (ME28 or ME29N); an unreleased PO cannot be received. Source lists and info records control price and vendor defaults, and tolerance limits control how far invoices may deviate from the PO.
Most PO issues are one of three: a missing master data field (for example a material not extended to the plant), a missing authorization, or a release strategy that was not expected. The message in the status bar usually names the field.
Try it here, free
SAP MIGO Goods Receipt Checklist
Step by step checklist to post a clean goods receipt against a purchase order in MIGO, with critical checks flagged.
Common pitfalls
- !Creating a PO for a material that is not extended to the plant, which gives a plant error on save.
- !Overriding the info record price by hand and breaking the audit trail.
- !Ignoring the release strategy and expecting immediate goods receipt.
- !Posting an invoice before the goods receipt, causing blocked invoices.
- !Updating EKKO or EKPO directly instead of using the transaction or BAPI.
How an ERP-grounded AI assistant handles this
Buyers ask routine PO questions all day: where is this PO, what is received, why is the invoice blocked. A grounded assistant answers from EKKO, EKPO and EKBE under the buyer's own authorizations and can draft a PO for the buyer to review, never posting without approval. Netray's layer is read-only by default and can run on-prem.
Frequently asked questions
What is the T-code to create a purchase order in SAP?
ME21N creates a purchase order. ME22N changes it and ME23N displays it. The older ME21 and related transactions exist but ME21N is the standard in ECC and S/4HANA.
What are the steps in the SAP procure-to-pay process?
Purchase requisition, optional request for quotation, purchase order, goods receipt, invoice verification and payment. In transactions: ME51N, ME41, ME21N, MIGO, MIRO and F110.
Which tables store purchase order data?
EKKO holds PO headers, EKPO the items, EKET the schedule lines, EKKN account assignment and EKBE the PO history of receipts and invoices. Requisitions are in EBAN.
Why can I not save my purchase order?
Read the message in the status bar. Typical causes are a missing mandatory field, a material not maintained for the plant, a missing account assignment or authorization, or a pricing condition that cannot be determined. Fix the field named in the message.
Related
SAP MM Contract T-Codes: ME31K, ME32K, ME33K and Release Orders
In SAP MM a contract is an outline agreement with a vendor. ME31K creates it, ME32K changes it, ME33K displays it. A quantity contract (document type MK) caps total quantity, a value contract (WK) caps total value, and purchase orders created in ME21N reference the contract as release orders against it.
How-toSAP ME21N: why the release strategy is not determined on a purchase order
When a purchase order saves without a release strategy, no strategy in the release group matched the PO's characteristic values. Compare the PO header values (value, document type, purchasing group, plant) against the value ranges in the strategy classification (CL24N), and check that the release group and code are active for the PO document type.
Error fixPO Not Released in SAP: Release Strategy, ME28 and ME29N Fixes
A purchase order that stays unreleased almost always has a release strategy that is assigned but cannot advance: the release code is not given to the approver, the prior release step is still open, the approver or workflow agent does not exist, or a change reset the strategy. Check the Release Strategy tab in ME23N, then fix the code assignment, the workflow, or the value that triggered the strategy.
How-toSAP MM BAPI for PO Create and Change: BAPI_PO_CREATE1 and BAPI_PO_CHANGE
Use BAPI_PO_CREATE1 to create a purchase order and BAPI_PO_CHANGE to change one. Each takes a data structure and a matching X-structure that flags which fields to apply, returns messages in the RETURN table, and only persists after you call BAPI_TRANSACTION_COMMIT when no error message came back.
How-toSAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables
Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP MIGO Goods Receipt ChecklistStep by step checklist to post a clean goods receipt against a purchase order in MIGO, with critical checks flagged.
- SAP QM in Procurement Setup ChecklistCheck each step needed to run goods receipt inspection for purchased materials, from QM control key to vendor release.
- SAP MM Transaction Codes ReferenceSearchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
ERP fixes and how-tos
- How to Create a Purchase Order in SAP MM (ME21N)Step-by-step purchase order creation in SAP MM with ME21N: manual PO, PO from requisition, account assignment, release and the order-to-invoice flow.
- SAP MM Errors and Solutions: The Common Ones, by Process StepCommon SAP MM errors by process step, with cause and fix: stock deficit, closed periods, release strategy, blocked invoices and account determination.
- SAP MM Return to Vendor Process: Return PO, MIGO 161 and Credit MemoReturn goods to a vendor in SAP MM: return PO, MIGO movement 161 or 122, credit memo in MIRO, and how to handle scrap, rework and replacement shipments.