Document Builder Outcome Type LOV Is Missing Values - Add To Order and New Order

(Doc ID 2322861.1)

Last updated on OCTOBER 30, 2017

Applies to:

Oracle Sourcing - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

In Oracle Sourcing, Release 12.2.4, the options "Add to Order" and "New Order" are not displayed in the Document Builder "Outcome Type" list of values (LOV) in one environment.
However, these values are appearing in another environment.

It is expected that the Outcome Type LOV will show the values "Add to Order" and "New Order" when accessing the Demand Workbench page from Sourcing responsibility.
When accessing the Demand Workbench page from Purchasing's Buyer Work Center, the values are displayed there.

Due to this issue, users cannot select the option to "Add to Order" or "New Order" from the Demand Workbench in Sourcing responsibility.


Steps To Reproduce

The issue can be reproduced at will with the following steps.
In the examples below, Env A is using a custom responsibility and menu structure, while Env B is using the seeded Sourcing Super User responsibility and seeded menu.

1. Sourcing responsibility > Requisitions tab
On the Demand Workbench page, Document Builder region
- Env A - the Outcome Type list of values (LOV) contains the following values:
Add to Auction
Add To Order
Add to RFQ
New Auction
New Order
New RFQ
- Env B - the Outcome Type LOV contains the following values:
Add to Auction
Add to RFQ
New Auction
New RFQ
- Env B - the following values are not displayed in the Outcome Type LOV:
Add To Order
New Order


2. Purchasing responsibility > Buyer Work Center > Requisitions tab
On the Demand Workbench page, Document Builder region
- Env A - the Outcome Type LOV contains the following values:
Add to Auction
Add To Order
Add to RFQ
New Auction
New Order
New RFQ
- Env B - the Outcome Type LOV contains the following values:
Add to Auction
Add To Order
Add to RFQ
New Auction
New Order
New RFQ

So the values "Add To Order" and "New Order" are only missing from Sourcing responsibility in Env "A" above..


3. In the Purchasing Lookups form for lookup Type = PO_AUTOCREATE_ACTIONS, all of the above codes are enabled in both Env A and Env B.




Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms