Inactive Category Error When Create RFQ Line Even Though Category Is Active And Enabled
(Doc ID 1510480.1)
Last updated on FEBRUARY 05, 2019
Applies to:Oracle Sourcing - Version 12.1.3 to 12.2.8 [Release 12.1 to 12.2]
Information in this document applies to any platform.
In Oracle Sourcing, Release 12.1.3, an error occurs on the Create RFQ Lines page when using to use the Category list of values to select the Category value.
1. Query has exceeded <NUMBER> rows. Potentially more rows exist, please restrict your query.
2. Error - Inactive Category in Line 1. Please enter a valid and active Category.
Steps To Reproduce
The issue can be reproduced at will with the following steps in a Vision Demo environment:
Set the value of "FND: View Object Max Fetch Size" to "15" at the User level, for user <USERNAME>.
1. Log in to Oracle Applications as user <USERNAME>.
2. Select the Sourcing Super User responsibility and navigate to the Sourcing Home Page.
3. On the Negotiations Home page, under the Create section, click the RFQ link to create a new RFQ.
4. On the Create RFQ: Header page, enter the Title and then the Save As Draft button. Then, click the Lines link on the left-hand side of the page.
5. On the Create RFQ: Lines page, select Actions = Create Line and click the Go button.
6. On the Lines: Create Line 1 (RFQ) page, enter the Description and Quantity values.
7. Still on the Lines: Create Line 1 (RFQ) page, enter the value "2%" and click the LOV icon.
8. In the Search and Select: Category window (the list of values), select any value from the LOV window. Notice that there are 30 results returned (on multiple pages) for the search "2%".
9. Back on the Lines: Create Line 1 (RFQ) page, click the Apply button. The error occurs at this point.
Due to this issue, users cannot correctly search for the Category values when creating an RFQ line.
The error occurs when the number of rows returned by the Category value search is greater than the value of the setting for profile option "FND: View Object Max Fetch Size".
The workaround is to set the profile to a very high value; however, this can potentially lead to performance issues in other areas of Oracle Applications.
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