C_TS4FI_2023 · Question #65
You perform the depreciation run for your assets. For a specific asset, you would like to post the depreciation specified in the asset master data. How do you achieve this?
The correct answer is A. By changing the corresponding error into a warning via configuration. Option A is correct because during the SAP depreciation run (transaction AFAB), the system may encounter an error that blocks posting - for example, when account assignment validation detects an inconsistency. By reconfiguring that specific error message to a warning (via…
Question
You perform the depreciation run for your assets. For a specific asset, you would like to post the depreciation specified in the asset master data. How do you achieve this?
Options
- ABy changing the corresponding error into a warning via configuration
- BBy removing the cost center from the asset master data
- CBy creating a substitution in Financial Accounting line items
- DBy setting the "identical" parameter as not activated in the account assignment configuration
How the community answered
(22 responses)- A55% (12)
- B14% (3)
- C5% (1)
- D27% (6)
Explanation
Option A is correct because during the SAP depreciation run (transaction AFAB), the system may encounter an error that blocks posting - for example, when account assignment validation detects an inconsistency. By reconfiguring that specific error message to a warning (via message control in customizing), the system no longer blocks the posting and will proceed to post the depreciation exactly as defined in the asset master data.
Why the distractors are wrong:
- B (removing the cost center) changes the asset master data itself, altering the account assignment rather than allowing the existing specification to post - the opposite of the goal.
- C (creating a substitution) replaces field values during posting, meaning you'd be posting different values than what's in the master data, not the values specified there.
- D (deactivating the "identical" parameter) affects how account assignments are compared across line items and doesn't address the mechanism that blocks the depreciation run from completing.
Memory tip: Think "error → warning = proceed." In SAP Asset Accounting, an error halts, a warning informs but allows posting. Whenever a depreciation run is blocked by a validation error, the fix is often found in message control configuration - you're not changing what gets posted, just the severity of the check that was blocking it.
Topics
Community Discussion
No community discussion yet for this question.