Problem With Wildcard % Search For Add/Update A Person Component

(Doc ID 2269263.1)

Last updated on NOVEMBER 01, 2017

Applies to:

PeopleSoft Enterprise CS Campus Community - Version 9.2 and later
Information in this document applies to any platform.


Why are users seeing some differences in the search record when % wildcard is used and CASE is different for primary names?

Test case:

On the Campus Community > Personal Information > Add/Update a Person screen, attempting to search for people with the last name of WILSHIRE or WILTSHIRE. Entered a last name search parameter of wil%shire.  Taken into the one record in the system that has a last name of WILSHIRE. However, when querying PS_NAMES table in the backend, there are 2 records with a last name of WILTSHIRE.



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