FICO FI Integration Part 3: MM-FI Account Determination in Depth
Configure and troubleshoot MM-FI integration: valuation grouping codes, valuation classes and account category references, OBYC transaction keys and account modifiers, movement type links, and the GR/IR and price difference postings behind procure-to-pay.
Explanation
📌 KEY POINTS
✅ Valuation grouping codes (OMWD) let plants share or separate MM account determination.
✅ Valuation classes (OMSK) link material types to accounts.
✅ OBYC keys: BSX stock, WRX GR/IR, GBB offsetting (with modifiers), PRD price differences.
✅ Movement types decide which keys and modifiers are used.
⚠️ A missing OBYC entry stops goods movements; a wrong one posts silently to the wrong account.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 covered all modules. Now MM in depth. (See also the MM Automatic Account Determination topic.)
━━━━━━━━━━━━━━━━━━━━
▶ 1. BUILDING BLOCKS
- Chart of accounts, grouping code, valuation class.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. KEYS\n• BSX, WRX, GBB, PRD and others.
━━━━━━━━━━━━━━━━━━━━
▶ 3. MODIFIERS
- GBB-VBR consumption, VNG scrapping, INV inventory differences.
━━━━━━━━━━━━━━━━━━━━
▶ 4. P2P POSTINGS
- GR, invoice, differences.
━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING
- Error message analysis; simulation.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Review OMWD and OMSK.
- Display OBYC for BSX and GBB.
- Post GR and GI; verify accounts.
✅ CHECKPOINT: accounts match the matrix.
Code example
===== CONFIG =====OMWD valuation grouping | OMSK valuation classes | OBYC transaction keys | OMJJ movement type account grouping ===== P2P POSTINGS =====GR 101 (standard price 10, PO 11, qty 100): Dr BSX 1,000 | Dr PRD 100 | Cr WRX 1,100Invoice: Dr WRX 1,100 | Cr Supplier 1,100Real project scenario
A new plant's goods receipts failed with an account determination error. Its valuation grouping code had no OBYC entries. Assigning the existing grouping code (shared accounts) solved it on day one.
Common mistakes
- New grouping codes without entries.
- Ignoring modifiers.
- Unsimulated postings.
- Changing classes with stock.
- No finance review.
Best practices
- Share grouping codes deliberately.
- Complete modifiers.
- Simulate.
- Control class changes.
- Review with finance.
Interview angle
Questions: "Explain OBYC keys", "What is a valuation grouping code?", "How do price differences post?"
Strong answer: building blocks, keys and modifiers, movement types, P2P postings, troubleshooting.
Practice this lesson
Quick check
1. Which OBYC transaction key represents the GR/IR clearing account?
2. In automatic account determination for goods movements, which object works together with the valuation class to determine the specific G/L account posted?
3. During a standard three-way match process (purchase order, goods receipt, invoice receipt), which account is used as an interim liability account that is cleared once the vendor invoice is posted?
Interview questions
1. A new plant's goods receipts fail and price differences post to the wrong account. How do you configure and troubleshoot MM-FI account determination?
Answer it in your own words first, then compare.
2. A production issue is reported in FI Integration. What would you check first, and how would you troubleshoot it systematically?
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
- FICO FI Integration Part 1: Why Every Module Ends in Finance
- FICO FI Integration Part 2: Automatic Account Determination and the Integrated Posting Flow
- FICO FI Integration Part 4: Integration Strategy Across Modules and Deployment Models
- FICO FI Integration Part 5: FI-SD Revenue Account Determination and Posting Errors