PeopleSoft Enterprise Project Costing: REQ (REQUISITION) ROW NOT DELETED AFTER CLOSING REQUISITION (Doc ID 1559123.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

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

Symptoms

In the past bug 12897362 had been created, which was closed as working as designed. However, there is an issue with closing the requisition. A requisition (REQ) row has been created in Project Costing. The PO is cancelled using the option "No, Do Not Re-Source Reqs". Using that option the system does not allow you to cancel the requisition.

However, the system does allow you to close the requisition, which is wrong. As we chose the option "No, Do Not Re-Source Reqs", you are not allowed to cancel the requisition and therefore closing it should also not be allowed. Run the PC_PO_TO_PC and PC_POADJUST. The REQ row has not been deleted, which is wrong. The system should have deleted the row as the requisition has been closed.

Either we prevent the user from closing a requisition when the option "No, Do Not Re-Source Reqs" is used by presenting an error message on the Reconciliation Workbench or we have to change the engines PC_PO_TO_PC or PC_POADJUST to delete the REQ row when the requisition is closed.

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