MM: procurement, GR/IR and inventory — Concepts and mental models
Full lesson currently free to read · AI practice limits apply separately
Training simulation: All sample identifiers, logs, requests, transactions, values and cases are fictional. Tools and permissions vary by SAP release; perform any changes only in approved DEV/QA environments. MM: procurement, GR/IR and inventory — Concepts and mental models Outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
Visual overview
What this complete series covers
Three-part SAP Debugging learning journey: understand concepts, follow the guided investigation, resolve a realistic case.
- Who it is for
- Technical developers, functional consultants, support analysts and solution architects.
- Prerequisites
- Use only synthetic data and approved non-production systems. Some tools are not available in SAP public cloud.
- Final outcome
- Purchase order approval, GR posting or invoice matching fails. Learning outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
- Part 1: MM: procurement, GR/IR and inventory — Concepts and mental models
Purchase order approval, GR posting or invoice matching fails. Learning outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
- Part 2: MM: procurement, GR/IR and inventory — Guided debugger and evidence walkthrough
Purchase order approval, GR posting or invoice matching fails. Learning outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
- Part 3: MM: procurement, GR/IR and inventory — Root-cause case, remediation and assessment
Purchase order approval, GR posting or invoice matching fails. Learning outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
System and release assumptions: SAP edition, Basis release, available transactions and authorization vary by system.
Explanation
Training simulation: All sample identifiers, logs, requests, transactions, values and cases are fictional. Tools and permissions vary by SAP release; perform any changes only in approved DEV/QA environments.
MM: procurement, GR/IR and inventory — Concepts and mental models
Outcome: Follow PO, goods movement and invoice evidence before blaming enhancements.
Environment: MM/Inventory/Invoice Verification in ECC and S/4HANA with MATDOC-led reporting; public cloud uses corresponding apps.
Mental models
1. Understand the boundary
Purchase requisition, PO, goods receipt, invoice verification and FI clearing form one evidence chain. One document may be valid while a downstream step remains pending because of tolerance, status, valuation, master data or approval. Start with PO History and actual material/invoice documents.
2. How this investigation works
GR/IR open items often represent time or quantity/price differences, not faulty postings. A received quantity of 10 and an invoiced quantity of 8 normally creates an open quantity; first reconcile source units, reversals and valuation before correcting anything.
3. Evidence-based decisions
Workflow agent determination, goods movement and invoice blocking follow separate rules. Check movement type, valuation class/OBYC, posting periods, tax, tolerance keys and authorization before asking technical developers to debug a user exit.
Three common false diagnoses
- An open GR/IR item can be an expected business timing mismatch.
- A MIRO tolerance block isn't the same as a missing PO approval.
- S/4HANA's MATDOC-based inventory data model changes how diagnostic queries should be designed.
Synthetic evidence
PO DEMO-MM-204: 10 EA at 100 EUR; GR 10 EA postedInvoice IR DEMO-204: 8 EA at 100 EURGR/IR quantity open = 2 EA | amount example 200 EURMIGO material doc and MIRO invoice both existNo failed posting dump in this sampleDiagnostic flow
- Compare document history and master data
- Inspect account determination, periods, tolerances and approvals
- Reproduce with matching valuation and tax conditions
Tools
ME23N · MIGO · MIRO · MB51 · Account determination · Workflow log
Check your understanding
Question: A PO shows GR 10 units, IR 8 units and a remaining GR/IR balance. What does the evidence suggest?
A. The difference may be legitimate pending invoice quantity; reconcile source documents.
B. The database must be corrupted.
C. Post a dummy invoice in production to zero the balance.
Correct: A. Document quantity difference explains the open item until other evidence proves an error.
Safety: GR/IR clearing, invoice reposting or stock movements are financial actions requiring business authorization, not debugging shortcuts.
Real project scenario
Synthetic case: Purchase order approval, GR posting or invoice matching fails.
The sample deliberately has an invoiced quantity lower than the received quantity. The residual GR/IR amount is a traceable business timing difference, not an ABAP or FI ledger defect.
Common mistakes
- An open GR/IR item can be an expected business timing mismatch.
- A MIRO tolerance block isn't the same as a missing PO approval.
- S/4HANA's MATDOC-based inventory data model changes how diagnostic queries should be designed.
Best practices
Confirm with procurement and AP whether the missing quantity will be invoiced, credited or returned. Complete the approved process and reconcile resulting FI balances; do not force clearing to make a dashboard green.
- Positive: Matched GR/IR quantities reconcile to expected open items under the business process.
- Negative: Price/quantity/tax mismatch cases receive their designated tolerance handling.
- Cross-process: Duplicate invoice reference is detected or reviewed before any repeat posting.
GR/IR clearing, invoice reposting or stock movements are financial actions requiring business authorization, not debugging shortcuts.
Interview angle
Procure-to-pay debugging: purchase order history, account determination for goods receipt (OBYC transaction keys), invoice verification blocks and tolerances, GR/IR balances and their clearing, and source determination issues.
Practice this lesson
Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.
Quick check
0 of 4 questions attempted
1. A PO shows GR 10 units, IR 8 units and a remaining GR/IR balance. What does the evidence suggest?
2. A goods receipt posts to the wrong G/L account. Which area do you analyse?
3. An invoice is blocked for payment due to a price difference. What is the cause?
4. Where can you see goods receipts and invoices posted for a PO item?
Interview questions
1. How do you investigate a GR/IR account balance that doesn't clear?
Answer it in your own words first, then compare.
2. A purchase requisition doesn't convert to a PO automatically. What do you check?
Answer it in your own words first, then compare.
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.