Last updated on MAY 03, 2017
Applies to:Oracle Sourcing - Version 12.2.5 and later
Information in this document applies to any platform.
In Oracle Sourcing, Release 12.2.5, the RFQ "Outcome" field value is changing back to "Standard Purchase Order" after the user has previously changed it to "Blanket Purchase Agreement".
It is expected that the value of the Outcome field will remain "Blanket Purchase Agreement" when the user has entered that same value.
The functionality was working fine in Release 12.1.3 and is noticed to occur after the upgrade to R12.2.5 was performed.
Due to this issue, users cannot create the new RFQ documents with the proper outcome value.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
1. Log in to Oracle Applications, using the Sourcing Super User responsibility > Sourcing > Sourcing Home Page.
2. On the Negotiations home page, click the link to Create RFQ.
3. On the Create RFQ: Header page, the Outcome value has defaulted to "Standard Purchase Order". Change the value to "Blanket Purchase Agreement".
4. Click the Save as Draft button. A message appears, which is correct because there is a mandatory DFF enabled on the RFQ headers page.
The following required field does not have a value: Procurement Type
5. Scroll down to the bottom of the header page. In the Additional Header Attributes region (DFF), enter the value for Procurement Type (this is the DFF field name).
6. Click the Save as Draft button. The Outcome field value has now changed back from "Blanket Purchase Agreement" to "Standard Purchase Order".
The issue occurs when the user has selected the Outcome field value before entering the required DFF field value.
As a workaround, if the user enters the mandatory DFF header value before changing the Outcome value, the Outcome value is then saved properly. However, the logical use of the page is to enter the Outcome field value first, since it is at the top of the Create RFQ: Header page and the DFF field are at the bottom of the page. The workaround is not acceptable because users most of the time will not catch the changed value of the Outcome field.
Upgrade from Release 12.1.3 to Release 12.2.5
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