ME21N — Create a purchase order
ME21N creates a purchase order: the formal commitment to a supplier for materials or services at agreed prices and dates. Header data covers supplier, purchasing organisation, group and terms, while each item carries material, quantity, delivery date, plant and account assignment. Saving the order makes it available for goods receipt and invoice verification.
Purchase order creation: the header and item data that matter, how account assignment works, and the errors that block a save.
Reviewed by an ERPClimb SAP consultant on 13 Sept 2026· 611 words
What ME21N is for
ME21N is where procurement intent becomes a legal and financial commitment. The purchase order names the supplier, the purchasing organisation buying on behalf of the company, the material or service being bought, the quantity, the price and the delivery date. It is also the document the rest of procure-to-pay is measured against: goods receipt records what actually arrived against these quantities, and invoice verification compares what the supplier billed against these prices. Because of that, data quality entered here determines how much three-way matching work the finance team faces later.
When it is used in procure-to-pay
The order is created after a requirement exists and a source has been decided, whether that requirement came from a purchase requisition, from planning, or directly from a buyer. Buyers use it for one-off and negotiated purchases, and consultants use it constantly in testing because almost every procure-to-pay scenario, stock or consumable, domestic or import, service or material, starts with an order created here. Where a requisition and a release strategy exist, the order is converted rather than typed, and understanding which path an organisation uses matters more than the screen itself.
How it is used in practice
You choose the document type, enter the supplier and the purchasing organisation, purchasing group and company code, then add items with material or short text, quantity, unit, delivery date, plant and net price. Item detail carries the account assignment, delivery schedule, conditions, texts and any confirmation or invoicing control. For a consumable or a service, the account assignment category decides which cost object must be supplied, so a cost centre, order or project is mandatory there while a stock item posts to inventory instead. Check the document overview and any messages before saving, since the save creates the commitment. On S/4HANA the classic transaction remains available alongside Fiori procurement apps that create the same document.
Fields and objects that matter
- Document type, which controls number range, field selection and the item categories allowed
- Supplier, purchasing organisation, purchasing group and company code, which set responsibility and terms
- Material or short text with quantity, unit and net price, the commercial content of each item
- Delivery date and plant, which drive expected receipts, planning and where the goods are received
- Account assignment category with its cost object, for consumable and service items
- Purchase order header EKKO and items EKPO, and the account assignment stored per item
Common pitfalls and how they show up
- Missing or incomplete supplier or material master data for the relevant organisational level, which blocks the item rather than the header
- Choosing an account assignment that requires a cost object nobody supplied, producing an error users read as a permissions problem
- A price that contradicts an existing agreement, so invoice verification later reports a price variance
- Unrealistic delivery dates entered to satisfy a required field, which then distort planning and receipt reporting
- Wrong tax code, which surfaces only when the supplier invoice is posted
- Creating a fresh order when a requisition already exists, breaking the audit trail and the release strategy
- Ignoring the release strategy, then reporting that the supplier never received an order that was never released
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.