2006 Sep 05 9:25 AM
When I use translate statement in my report of course it is executing well..when I checked extended syntax check it is giving Dangerous use of TRANSLATE in a multilingual system...can anyone suggest any other method for it ..
2006 Sep 05 9:31 AM
use the below.
SET LOCALE LANGUAGE sy-langu.
TRANSLATE wl_werks TO UPPER CASE.
2006 Sep 05 9:29 AM
REPLACE by Pattern
Replaces strings in fields with other strings using a pattern.
Syntax
REPLACE [ FIRST OCCURENCE OF | ALL OCCURENCES OF ] <old>
IN [ SECTION OFFSET <off> LENGTH <len> OF ] <text> WITH <new>
[IGNORING CASE|RESPECTING CASE]
[IN BYTE MODE|IN CHARACTER MODE]
[REPLACEMENT COUNT <c>]
[REPLACEMENT OFFSET <r>]
[REPLACEMENT LENGTH <l>].
2006 Sep 05 9:30 AM
Hi,
The warning is only applicable if you are using TRANSLATE on the content which could be of any language apart from English.
If the variable for which you are using TRANSLATE will only hold ENGLISH values, then please ignore the warning.
Best regards,
Prashant
2006 Sep 05 9:31 AM
use the below.
SET LOCALE LANGUAGE sy-langu.
TRANSLATE wl_werks TO UPPER CASE.
2006 Sep 05 9:35 AM
can u explain what is the use of " SET LOCALE LANGUAGE sy-langu."
2006 Sep 05 10:07 AM
SET LOCALE LANGUAGE sy-langu.
it will run accordingly to the system language...
if ur logon languae is other than 'EN'...it works perfectly for those languages also...
Ramesh
2006 Sep 05 10:14 AM
Is it just like global declaration??? can i use it inside the loop?? or in the global/local declaration???
2006 Sep 05 10:02 AM
Before translating to upper or lower case letters, the system has to be set to the current text environment.
This statement is used for this purpose
2006 Sep 05 10:25 AM
Hi,
You can use locally in your form
set local language sy-langu
translate ---
Regards
Amole
2006 Sep 05 10:28 AM
hi,
You can set the language even inside a loop.
As soon as you set the language, it applies to the program.
It is better to set before the loop starts, instead of setting it for every loop pass.
Regards,
Sailaja.