EAM: After Consolidating PO Receipts With NAD (Non Financial Add) Transactions, Interfacing the Associated PO Vouchers Creates Additional Asset IDs. (Doc ID 2976509.1)

Last updated on SEPTEMBER 27, 2023

Applies to:

Symptoms

After Consolidating PO Receipts with NAD (Non Financial Add) transactions, Interfacing the associated PO Vouchers creates additional Asset IDs.
Expecting the initial Consolidated Cost/Asset ID to be capitalized and no Additional Asset ID to be created


The issue can be reproduced at will with the following steps:

1. Create two (2) PO's with single line distributions (i.e.,100% costed).
Ensure that capitalize check box is not selected on the asset information tab.
Menu > Purchasing > Purchase order > Add / Update PO.
2. Create Receipts for the PO's created above. Enter the same Tag and serial id in each receipt (optional).
Menu> Purchasing > Receipts > Add/Update Receipts.
3. Create two (2) Vouchers, by selecting Copy from PO Receipt option.
Menu > Accounts Payable > Vouchers > Add/Update > Regular Entry
4. Process receipts using PO receiver push process.
Menu > Purchasing > Receipts > Process Receipts.
5. Run the AMPS1000 process to retrieve PO information.
Menu > Asset Management > Send/Receive Information > Retrieve Info from AP/PO.
6. Consolidate the two (2) interface line asset information.
Menu > Asset Management > Send/Receive Information > Interface Transactions > Consolidate Assets.
7. Run transaction loader process (AMIF1000), Total of 1 asset is created.
Menu > Asset Management > Send/Receive Information > Interface Transactions > Load into AM.
8. Process the two (2) asset vouchers using the Load Asset Request process.
Accounts Payable > Batch Processes > Extracts and Loads > Load Assets Request.
9. Run the AMPS1000 process to retrieve Voucher information.
Menu > Asset Management > Send/Receive Information > Retrieve Info from AP/PO.
10. Run the transaction loader process (AMIF1000).
The asset created in step 7 above is capitalized (interface type = "CAP"), however, a new asset is also created (interface type = "FAD" and not "ADQ" which is what is expected).
Menu > Asset Management > Send/Receive Information > Interface Transactions > Load into AM.

Detailed DEMO Replication Steps Attached

Changes

 The issue occured after upgrading to FSCM 9.2.37

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.