When Adding Requisition Lines To RFQ The Operating Unit Defaulting Is Not Correct
(Doc ID 2372095.1)
Last updated on MARCH 26, 2018
Applies to:Oracle Sourcing - Version 12.2.6 and later
Oracle Purchasing - Version 12.2.6 and later
Information in this document applies to any platform.
"MO: Default Operating Unit" profile is set for example to - 'Operating Unit 1'
User is creating a Request For Quotation (RFQ) from quick links (Sourcing Responsibility -> New RFQ) and is changing the Operating Unit (OU) for example to 'Operating Unit 2'.
On the Lines Tab, there is an option 'Add requisition Lines' that will direct customer to Demand workbench page. The Document Builder OU is getting defaulted as 'Operating Unit 1' instead of 'Operating Unit 2'. RFQ number is getting defaulted fine.
Now, as RFQ is of OU 'Operating Unit 2' while user is trying to search lines, it is giving the below error:
If user is adding again the RFQ number and the correct Operating unit, the data will be returned correctly without any error.
User is expecting to see the changed of the Operating Unit when trying to add requisition lines to the RFQ.
The issue can be reproduced at will with the following steps:
1. Sourcing Responsibility ->
2. Negotiation Tab ->
3. Create new Request For Quotation ->
4. Add title -> Select "Two stages" option ->
5. Operating Unit 1 -> Change the OU with Operating Unit 2 ->
6. Lines tab ->
7. Add requisition lines ->
8. OU displayed is Operating Unit 1 ->
9. Search ->
10. Error occurs
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!