ERPClimb logoERPClimb
Login

M8 147

No G/L account found

MIGO or MIRO fails with "Account determination for entry ... not possible".

Quick answer

Most likely cause
Missing OBYC entry for the transaction key (BSX, WRX, GBB...) and valuation class.
Check first
The message details: chart of accounts, transaction key, valuation modifier, valuation class
First resolution step
Read the full message to get the transaction key and valuation class.

Likely root causes

  1. Missing OBYC entry for the transaction key (BSX, WRX, GBB...) and valuation class.
  2. A new plant's valuation area has no valuation grouping code assigned.
  3. The material has no valuation class, or the wrong one.

What to inspect

  1. The message details: chart of accounts, transaction key, valuation modifier, valuation class
  2. OBYC – automatic account determination
  3. MM03 – Accounting 1 view for the valuation class
  4. OMWD – valuation grouping code

Resolution path

  1. Read the full message to get the transaction key and valuation class.
  2. Check OBYC for that key and valuation class combination.
  3. Check the material's valuation class in MM03 and the plant's grouping code in OMWD.
  4. Maintain the missing entry with Finance approval in development.
  5. Transport it through the landscape; never configure directly in production.

Share this diagnosis

Paste a credited summary into a ticket, chat or forum reply. Your pasted input is never included.

ERPClimb is an independent platform and is not affiliated with SAP SE.