Requisition Sourcing Status is in Error When Payment Locations Are Not The Same On Contract And Requisition
(Doc ID 3043405.1)
Last updated on SEPTEMBER 24, 2024
Applies to:
PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Requisition stuck in error status in sourcing workbench when the price location on the requisition is different than the one on the contract, this only starts happening after upgrading to PUM#48 tools : 8.60.07
The issue can be reproduced at will with the following steps:
- Navigate to : Procurement Contracts > Add/Update Contracts and Create a general contract or a Purchase Order contract.
- Make sure that the price location on the contract line details is not the default one.
- Navigate to eProcurement> Create Requisition and create a new requisition for the same item/Supplier on the contract.
- On requisition line details make sure that the default supplier location is used (different than the one on the contract).
- Navigate to eProcurement > Buyer center > Expedite Requisition and source that requisition to a PO.
- Navigate to : Purchasing > Purchase Orders > Stage/Source Requests > Sourcing Workbench and review the sourcing status.
- Notice that it is in error status.
- This is not happening if the price location on contract is the same as the one on requisition.
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 |