EAM: After Recat From Depr To Non Depr, Asset Status Is In Service

(Doc ID 2372741.1)

Last updated on MARCH 12, 2018

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

After Recategorizing an Asset from a Depreciable category to a Non Depreciable category, the asset remains In Service. Then after retiring the asset and reinstating it, the asset status is changed to Suspended. Upon retiring the asset a second time, proceeds and removal costs are required when none exist for the asset retirement.


Expected Behavior
--------------------------
It is expected that the asset status will be set to Suspended when the asset is recategorized. Once recategorized, retired, and reinstated, when attempting to retire the asset a second time, it is expected that the retirement will save without requiring proceeds or removal costs.

Steps
--------------
This issue can be replicated by performing the following steps:

1. Change category of a depreciating asset to Non Depreciable category.
a. Asset Status Remains In Service - Note: This is the first issue.
2. Retire the Asset.
a. Asset status gets changed to Disposed
3. Reinstate Asset.
a. Asset status gets changed to Suspended
4. Re-retire the Asset
a. Proceeds or Removal costs required. Note that ps_book.retired_sw is 'Y' for both books even though the asset is reinstated. Note: This is the second issue.
5. SQL update the  ps_book.retired_sw to 'N' for both books.
6. Re-retire the asset. Note that the retirement saves successfully.  
a. Asset status gets changed to Disposed

Business Impact
--------------------------
1. The asset is in the wrong status after the recategorization. It is in service when it should be suspended. This discrepancy will skew reporting.  
2. Once the asset is recategorized, retired, and reinstated, when attempting to retire the asset a second time, the system requires the entry of proceeds or removal costs when both fields should be zero. This discrepancy will skew reporting.  

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