2
Release 12: Where is the Option for Rollback Depreciation? Doc ID : Note:421352.1 Type: HOWTO Last Revision Date: 22-APR-2007 Status : MODERATED Applies to: Oracle Assets - Version: 12.0 to 12.0 Information in this document applies to any platform. FADRB - Rollback Depreciation Goal Where is the Rollback Depreciation process in Fixed Assets Release 12? Solution In Release 12 the concurrent process for Rollback Depreciation has been obsoleted and Release 12 now introduces Automatic Depreciation Rollback. After the initial run of Depreciation all of the assets stay in a depreciated state. If it is needed to perform additional transactions on particular assets (adjustment, retirement etc.) the user can go in an update those assets with whatever transaction is needed. For those particular assets the depreciation data is rolled back and the transactions can be performed on them. After this the user can run Depreciation again which will run much faster now because it is only the assets that were rolled back and updated that need to be depreciated again. From a performance standpoint this makes the process more efficient, there is no need to rollback all depreciation data for all assets and then rerun all of it again just to make changes to a smaller amount of assets.

Rollback Depreciation Process in Fixed Assets Release 12

Embed Size (px)

Citation preview

Page 1: Rollback Depreciation Process in Fixed Assets Release 12

Release 12: Where is the Option for Rollback Depreciation?  Doc ID: Note:421352.1 Type: HOWTO

 Last Revision

Date: 22-APR-2007

Status: MODERATED

Applies to:

Oracle Assets - Version: 12.0 to 12.0Information in this document applies to any platform.FADRB - Rollback Depreciation

Goal

Where is the Rollback Depreciation process in Fixed Assets Release 12?

Solution

In Release 12 the concurrent process for Rollback Depreciation has been obsoleted and Release 12 now introduces Automatic Depreciation Rollback.

After the initial run of Depreciation all of the assets stay in a depreciated state. If it is needed to perform additional transactions on particular assets (adjustment, retirement etc.) the user can go in an update those assets with whatever transaction is needed.

For those particular assets the depreciation data is rolled back and the transactions can be performed on them.  After this the user can run Depreciation again which will run much faster now because it is only the assets that were rolled back and updated that need to be depreciated again.

From a performance standpoint this makes the process more efficient, there is no need to rollback all depreciation data for all assets and then rerun all of it again just to make changes to a smaller amount of assets.