Transfer in Period of Addition Does Not Move Catchup Depreciation to New Account Code (Doc ID 1459672.1)

Last updated on DECEMBER 14, 2016

Applies to:

Oracle Assets - Version 11.5.10.2 and later
Information in this document applies to any platform.
This happens post of the fix for <>, which delivers these code levels:

For 12.1.x:
FAVVALB.pls 120.69.12010000.34
FAXASSET.fmb 120.208.12010000.63

For 12.0.x:

FAVVALB.pls 120.65.12000000.38
FAXASSET.fmb 120.189.12000000.81

For 11i :

FAVVALB.pls 115.180
FAXASSET.fmb 115.560

Goal

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.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms