MM / P2Pbeginner

MM Purchase Order Part 1: Purchase Order Anatomy — Header, Item, Schedule Lines and Account Assignment

Key takeaway

The purchase order is the legal request to a supplier. Learn its structure — header (supplier, purchasing org, currency, payment terms), items (material, quantity, price, plant), schedule lines (delivery dates), account assignment — document types, and how to create POs manually or from requisitions.

What this complete series covers

Learn Purchase Order in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Purchase Order.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Purchase Order clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: MM Purchase Order Part 1: Purchase Order Anatomy — Header, Item, Schedule Lines and Account Assignment
Read a purchase order structurally: header controls supplier and purchasing context, items define what/how procurement occurs, schedule lines define when/how much is expected, and
Part 2: MM Purchase Order Part 2: PO Pricing — Conditions, Info Records and Calculation Schema
Understand where PO pricing originates, how purchasing conditions and info records influence proposed values, and why a final PO price must be traced through source, validity, scal
Part 3: MM Purchase Order Part 3: Item Categories — Standard, Consignment, Subcontracting, Third-Party, Service and Limit
Use PO item categories to model different procurement processes, including standard purchase, subcontracting, supplier consignment, and limit procurement, each with distinct materi
Part 4: MM Purchase Order Part 4: Follow-On Processing — Confirmations, Goods Receipt and Invoice Receipt
Trace a PO through supplier confirmation, goods receipt, invoice receipt and document history so quantity, delivery and financial status can be reconciled across the end-to-end procure-to-pay process.
Part 5: MM Purchase Order Part 5: Approval, Output, Change Control and Troubleshooting
Operate a PO after creation by controlling approval, change-triggered reapproval, supplier output, version/change evidence, and support diagnostics across purchasing and workflow layers.

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ Header: supplier, document type, purchasing org/group, company code, currency, payment terms, incoterms.
✅ Items: material or text, quantity, price, plant, storage location, item category, account assignment.
✅ Schedule lines split an item into delivery dates and quantities.
✅ Document type (e.g. NB standard, UB stock transport) controls number range, item categories and field selection.
⚠️ A PO without correct plant, account assignment or price creates problems at GR and invoice.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: PO anatomy
Part 2: PO pricing
Part 3: PO item categories
Part 4: Follow-on processing: confirmations, GR, IR
Part 5: Approval, output, change control and troubleshooting

━━━━━━━━━━━━━━━━━━━━
▶ 1. HEADER

Supplier, purchasing org, group, company code, currency, payment terms, incoterms, partners.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ITEMS

Material, quantity, order unit, net price, plant, sloc, material group.
Item category and account assignment category.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SCHEDULE LINES

Delivery dates and quantities; statistical dates.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DOCUMENT TYPES

NB standard, UB stock transport, FO framework (per config).

━━━━━━━━━━━━━━━━━━━━
▶ 5. CREATION

ME21N manual, with reference to PR/RFQ/contract; ME59N automatic; Fiori apps.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a PO for a stock material.
Add a consumable item with cost center.
Split an item into two schedule lines.

✅ CHECKPOINT: the PO shows correct defaults from supplier, info record and material.

Code example

ABAP Code

===== STEP 1: create =====ME21N: type NB, supplier 300100, POrg 1000, group 001, CC 1000Item 10: R-100, 1,000 KG, 12.00 EUR/KG, plant 1000, sloc 0001Item 20: text "Safety gloves", 50 PC, account assignment K cost center 4100, material group 02 ===== STEP 2: schedule lines =====Item 10: 500 KG on 10.10, 500 KG on 24.10 ===== STEP 3: display =====ME23N: header tabs, item details, PO history

Real project scenario

A company let buyers create POs with free-text items for regular materials. GRs couldn't update stock, prices varied wildly and spend reports were unusable. Enforcing material masters for regular buys and catalogs for indirect items fixed data quality.

Common mistakes

Free text instead of materials.
Wrong plant or storage location.
Missing account assignment for consumables.
Unrealistic delivery dates.
Wrong document type.

Best practices

Create POs from PRs/contracts.
Use materials and catalogs.
Default data from master data.
Keep schedule lines realistic.
Review PO history.

Interview angle

Questions: "What is the structure of a PO?", "What does the document type control?", "What are schedule lines?"
Strong answer: header/items/schedule lines, account assignment, document types, creation methods, defaults from master data.

Practice this lesson

Quick check

1. Which PO level holds delivery dates and quantities for partial deliveries?

2. A team proposes using free-text PO items for all regular materials to save time. What is the main problem?

3. What does the PO document type control?

Interview questions

1. Walk through the end-to-end process and document type considerations for handling a vendor return that requires both a returns purchase order and financial reversal of an already-settled invoice.

Answer it in your own words first, then compare.

2. What document type considerations apply when creating a returns purchase order for a vendor return in SAP MM, and how does this differ from a standard purchase order document type?