C_TS452_2410 · Question #54
In which cases do you receive an error message from the system if the automatic account determination was set up incorrectly? There are 3 correct answers to this question.
The correct answer is A. In case of material price change C. In the event of a transfer from one inventory type to another D. In the event of a transfer from one company code to another. Automatic account determination errors in SAP only surface during transactions that trigger actual financial postings to the general ledger. A material price change (A) requires posting the valuation difference to G/L accounts, so a misconfigured account key immediately…
Question
In which cases do you receive an error message from the system if the automatic account determination was set up incorrectly? There are 3 correct answers to this question.
Options
- AIn case of material price change
- BIn the case of a booking in the goods receipt blocked stock (GR blocked stock)
- CIn the event of a transfer from one inventory type to another
- DIn the event of a transfer from one company code to another
- EIn case of a price change of the purchasing info record
How the community answered
(27 responses)- A85% (23)
- B7% (2)
- E7% (2)
Explanation
Automatic account determination errors in SAP only surface during transactions that trigger actual financial postings to the general ledger. A material price change (A) requires posting the valuation difference to G/L accounts, so a misconfigured account key immediately produces an error. A cross-company-code transfer (D) involves inter-company clearing accounts and complex account assignments, making it highly sensitive to incorrect configuration. A transfer between inventory types (C) - such as unrestricted to quality inspection stock - can trigger valuation postings depending on the movement type, so missing or wrong account assignments will also cause an error.
Why B is wrong: Goods receipts into GR blocked stock (movement type 103) are non-valuated - no accounting document is created at that point, so account determination is never called and no error appears.
Why E is wrong: Changing the price in a purchasing info record is a master data update only - it creates no financial posting whatsoever, so account determination is never triggered.
Memory tip: Ask yourself, "Does this action create a financial document?" If yes (price change, company-code transfer, inventory-type transfer), account determination runs and can fail. If no (GR blocked stock, PIR price update), it never runs and can never error - the misconfiguration stays invisible until a real posting occurs.
Topics
Community Discussion
No community discussion yet for this question.