EAM: Consolidated/Unitized Asset Not Capitalizing Properly (Doc ID 2299844.1)

Last updated on AUGUST 22, 2017

Applies to:

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

Symptoms

On : 9.2 version, Integration

ACTUAL BEHAVIOR
---------------
Consolidated/Unitized Asset Not Capitalizing Properly



EXPECTED BEHAVIOR
-----------------------
Need to have all CAP rows

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a PO with two lines quantity of 2 for each line
2. Dispatch PO
3. Receive the two lines (leave asset id set to NEXT)
4. Run AMPS1000 to interface lines to AM
5. Consolidate the two Interface lines to one new pending line
6. Unitize the new pending line into two new lines
7. Load the two new assets
8. Create a voucher for the two assets
9. Approve, Match, Post Voucher
10. Run INTFAPAM
11. Run AMPS1000
12. Note that new rows are FAD rows instead of CAP rows
 


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot have CAP rows.

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