on 2025 Apr 11 6:33 AM
We are currently implementing SAP S/4HANA Public Cloud, focusing solely on the Finance (FI) module. As part of our asset accounting process, we are trying to post a fixed asset retirement integrated with a customer using the standard “Asset Retirement with Customer (Integrated)” app. During this process, we select the relevant customer and fixed asset, and assign a revenue G/L account for the transaction. Additionally, we enter the profit center as required by the client for reporting purposes.
However, upon simulation or posting, the system throws error KI248 stating:
"Account xxxxxxxx requires a true account assignment relevant to cost accounting."
The error indicates that the profit center assignment is considered only statistical and therefore not sufficient for revenue postings to this G/L account, which is defined as a Primary Cost or Revenue account with Cost Element Category 11 (Revenue).
Our client is not implementing or Profitability Analysis (CO-PA), and we do not have any real CO objects such as internal orders, WBS elements, or sales orders configured or available in scope. The requirement is simple: to record revenue against profit centers so financial statements can be generated by profit center dimension. We do not want to (and should not need to) maintain real CO objects, as they are not part of the project scope.
Despite entering a profit center, the system requires a true cost accounting object due to the nature of the cost element category. Since we are not implementing CO-PA, this requirement is currently blocking a valid business process in SAP Public Cloud. The error seems to enforce controlling behavior, even when controlling is not part of the activated scope in the cloud tenant.
Therefore, we request SAP Support to advise on how this can be resolved. Ideally, we would like to continue using a revenue G/L account (to reflect revenue properly in the P&L) and post to it with only a profit center, without the need for any additional CO-relevant object. If there is a configuration workaround, scope item adjustment, or recommendation for using a different G/L setup for such scenarios in SAP Public Cloud, please advise accordingly.
Request clarification before answering.
Hello dear user,
And thank you for asking your question in the SAP Community blog.
A similar error message has been solved already on this topic.
Have you checked the following note note below ?
This might be useful for your current issue.
Best regards,
Jeremy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 39 | |
| 20 | |
| 15 | |
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.