Procurement and End-to-End Procure-to-Pay
MM Procure to Pay Part 1: The P2P Process End to End
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.
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.
MM Procure to Pay Part 2: Document Flow and Control Points
Where P2P is controlled: approvals of PRs and POs, confirmations, GR-based invoice verification, three-way match, tolerances and invoice blocks, payment blocks and release, GR/IR maintenance — and what each control prevents.
A supplier invoice was blocked for quantity variance every month because deliveries arrived in partial GRs while invoices covered full orders. Enabling GR-based IV and aligning invoicing to deliveries eliminated most blocks; remaining ones were resolved quickly with MRBR.
MM Procure to Pay Part 3: Integration and Production Troubleshooting
Diagnose P2P incidents across modules: PO not sent, GR not possible, wrong account postings, invoice blocks, GR/IR imbalances, payment issues and integration with suppliers (EDI, Ariba Network) — with a document-flow-first analysis path.
Suppliers reported POs not received while SAP showed them as released. Output logs revealed EDI partner profiles missing for suppliers onboarded after go-live. Adding partner setup to supplier onboarding and a daily output error report ended the complaints.
Interview questions covered
- 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?
- An architect is designing the Fiori app landscape for operational procurement covering purchase requisition creation, PO management, and source determination. What key design considerations differentiate app choices for a transactional buyer role versus a strategic sourcing role?
- A global organization implementing Central Procurement (Hub) wants purchase requisitions from multiple ECC and S/4HANA backend systems to be sourced centrally into a single S/4HANA hub, with resulting POs replicated back and output managed centrally. What are the key architectural and output management considerations?
- In a catalog procurement setup (e.g., SAP Ariba or open catalog interface), how should output management be configured to ensure PO documents are correctly transmitted to catalog-sourced vendors?
- You inherit an existing Procurement and End-to-End Procure-to-Pay implementation covering P2P Integration and Production Troubleshooting. What would you review before changing it, and what would make you confident the change is production-ready?
- A buyer considers a PO complete, but finance shows an open GR/IR balance. How do you explain and resolve it?
- Invoices are frequently blocked and paid late. How do you review P2P control points?