My Oracle Support Banner

Requisition Getting Sourced Multiple Times Due to the Source Status Field not Getting Updated From "Available" to "Sourcing Complete" (Doc ID 1462228.1)

Last updated on FEBRUARY 06, 2024

Applies to:

PeopleSoft Enterprise SCM eProcurement - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.

Symptoms

Requisitions getting resourced multiple times to a Purchase Order because the Source Status is not getting updated from "Available" to "Sourcing Complete."


Replication Steps:

Part A

  1. Create Requisition and Save and Submit it.
  2. Approval requisition by login as SVxx and WENxxxxx by navigating to Worklist. You can also SVxx for both the stages as SVP1 has assigned roles to both the stages Hardware and Software buyer.
  3. Login back as VP1 - Navigate to Buyer Center > Quick Source and source the requisition.
  4. Check the PO Created.
  5. Navigate to Manage Requisition > Edit Requisition and click on Go to Edit the Requisition.
  6. Change the Qty of line 1 from 1 to 5 and Save and Submit.
  7. Here Change Request is triggered. Leave it as it is. Don’t approve any of these Change Requests.
  8. Line 1 Quantity is edited from 1 to 5, status of requisition is changed to ‘Pending’ and Change Request is triggered for approval, approval process is initialized and not completed.
  9. Check the status of Manage Requisition.
  10. Don’t approve this change request, leave it as it is.
  11. Now again go back to Purchasing > Add/Update PO and Cancel the PO.
  12. Select the Option of ”Yes, Re-Source all Reqs” and click on Continue.
  13. Now start the Change Request Approval process again. Approve the Change Request approval by stage 1 approve and then stage 2 approver. Navigate to worklist of SVP1  i.e. first stage approver similarly for another stage approver.
  14. Approve at 2nd stage. You can use either SVP1 and WENxxxxx or only SVP1. SVP1 has both the roles. Hence, SVP1 can also do both stages approver. I have used SVP1.
  15. Approval at 2nd stage and click OK.
  16. Now, Login as VP1 and check the Manage Requisition status.
  17. See the Change Request status, it is Ready for Process. Yet to be approved. Don’t approve it. Leave it as it is.
  18. Run the PO_POCHNG Process - Navigate to Buyer Center > Procurement Processes > PO Change Process.
  19. Run PO Auto Source process again - Navigate to Buyer Center > Quick Source Requisition.
  20. Check the PO.
  21. We are done with Req ID 211 for example.


Part B

  1. Lets leave the transaction as it is. As per the scenario this is whole one scenario.
  2. Start with a new Requisition
  3. Create Requisition for 2 Lines and Save and Submit.
  4. Req ID 212 gets created.
  5. Approve by Approvers at both stages. 
  6. Approved by 1st stage.
  7. Approved by 2nd stage approver.
  8. Login back as VP1 Requester and navigate to Buyer Center > Quick Source Requisitions and source the requisition.
  9. Check the PO Created.
  10. Navigate to Manage Requisition > Edit Requisition and click on Go to Edit the requisition. 
  11. Change the Qty of Line 1 from 1 to 5 and Save and Submit.
  12. Line 1 Quantity is edited from 1 to 5, status of requisition is changed to ‘Pending’ and Change Request is triggered for approval, approval process is initialized and not completed.
  13. Now go to Add/Update PO and Cancel the PO. 
  14. Select Yes to "Resource all Reqs" message.  
  15. Check the status of PO cancelled. 
  16. Approve change request by approvers at first stage for change request created
  17. Approved by 1st stage
  18. Similarly for 2nd stage Approver  
  19. See the Change Request Status is "Ready for Process." 
  20. Approve the Change Request finally by the Buyer-POS1  
  21. Check the status of Change Request and requisition
  22. Run PO_POCHNG process  
  23. Run the Quick Source (PV_AUTO_SRC) process 
  24. Check the new PO created.


Part C

  1. Create a requisition and Save and Submit then source it to PO.
  2. Approve at both the stages
  3. Quick Source
  4. Cancel the PO and check the requisition


Part D (same steps as in Part B)

  1. Same steps again - Create a Requisition and Save and Submit then run Quick Source to build a PO.
  2. Approve by both the stages
  3. Quick Source
  4. Check the PO Created
  5. Navigate to Manage Requisition > Edit Requisition and click on Go to Edit the requisition  
  6. Change the Qty of Line 1 from 1 to 5
  7. Save and Submit  
  8. Line 1 Quantity is edited from 1 to 5, status of requisition is changed to ‘Pending’ and Change Request is triggered for approval, approval process is initialized and not completed.
  9. Now go to Add/Update PO and cancel the PO. 
  10. Select Yes to "Resource all Reqs" message. 
  11. Check the status of PO cancelled. 
  12. Approve change request by approvers at first stage. 
  13. Similarly for 2nd stage Approver.
  14. See the Change Request status, it is Ready for Process. 
  15. Approve the Change Request finally by the Buyer-POS1. 
  16. Approve all the Change Requests this time.
  17. Run PO_POCHNG Process.
  18. Run the Quick Source process. 
  19. Check the new PO created.
  20. As you can see there are 3 more PO’s after last PO 359.
  21. Lets check PO 360.
  22. It is still getting created from Req 207 as told in the starting.
  23. Lets check PO 361.
  24. See the issue is replicable again . Req ID 211 is getting sourced apart from Req ID 207.
  25. Lets check Manage Requisition status for Change Request for Req ID 214.
  26. Lets run the PO Auto Source process again, this is the problem area. Every time the User runs the Quick Sourcing Process, the system creates a PO of Qty 4.
  27. Lets run the Quick Sourcing Process again.
  28. Last created PO was 362.
  29. There are 2 new PO’s getting created. One for Req ID 207 and other for Req ID 211.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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