Running PC_PO_TO_PC is Overriding Existing COM Rows In PROJ_RESOURCE When Change Order is Involved. (Doc ID 2125020.1)

Last updated on JULY 01, 2016

Applies to:

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

Symptoms

On : 9.1 version, Purchasing Integration

ACTUAL BEHAVIOR
---------------
Change Orders impacting existing PO rows are not creating new COM rows to PROJ_RESOURCE with Transaction Dates equal to current date and accounting date equal to PO header acctg dt; instead they are overwriting the PROJ_RESOURCE amount making Effective Dated reporting inaccurate for prior periods

EXPECTED BEHAVIOR
-----------------------
Change Orders impacting existing PO rows should create additional rows to PROJ_RESOURCE with Transaction Dates equal to current date and accounting date equal to PO header acctg dt and not overwrite the PROJ_RESOURCE existing date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create and dispatch a PO with Project Costing values (For Example: $300 on 4/1/2015)
2) Run Cost Collection (PC_PO_TO_PC) -- the RESOURCE_AMOUNT will be $300; Accounting and Transaction Dates will be 4/1/2015
3) At a later date (at least one day later) create a change order that increases the row from step 1 by $200 to $500 and dispatch. Day on 4/2/2015
4) Run Cost Collection (the COM row created in step 2 will be $500 with Accounting and Transaction Dates of 4/1/2015. The COM row created in Step 2 has been overwritten with the PO line changed amount.

The expectation is that the process should not change the existing row that has $300 on 4/1. Rather should create a new COM row for $200 on 4/2 leaving the original row intact.

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