E1: FDA: UDC Search Screen (P0005S) Has Become Case Sensitive in 9.2?
(Doc ID 2469001.1)
Last updated on JULY 21, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.
UDC Search by "description 1" or "description 2" has become case sensitive in 9.2? and the followings symptoms have been observed
1. If there is no translation record exists in the translation table like F0005D , UDC (p0005S) application gives no result by description 1& 2 search with either case like e* and E* whilst the expected results is "English" to be returned
2. After adding at least one translation record in F0005D table, description search start working fine and it overrules the case sensitivity issue, and able to see results with either case like e* or E*, in both the cases, getting same results like "English"
3. On further test noticed that, when there is a change in the User profile languages, that also reproducing case sensitive issue in some cases like
a. if user profile is non English and have records in the translation table, case sensitiveness is completely ignored and get the results irrespective of search case like e* or E*
b. if user profile is English and have records in the translation table, case sensitiveness is completely ignored and get the results irrespective
of search case like e* or E*
c. if user profile is BLANK and have records in the translation table, case sensitiveness is active and don't get the results when search by case like e*??
So basically, there are two issues observed here
Issue#1- Why case sensitivity is related with translation record? if no records in the translation table, case sensitivity has become enabled and having at least one record in the table, case sensitivity has become inactive?
Issue#2- Why case sensitivity has become active when user profile language is BLANK?
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