EEX 9.2: Maximum Number Of Records (4,2) Error Message When Searching Travel Authorizations In Fluid User Interface If More Than 300 Expense Locations Have Been Defined In The System
Last updated on SEPTEMBER 19, 2016
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
While searching for existing Travel Authorization transactions (Pending, Approved, Submitted, All) in Fluid User Interface, the system throws a Warning Message. It has been determined that this comes from the fact of having more than 300 valid Expense Locations under one Set ID value, (Records PS_EX_LOCATION_MAP, and PS_EX_LOCATION_TBL).
This seems to be similar to the issue originally reported by Defect # 11550914 (EX: Printing a Travel Authorization or Time Report gets maximum number of records error). This happened in Classic Online PIA when trying to view or print existing Travel Authorizations, and Time Reports. Same problem still seems to be taking place when using Fluid UI now.
The Warning Message can be clicked away by the User, but it is confusing, as it gets triggered each time this Travel Authorizations Search page in Fluid is accessed, and does not offer enough information to determine what is causing it to appear on the first place.
Such Warning Message should not be triggered by the system.
- Perform the necessary SQL Inserts to ensure that Record PS_EX_LOCATION_MAP contains more than 300 values under Set ID SHARE
- Perform the necessary SQL Inserts to ensure that Record PS_EX_LOCATION_TBL contains more than 300 values under Set ID SHARE
- Log into the FSCM Online Application as User ID VP1
- Go to the Employee Self-Service Homepage in Fluid User interface
- Click on the Travel Authorizations tile
- The system throws an Error Message
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
" Maximum number of records found matching specified key(s) -- others not included in list. (4,2)
When performing a Lookup, the database returned more rows than can be accommodated in the list box.
Use a Partial Key value or Advanced Search to limit the number of rows returned or specify more characters to further qualify the key value. "
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