M8 147 — M8 147 — Account Determination for Entry Is Not Possible

M8 147 is an automatic account-determination error. During a logistics posting, SAP derives an accounting key from the business transaction and valuation context, then searches account determination for a matching G/L account. The message means that no valid account could be found for the derived combination. The text can include the chart of accounts, transaction key, valuation grouping code, account modifier and valuation class. Because the message is raised at accounting determination, the inventory or warehouse transaction may be operationally valid while the financial posting cannot be completed.

The most common cause is a missing OBYC entry for the required transaction key and valuation class. New materials, new valuation classes, new plants or valuation areas, or a new chart-of-accounts setup can expose combinations that were never configured. Account modifiers for movements such as GBB can make apparently similar goods movements determine different accounts. Valuation grouping code assignments can be inconsistent across plants. In EWM-integrated scenarios, goods-movement queues can remain stuck because the ERP-side accounting determination is incomplete. Another cause is that material master or valuation-class data is wrong, so SAP correctly looks for a combination that the business never intended to use.

Read every variable shown in the M8 147 message. Identify the transaction key, account modifier, valuation class, valuation grouping code and chart of accounts. Check the material valuation data and confirm the valuation class is appropriate for the material type and business process. Review plant/valuation-area grouping and then inspect OBYC for the exact derived key. If the issue is movement-specific, compare a successful material document with the failing one and note the movement type and account modifier. In an EWM or queue scenario, inspect SMQ2 only to understand the failed business document; the financial root cause still needs to be resolved in ERP/S/4HANA account determination.

Maintain the missing automatic account-determination entry when the derived combination is correct and approved by Finance. If the valuation class or valuation grouping is wrong, correct the master/configuration source instead of adding an account for an unintended combination. For GBB and similar keys, verify the account modifier produced by the movement type before adding entries. After configuration is corrected, test the goods movement directly in a controlled scenario and then reprocess the failed queue or document. Validate the resulting debit/credit accounts with FI; a posting that succeeds technically but hits the wrong G/L account is not a valid resolution.

A common emergency fix is to copy an existing G/L account into the missing OBYC combination just to release the queue. That can misstate inventory, consumption, price differences or other financial categories. Another poor fix is to change the material valuation class solely to match an existing account-determination row. Valuation class is a business/accounting attribute and can affect many postings. The right sequence is to prove the expected transaction key and valuation class, confirm Finance's intended account, and then maintain the correct mapping.

MM account determination and FI jointly own M8 147. MM identifies the movement, valuation class and transaction key; FI approves the target G/L account and chart-of-accounts impact. EWM or logistics teams are stakeholders when a warehouse queue is blocked, but they generally do not own the financial configuration. Master-data teams may be involved if the valuation class is incorrect. ABAP is rarely required unless a custom movement or enhancement is deriving an unexpected account modifier or valuation context.

Do not maintain OBYC using only the transaction key while ignoring valuation grouping, modifier and valuation class. Do not assume two plants share the same grouping. Check whether the material is valuated differently by area or split valuation. When reprocessing queues, ensure the configuration transport is present in the target system before retrying. Be careful when copying configuration between company codes with different charts of accounts. Finally, validate the accounting document after the fix; absence of M8 147 proves only that an account was found, not that it was the correct one.