My Oracle Support Banner

E-PIA: / E-PPR: Type Ahead on Fields With Prompt Lookups Is Not Returning the Correct and Expected Values for the Field, When Keyword Search Is Enabled in Configurable Search, Causing the Page to Time Out (Doc ID 3022673.1)

Last updated on MAY 14, 2024

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.60 and later
Information in this document applies to any platform.

Symptoms

Type ahead on fields with prompt lookups is not returning the expected values for the field, when Keyword Search is enabled in Configurable Search, causing the page to time out.
It seems to bring the results that would be valid for the next field. For Example, in page 'Owned Assets' (FSCM 9.2: Menu > Asset Management > Asset Transactions > Owned Assets > Basic Add), for the field Business Unit, type ahead is bringing back the Asset IDs for the Business Unit, instead of simply the Business Unit, matching what was entered for the field, and its Description. If the Business Unit value is only partially entered, type ahead returns 'No matching values were found'.

It was expected for type ahead to return the values that are related to the field being entered at the time. For example, if entering the value for Business Unit, only the list of Business Units, and their respective Descriptions, matching the data entry, should be returned.

The issue was reproducible in the customer site with the following steps:
[Note: Page 'Owned Assets' is used as example FSCM 9.2: Menu > Asset Management > Asset Transactions > Owned Assets > Basic Add]

1- Keyword Search must be enabled.
    1.1- To have Keyword Search function as intended, you must deploy and run the index process for the related search definition, in this case EP_AM_ASSET.
    1.2- In Configurable Search, set Keyword Search as the Search Type. Search Definition: EP_AM_ASSET
    
2- Navigate to the page - Menu > Asset Management > Asset Transactions > Owned Assets > Basic Add.
3- In Business Unit, type the first characters of a known Business Unit, on the Search page.
    Expected result would be different BU’s to come back - for example, typing in 'AUS' should give the prompt of 'AUS01', 'AUS02', etc.
    Instead, it comes back with 'No matching values were found'.
   
    3.1- Click on the Prompt Lookup icon for Business Unit. It actually returns the Business Units, as expected - 'AUS01' and 'AUS02'.
    3.2- Back to the Business Unit, type the full name of the Business Unit - AUS01 - and note that type ahead brings up the list of the Asset IDs for that Business Unit. It should return only the Business Unit and its Description.
    
This happens across all Keyword Search enabled search pages. For example, Business Units in Add/Update POs brings back the PO IDs instead.
In some cases, the Type Ahead feature is trying to fetch a big amount of data, causing the page to just spin until it times out. Users are then kicked out of the system. Their only alternative is to use the Prompt Lookup, before entering any data, thus avoiding Type Ahead on the impacted fields.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.