Solved: Search help without case sensitivity

Former Member · ‎11-24-2004

Hi!

The standard search help for eg. materialetext is case sensitiv.

Is it possible to make a search help case insensitiv?

Regards!

Former Member · ‎11-24-2004

Hello Martin,

Firstly, I'm sorry that I did not look a little deeper into the problem. I have found out what you mean and I shall explain it to you -

The table MAKT contains the Material Descriptions. If you have observed there are two fields of interest to us in this table - MAKTX and MAKTG. Semantically, the content in both these fields is identical, except for the fact

that MAKTG is the UPPERCASE version of MAKTX. Now consider the domains for these two fields -

MAKTX has the domain TEXT40, for which the attribute Lowercase has been set.

MAKTG, on the other hand, has the domain CHAR40 for which the Lowercase attribute is unchecked.

The Field MAKTG, as the short description says, has been created exclusively to be used in search-helps. However, if you do a where-used list on the data-element MAKTX, you will find that it is still being used in some search-helps. So, whenever you have a field that has been declared with reference to a DDIC field which has the search help based on MAKTX, you will find the search to be case sensitive. And in that case, I don't think we can do anything about it. But if you tell me the exact nature of your problem, we can think of a workaround.

Hope this drives the point home and clarifies the concept, if not provides a solution :-).

Regards,

Anand Mandalika.

Former Member · ‎11-24-2004

Hi Martin,

I'm not sure if I understand your problem. The standard search help for material description runs over field MAKTG which is the uppercase translation of the material description. This should work case insensitive?

Regards,

John.

Former Member · ‎11-24-2004

Hi Martin,

I'm sorry, but I have not found any case sensitivity in case of the search help you have mentioned. If you could provide me with the exact search help name for which you are facing this problem, I will be in a better position to help you.

Regards,

Anand Mandalika.

Former Member · ‎11-24-2004

Hello Martin,

Firstly, I'm sorry that I did not look a little deeper into the problem. I have found out what you mean and I shall explain it to you -

The table MAKT contains the Material Descriptions. If you have observed there are two fields of interest to us in this table - MAKTX and MAKTG. Semantically, the content in both these fields is identical, except for the fact

that MAKTG is the UPPERCASE version of MAKTX. Now consider the domains for these two fields -

MAKTX has the domain TEXT40, for which the attribute Lowercase has been set.

MAKTG, on the other hand, has the domain CHAR40 for which the Lowercase attribute is unchecked.

The Field MAKTG, as the short description says, has been created exclusively to be used in search-helps. However, if you do a where-used list on the data-element MAKTX, you will find that it is still being used in some search-helps. So, whenever you have a field that has been declared with reference to a DDIC field which has the search help based on MAKTX, you will find the search to be case sensitive. And in that case, I don't think we can do anything about it. But if you tell me the exact nature of your problem, we can think of a workaround.

Hope this drives the point home and clarifies the concept, if not provides a solution :-).

Regards,

Anand Mandalika.