Incorrect Buyer Defaulted To PO when Expediting Requisitions
Last updated on SEPTEMBER 28, 2017
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Issue:-Incorrect Buyer Defaulted To PO when Expediting Requisitions
Steps To Reproduce the Issue:-
Primary Buyer for Item Category HARDWARE is set as ‘CHRISBAKER’
Primary Buyer for Item Category ALLITEMS is set as ‘WENDYCHO’
For VP1 the Buyer is set to VP4 under User preferences
1.Create an ePro Requisition, special request , line 1 with ALLITEMS category ,Line 2 with HARDWARE category
2.Check the Line 1 details.WENDYCHO got defaulted from category setup ,Check the Line 2 details.CHRISBAKER got defaulted from category setup
3.Submit the Requisition
4.Now Go to Expedite Requisition Page. Populate the Requisition, Now select the Line 1 first and then the Line 2 and Submit.Check the Sourcing workbench .PO created.PO created with WENDYCHO as the Buyer.
5.It is observed that whatever the line which you select first on the Expedite Requisition page, the PO created with Buyer defaulted on that line. For eg if we select line 2 first and then line 1 then the PO gets created with CHRISBAKER.
Also if we select Include all checkbox, then the PO get created with Buyer specified in the User preferences of the User.
Now test the same scenario using Quick Source.
1.Copy the same Req .Save and Submit.Quick Source the Requisition
2.Check Sourcing Workbench
3.Note the PO got created using the Buyer specified in the User Preferences.
So Quick Source and Expedite requisitions are behaving differently.
Further one more thing was observed that if for both the Req lines we specify only one Buyer (for eg.WENDYCHO) then the PO will be created with WENDYCHO.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms