How Requirement Score Is Used During Automatic Award Recommendation for Negotiations?
(Doc ID 2234825.1)
Last updated on OCTOBER 10, 2018
Applies to:Oracle Fusion Sourcing Cloud Service - Version 126.96.36.199.0 and later
Oracle Fusion Sourcing - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
User has created a negotiation. User has defined requirements by adding predefined sections and manual ones with response values, weights and scores. After the responses are all in it was noticed that the 'automatically award' functionality always chooses the supplier who provides the lowest overall amount (for the whole negotiation or several lines, depending on the setup).
Supplier A who scores best on requirements (100%) and best on attributes (manual decision) but has a higher price
Supplier B who scores worst on requirements (0%) and worst on attributes (manual decision) but has lower price
The system will never choose supplier A because it evaluates on price only, which means he will always choose supplier B.
How requirement scores and attributes are valued during automatically award functionality ?
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