EAM:AM_DEPR_CALC Produces Incorrect Depreciation After An Asset Is Suspended, Re-categorized, Then Resumed (Doc ID 1578211.1)

Last updated on JULY 21, 2016

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

AM_DEPR_CALC produces incorrect Depreciation after an asset is Suspended, Re-categorized, then Resumed

Expected result:
Since its in-service date of 3/15/2000 to 3/31/2013, which is 157 periods, total accumulated depreciation should be 157 * $4,223.80 = $663,136.93.

Actual result:
After resuming depreciation for the asset with a resume date of 6/30/2009 (same as the suspension date), the new per period depreciation for the CORP book is $4,257.19. Applying this amount to the 157 periods comes to $668,378.83, which also does not agree with the total accumulated depreciation amount of $652,353.29 as found on the ASSET_NBV_TBL for the CORP book as of 3/31/2013.

Replication steps:
1. Create an asset with Transaction date in 2000-03-15 and accounting date 2012-10-31. Standard straight line depreciation for 480 periods with an initial cost of $2,027,425.00 should produce $4,223.80 worth of depreciation per period. Run Depreciation
2. Suspend the asset with trans date 2009-06-30 and accounting date 2012-11-01 on CORP book. Run Depreciation
3. Re-categorize and move the category with trans date 2000-03-15 and accounting date 2013-03-01. Run Depreciation.
4. Resume the asset with transaction date 2009-06-30 and accounting date 2013-03-20. Run Depreciation.

Cause

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