Procurement and End-to-End Procure-to-Pay

MM / P2Padvanced

MM Procure to Pay Part 3: Integration and Production Troubleshooting

Key takeaway

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.

Explanation

📌 KEY POINTS
✅ Start with PO history and document flow to see where the chain broke.
✅ Classify: purchasing (release, output), inventory (GR errors), finance (account determination, invoice blocks), payment.
✅ Integration issues (EDI, Ariba Network) need message monitoring and partner data checks.
✅ Fix root causes in master data or configuration; avoid manual postings.
⚠️ Manual FI corrections for P2P errors break reconciliation between MM and FI.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered controls. Now troubleshooting.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PURCHASING

PO not released; output not sent; supplier data missing.

━━━━━━━━━━━━━━━━━━━━
▶ 2. GOODS RECEIPT

No open quantity, account assignment errors, period closed, missing storage location.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ACCOUNTING

Account determination errors (OBYC); tax codes.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INVOICE AND PAYMENT

Blocks, variances, duplicate checks, payment blocks, bank data.

━━━━━━━━━━━━━━━━━━━━
▶ 5. INTEGRATION

EDI/IDoc and Ariba Network messages (PO, confirmations, ASN, invoices).

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

Take an incident; check PO history.
Identify the failing step and module.
Check logs/monitors; fix cause; reprocess.

✅ CHECKPOINT: each incident has a documented root cause and prevention.

Code example

ABAP Code

===== STEP 1: analysis path =====ME23N (release, output, history) → MIGO/MB51 (GR) → OBYC / error message (accounts) → MIRO/MRBR (invoice) → F110 log (payment) ===== STEP 2: integration =====WE02 IDocs | Ariba Network / integration monitor | partner profiles ===== STEP 3: typical causes =====PO unreleased | period closed (MMPV) | missing OBYC entry | tolerance block | supplier bank data

Real project scenario

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.

Common mistakes

Starting with FI postings.
Manual corrections.
Ignoring output logs.
Not checking period status.
No runbook.

Best practices

Use PO history first.
Classify by module.
Monitor outputs and interfaces.
Fix at source.
Maintain a runbook.

Interview angle

Questions: "How do you troubleshoot P2P?", "GR fails — what do you check?", "Why are suppliers not receiving POs?"
Strong answer: PO history first, module classification, typical causes per step, integration monitoring, root-cause fixes.

Practice this lesson

Quick check

1. Suppliers say they never receive POs, but POs are released. What should be checked first?

2. A GR fails with an account determination error. Where is the cause typically found?

3. Why should P2P posting errors not be fixed with manual FI journal entries?

Interview questions

1. 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?

Answer it in your own words first, then compare.

2. 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?