Transfer in Period of Addition Does Not Move Catchup Depreciation to New Account Code
(Doc ID 1459672.1)
Last updated on SEPTEMBER 04, 2020
Applies to:Oracle Assets - Version 220.127.116.11 and later
Information in this document applies to any platform.
This happens post of the fix for <
For 11i :
You have entered an addition that caused catchup depreciation to be taken, usually because the date placed in service (DPIS) is backdated to an earlier period. Following this entry, you realize the code combination is wrong. You enter a transfer to move the asset to the new code combination. The transfer defaults it's effective date to the end date of the open period, instead of DPIS, and finishes normally. However this does not move the catchup depreciation's expense to the new combination.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!