OTBI 'Fixed Asset - Depreciation Real Time' Is Showing Unexpected Depreciation Reserve Amounts for Assets with Backdated DPIS after Migration.
(Doc ID 2676621.1)
Last updated on JUNE 02, 2020
Applies to:Oracle Fusion Assets Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.
The OTBI 'Fixed Asset - Depreciation Real Time' analysis has been ran with filter on "Depreciation Source Code" = 'D', with the purpose of reviewing the depreciation reserve amounts right after data migration from legacy system.
Taking the example of 2 assets:
1) asset number 1, loaded with backdated DPIS and without Depreciation Reserve already provided in the addition transaction. For this asset the system calculated catch-up depreciation.
2) asset number 2, loaded with backdated DPIS and with Depreciation Reserve already provided in the addition transaction. For this asset the system did not calculate catch-up depreciation, since accumulated depreciation was already provided.
For asset 1, the OTBI analysis displays the Depreciation Reserve = 0.
For asset 2, the OTBI analysis displays the Depreciation Reserve = 5579.95.
Expected behavior would have been for both assets to display the accumulated depreciation as seen in Asset Inquiry.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document