MM / P2Padvanced

MM Account Determination Part 5: Troubleshooting and Production Support

Key takeaway

Resolve account determination incidents: reading the error message (e. g. M8147 account determination not possible), identifying the key and missing combination, checking valuation class and grouping code, simulation, fixing entries safely, and correcting wrong postings.

Explanation

📌 KEY POINTS
✅ Error messages name the chart of accounts, key and combination — read them fully.
✅ Check valuation class of the material, grouping code of the plant, modifier of the movement type.
✅ Fix missing entries via transport with finance approval; don't bypass with manual postings.
✅ Wrong postings are corrected by reversal and reposting after the fix.
⚠️ Emergency changes directly in production without review create more errors.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered architecture. Now production support.

━━━━━━━━━━━━━━━━━━━━
▶ 1. READ THE ERROR

Key, chart of accounts, valuation class, modifier in the message.

━━━━━━━━━━━━━━━━━━━━
▶ 2. IDENTIFY CAUSE

New class, new plant/grouping code, custom movement type.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SIMULATE

MIGO/MIRO simulation; OBYC display.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 4. FIX\n• Correct entry via change process; urgent transport.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CORRECT POSTINGS

Reversal and reposting; check reports.

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

Reproduce the error; capture message details.
Find the missing combination in OBYC.
Fix in dev, test, transport; repost.

✅ CHECKPOINT: incident closed with root cause and prevention.

Code example

ABAP Code

===== STEP 1: error =====M8147: account determination for entry INT BSX 0001 3100 not possible ===== STEP 2: analysis =====Material valuation class 3100 (new) | grouping code 0001 | OBYC BSX missing for 3100 ===== STEP 3: fix =====Add BSX 0001/3100 → stock account (finance approved) → transport → test → repost GR

Real project scenario

A goods receipt for a new plant failed with an account determination error on BSX. The plant used a new grouping code without entries. The team added entries through an emergency transport with finance approval and added "OBYC complete" to the plant-creation checklist.

Common mistakes

Ignoring message details.
Manual FI postings as workaround.
Direct production changes.
Not reposting affected documents.
No prevention step.

Best practices

Read errors fully.
Use simulation.
Change via transport.
Repost cleanly.
Update checklists.

Interview angle

Questions: "How do you fix an account determination error?", "What does the error message tell you?", "How do you correct wrong postings?"
Strong answer: message analysis, cause categories, simulation, controlled fix, reversal/repost, prevention.

Practice this lesson

Quick check

1. During a plant rollout, GRs fail with an account determination error for BSX. What is the most likely cause?

2. A user reports an account determination error while posting a goods movement. According to the recommended diagnostic method, what is the most critical first step?

3. An account determination error occurs in production, blocking multiple goods receipts. Why is it strictly advised not to make a configuration change directly in OBYC in the production client?

Interview questions

1. A goods receipt posting fails with an account determination error referencing a missing entry for transaction key BSX. How would you diagnose and resolve this?

Answer it in your own words first, then compare.

2. A goods receipt for a new plant fails with an account determination error even though OBYC settings appear correct for existing plants. What sequence of checks would you perform to resolve it?