MM Physical Inventory Part 5: Inventory Differences, Accounting Impact and Audit Controls
Control inventory difference postings: accounting via GBB-INV and difference accounts, tolerance groups limiting what users may post, approval for large differences, reason codes, analysis of recurring differences, and audit evidence for year-end.
Explanation
📌 KEY POINTS
✅ Differences post via 701/702 to stock and inventory difference accounts (GBB-INV in OBYC).
✅ Tolerance groups limit the value per document/item a user may post; larger differences need authorized users.
✅ Reasons and recount evidence document differences.
✅ Recurring differences point to process issues (unrecorded issues, UoM errors, theft) — analyse root causes.
⚠️ Posting many small differences without analysis hides systemic process failures.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered special counts. Now control.
━━━━━━━━━━━━━━━━━━━━
▶ 1. ACCOUNTING
- 701/702: BSX vs GBB-INV; value at material price.
━━━━━━━━━━━━━━━━━━━━
▶ 2. TOLERANCE GROUPS
- Max difference per document and item; assigned to users.
━━━━━━━━━━━━━━━━━━━━
▶ 3. APPROVAL AND EVIDENCE
- Recounts, reasons, supervisor approval, document archive.
━━━━━━━━━━━━━━━━━━━━
▶ 4. ANALYSIS
- Difference reports by material, sloc, reason; trend analysis.
━━━━━━━━━━━━━━━━━━━━
▶ 5. AUDIT
- Year-end evidence, method documentation, segregation of duties (counter ≠ poster).
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Configure tolerance groups and assign users.
- Post a difference above tolerance (blocked) and approve.
- Analyse differences for a quarter.
✅ CHECKPOINT: every large difference has recount evidence and approval.
Code example
===== STEP 1: accounting =====OBYC GBB-INV → inventory difference account 233000 | BSX stock ===== STEP 2: tolerances =====Tolerance group PI01: max 500 per item, 5,000 per document → user assignment ===== STEP 3: analysis =====Difference list by material/reason | recurring losses → check UoM, unposted issues, securityReal project scenario
A warehouse posted hundreds of small inventory differences monthly within tolerance. Analysis showed a pattern for one material: counting in cases while book stock was in pieces. Fixing the UoM on count sheets eliminated 70% of differences.
Common mistakes
- Unlimited posting authority.
- No root cause analysis.
- Counter posting own differences.
- Missing evidence.
- Ignoring small recurring differences.
Best practices
- Use tolerance groups.
- Separate counting and posting.
- Analyse trends.
- Keep evidence.
- Fix process causes.
Interview angle
Questions: "How are inventory differences posted?", "What are tolerance groups for PI?", "How do you control differences?"
Strong answer: 701/702 with GBB-INV, tolerance groups, approvals and evidence, analysis, audit controls.
Practice this lesson
Quick check
1. Which account determination transaction/event key is generally used for automatic G/L postings resulting from physical inventory differences in Inventory Management?
2. Hundreds of small inventory differences are posted each month for one material. What should be done?
3. What is the main purpose of a physical inventory difference list generated prior to posting differences?
Interview questions
1. During period-end close at a plant with Material Ledger active, physical inventory count adjustments are posted before the actual costing run, and the controller asks whether this sequence could distort actual cost calculations for the period. How would you respond and what would you verify?
Answer it in your own words first, then compare.
2. A plant uses split valuation to separate valuation types for a raw material by origin (domestic vs imported). Physical inventory counts are showing systematic differences only for the imported valuation type. What structural and process factors would you investigate?
Answer it in your own words first, then compare.
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
- S/4HANA MM Transformation, Ariba, Migration, Public Cloud and Architecture
- Invoice Verification, GR/IR, Integration and Production Support
- Procurement and End-to-End Procure-to-Pay
- Inventory Management, Valuation, Material Ledger and Account Determination
- MM Foundation, Enterprise Structure and Master Data
- Enterprise Structure