Customer search help: KNA1-NAME3 is case-sensitive. Why?

Question:
Dear all,
The problem with search help on customers.
I created a customized search help, technically it's quite simple, based on the only table KNA1, and the only enhancement was to add selection field KNA1-NAME3. However, it has unpleasant feature: this field NAME3 is case-sensitive, so results on search for *white* and *White* are quite different. At the same time, search field KNA1-NAME1 is not case sensitive.
Question: can anybody tell me why there is such difference? is there any way to change it (make NAME3 case-insensitive?
Thank you.
Answer:
There is a special Matchcode field (MCOD1) which contains an all-upper-case version of the name1 field. When you search on the name1 field, SAP usually uses the mcod1 field thereby giving a case-insensitive search.
Answer:
There is a special Matchcode field (MCOD1) which contains an all-upper-case version of the name1 field. When you search on the name1 field, SAP usually uses the mcod1 field thereby giving a case-insensitive search.
Thank's mate for your help.
You are right of course. Then, if we have actually 3 such fields in KNA1: MCOD1,2,3, and the last one "linked" to ORT01 field, can we by some means change it and set link to NAME3->MCOD3?
I am not an ABAPer, so sorry for stupid question(s).
runman
Answer:
Hi Runman,
You can use the transaction 'OBB2' to check search fields for customer matchcodes. Go through the IMG activity documentation as well.
Have fun,
Manoj
Answer:
You can use the transaction 'OBB2' to check search fields for customer matchcodes. Go through the IMG activity documentation as well.
Thanx Manoj,
Good transaction... I never stop to be tricked by SAP... The only issue will be to make it work for retrospective customer master data, but technically we will fix it.
Thanks guys for your help!

More Articles:

Material extension from one plant to another.?
Internal Table problem?
BAPI_GOODSMVT_CREATE - 101 movement with no matnr?
A quick thing on Inner Join?
Summing records in an internal table?
Dyanmically assigning value and increasing input/output box?