Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

case sensitive issue

Former Member
0 Likes
1,241

When searching for a contract, certain fields are case sensitive and will not provide results if the lower case is used. For instance, when search in the Contract Name field in "Active Contracts", if you enter xyz no values will come up. If you enter "XYZ* several locations will come up.

Is there a way for this to either be corrected to accept and recognize both upper or lower case or at a minimum provide a warning to use only capital letters? It is frustrating getting "no values" for a location that we know exists. Its urgent ... pls help gurus

Thank you,

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,196

if you are doing that programaticcy then use statement TRANSLATE text TO UPPER CASE to chng the data to upper case always and then use..

otheriwse check for any EXITS or OSS notes for that TCode...

That's the only option...

11 REPLIES 11
Read only

Former Member
0 Likes
1,197

if you are doing that programaticcy then use statement TRANSLATE text TO UPPER CASE to chng the data to upper case always and then use..

otheriwse check for any EXITS or OSS notes for that TCode...

That's the only option...

Read only

0 Likes
1,196

Hi Ram

Thanks for the same... but i am not doing it via program .... i have debugged also there i found the TRANSLATE<> TO UPPERCASE .... can u give me some other suggesstions how do i proceed....... thanks a lot

Read only

Former Member
0 Likes
1,196

If this is in a SELECT statement, you may be able to use native SQL.

Rob

Read only

Former Member
0 Likes
1,196

if you are tring to search using the find button

then in the popup that comes up, the is a check box <b>Match Case</b> , check that and search

Read only

0 Likes
1,196

HI

let me tell u clearly .... i am in the transaction RECN ... here i enter the company code . and for the contact no i use the search help .... in the same i do for the active contract and in that if i enter the contract name in lower case it will not take... and if i enter the same in the upper case ... it displays the result .... i hope i made myself clearer .... how can i give a warning message to avoid this mistake.... pls help

Read only

0 Likes
1,196

What table does the search help look at?

Rob

Read only

0 Likes
1,196

THE VIEW IS V_RECNCNB , RECNCNB is the serch help

Read only

0 Likes
1,196

OK - I think it's a user education issue. The users will have to understand that they have to match the case when using this search help.

To answer your other post - I don't think there are relevant OSS notes on this. Please close one or the other (or both) thread.

Rob

Read only

0 Likes
1,196

Hi CAN U HELP ME HOW DO I PROCEED IN THIS CASE THEN? URGENT.....

Read only

Former Member
0 Likes
1,196

HI

Use TRANSLATE statement for this problem.

Ex:

Data: it_tab type c(10) value 'AeAdare'.

Translate it_tab to uppercase.

Result will be AEADARE.

Reward me if its helpful

Regards

Ravi

Read only

former_member189059
Active Contributor
0 Likes
1,196

Check this code and output

This is the output

Rm167 is matched by pattern #R#m167

rm167 is not matched by pattern #R#m167

RM167 is not matched by pattern #R#m167

rM167 is not matched by pattern #R#m167

using this code:

FORM ANY .
DATA:
  lr_text TYPE RANGE OF text40 with header line,
  lv_text1 type text40 value 'Rm167',
  lv_text2 type text40 value 'rm167',
  lv_text3 type text40 value 'RM167',
  lv_text4 type text40 value 'rM167'.
  lr_text-sign = 'I'.
  lr_text-option = 'CP'.
  lr_text-low = '#R#m167'.
  APPEND lr_text.
 
  IF lv_text1  IN lr_text.
    WRITE: / lv_text1, 'is matched by pattern', lr_text-low.
  ELSE.
    WRITE: / lv_text1, 'is not matched by pattern', lr_text-low.
  ENDIF.
  IF lv_text2  IN lr_text.
    WRITE: / lv_text2, 'is matched by pattern', lr_text-low.
  ELSE.
    WRITE: / lv_text2, 'is not matched by pattern', lr_text-low.
  ENDIF.
  IF lv_text3  IN lr_text.
    WRITE: / lv_text3, 'is matched by pattern', lr_text-low.
  ELSE.
    WRITE: / lv_text3, 'is not matched by pattern', lr_text-low.
  ENDIF.
  IF lv_text4  IN lr_text.
    WRITE: / lv_text4, 'is matched by pattern', lr_text-low.
  ELSE.
    WRITE: / lv_text4, 'is not matched by pattern', lr_text-low.
  ENDIF.
 
ENDFORM.                    " any