Procurement and End-to-End Procure-to-Pay
MM / P2Pbeginner

MM Procure to Pay Part 1: The P2P Process End to End

Key takeaway

The complete procure-to-pay cycle in SAP: requirement, purchase requisition, sourcing, purchase order, goods receipt, invoice verification and payment — the documents created, the postings made and how purchasing, inventory and finance connect.

What this complete series covers

Learn Procurement and End-to-End Procure-to-Pay 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 Procurement and End-to-End Procure-to-Pay.
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 Procurement and End-to-End Procure-to-Pay clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: MM Procure to Pay Part 1: The P2P Process End to End

    Understand the full procure-to-pay document chain from demand through purchasing commitment, goods or service receipt, invoice verification and FI payment.

  2. Part 2: MM Procure to Pay Part 2: Document Flow and Control Points

    Understand P2P as one controlled chain from demand and source selection through PO, receipt, invoice and payment, with each document changing commitments, stock and accounting.

  3. Part 3: MM Procure to Pay Part 3: Integration and Production Troubleshooting

    Troubleshoot procure-to-pay by locating the first incorrect status in the PR-PO-GR-invoice-accounting chain and separating sourcing, logistics, valuation, invoice and workflow causes.

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
✅ P2P: requirement → PR → (RFQ/sourcing) → PO → GR → invoice → payment.

✅ GR (MIGO 101) posts stock (or consumption) against the GR/IR clearing account.

✅ Invoice (MIRO) clears GR/IR and creates the supplier liability; payment (F110) clears the supplier.

✅ Purchase order history links all follow-on documents.

⚠️ Most P2P issues surface at invoice time (price/quantity variances) but start at PO or GR.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: P2P end to end

Part 2: Document flow and control points

Part 3: Integration and production troubleshooting

Detailed tracks: PR, Source Determination, PO, GR/GI, Invoice Verification, Account Determination.

━━━━━━━━━━━━━━━━━━━━
▶ 1. REQUIREMENT AND PR

  • Manual, MRP or other applications; approval.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SOURCING AND PO

  • Source determination, RFQ; PO sent to supplier.

━━━━━━━━━━━━━━━━━━━━
▶ 3. GOODS RECEIPT

  • MIGO 101: stock up, Dr stock/consumption, Cr GR/IR.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INVOICE VERIFICATION

  • MIRO: Dr GR/IR, Cr supplier; variances checked.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PAYMENT

  • Payment run F110 clears open items.

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

  1. Create PR → PO → GR → invoice → payment for one material.
  2. Check PO history and accounting documents.

✅ CHECKPOINT: GR/IR is zero for the item after invoice, and the supplier item is cleared after payment.

Code example

ABAP Code
===== STEP 1: documents =====ME51N PR → ME21N PO → MIGO GR (101) → MIRO invoice → F110 payment ===== STEP 2: postings =====GR: Dr inventory (BSX) 1,000 | Cr GR/IR (WRX) 1,000IR: Dr GR/IR 1,000 | Dr input tax | Cr supplier 1,000 + taxPayment: Dr supplier | Cr bank ===== STEP 3: tracking =====ME23N PO history: GR and IR documents | FBL1N supplier open items

Real project scenario

A buyer saw a PO as complete, but finance had an open GR/IR balance because the invoice quantity was lower than the GR quantity. Reviewing PO history with finance and clearing the difference with a follow-on invoice (or GR/IR clearing) explained the gap; the team added a monthly GR/IR review.

Common mistakes

  • Ignoring PO history.
  • Invoices without PO reference.
  • No GR for goods.
  • Unmonitored GR/IR balances.
  • Treating P2P steps as separate departments.

Best practices

  • Use PO history for status.
  • Enforce PO-based invoicing.
  • Post GRs promptly.
  • Review GR/IR monthly.
  • Align purchasing, warehouse and AP.

Interview angle

Questions: "Explain P2P", "What happens at GR and IR?", "What is the GR/IR account?"
Strong answer: document sequence, postings at GR/IR/payment, GR/IR clearing role, PO history, integration.

Practice this lesson

Quick check

1. Where can a buyer see all GRs and invoices for a PO item?

2. Which account does a goods receipt for a stock material credit?

3. What is the correct document sequence in a standard P2P cycle?

Interview questions

1. A buyer considers a PO complete, but finance shows an open GR/IR balance. How do you explain and resolve it?

Answer it in your own words first, then compare.

2. What are the key operational procurement Fiori apps available to a purchaser in S/4HANA, and how do they differ from the classic SAP GUI transactions they replace?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics