Last updated on MARCH 24, 2016
Applies to:Oracle Assets - Version 12.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
When you reinstate the asset which has Extended Depreciation transaction, there is data corruption.
This problem occurs when the following conditions are met.
A. When you ran Extended Depreciation, you set past fiscal year on the First Period filed.
B. Asset has already canceled Extended Depreciation.
C. Asset has partial retirement transaction before reinstatement.
- Addition ***** 2012-03(MAR-11)
Book Type FA_CORP_BOOK Asset ID 123456 Book Class CORPORATE Asset Number 123456 Cost 2090000 YTD depreciation amount 0 Accumulated depreciation amount 2089000 DPIS 25-JUN-1996 Depren method JP-DB 7YR Salvage value 10% Depreciation limit amount 1000 JPY
- Run Extended Depreciation ***** 2013-04(APR-13)
Asset Number 123456 Avail Extended Depreciation Yes First Period APR-12 <= PAST fiscal year
- Cancel Extended Depreciation ***** 2013-04(APR-13)
- Partial Retirement with current month convention ***** 2013-05(MAY-13)
Retire Date 31-MAY-2013 Status PROCESSED Cost Retired 500000 Proceeds of Sale 0 Cost of Removal 0 Retirement Type FA_M ( Current month convention)
- Reinstatement ***** 2013-05(MAY-13)
COST ADJUSTED_COST ADJUSTED_RECOVERABLE_COST ALLOWED_DEPRN_LIMIT_AMOUNT EOFY_RESERVE 2090000 -208000 2089000 1000 2089000 2090000 999 2089999 1 2089000 2090000 -208000 2089000 1000 2089000 1590000 -158239 1589000 1000 1589239 2090000 * 1881000 * 2088000 * 2000 * 2088000
FA_BOOKS.ADJUSTED_COST, ADJUSTED_RECOVERABLE_COST, ALLOWED_DEPRN_LIMIT_AMOUNT and EOFY_RESERVE are incorrect after reinstatement.
As processsing and cancellation of extended depreciation happens in same year of retirement, trying to reprocess those transaction with standard logic.
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