<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Request to let me know replacement command for the Translate command. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436490#M208036</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;U can use REPLACE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IF u can give the details, i can be more specific.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Aarthi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Jul 2006 11:46:25 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-07-24T11:46:25Z</dc:date>
    <item>
      <title>Request to let me know replacement command for the Translate command.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436489#M208035</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Code Inspector show that Translate command is obsolete. please let me know the alternate command to be used for the Translate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Madhuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2006 11:43:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436489#M208035</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-24T11:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: Request to let me know replacement command for the Translate command.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436490#M208036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;U can use REPLACE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IF u can give the details, i can be more specific.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Aarthi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2006 11:46:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436490#M208036</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-24T11:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Request to let me know replacement command for the Translate command.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436491#M208037</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no alternative command for translate , use set language before using the translate command .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Appana&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE c TO UPPER/LOWER CASE: Additional Information &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Variants: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE c TO UPPER CASE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE c TO LOWER CASE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way in which the TRANSLATE statement works depends on the R/3 logon language. In general, users log on to the R/3 System in the same language as that in which the data they want to edit was created. Logging on in the wrong language causes loss of data, unless a conversion has been defined to deal with a different language environment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if German umlauts are processed in a Russian environment, the TRANSLATE statement returns a '|' for an 'ö' and a '¶' for a 'Ö'. Such discrepancies occur in particular: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the wrong language environment has been set inSET LOCALE LANGUAGE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the user edits data that was not written in the logon language (without using SET LOCALE LANGUAGE) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If, for example, the data to be converted is stored in a structure struwith the language key languand the text field text, then you can work round the problem in one of two ways: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF stru, &lt;/P&gt;&lt;P&gt;        langu TYPE sy-langu, &lt;/P&gt;&lt;P&gt;        text  TYPE sy-xcode, &lt;/P&gt;&lt;P&gt;      END   OF stru. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SET LOCALE LANGUAGE stru-langu. &lt;/P&gt;&lt;P&gt;TRANSLATE stru-text TO UPPER CASE. &lt;/P&gt;&lt;P&gt;SET LOCALE LANGUAGE SPACE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This solution ensures that every conversion is made in the appropriate language. If struis an internal table, it should be sorted beforehand, to reduce the number of times the system switches between languages. Depending on the table's range, this can substantially reduce processing time, since SET LOCALE LANGUAGE has a long processing time. The runtime is similar to the runtime for SQL statements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;IF stru-langu = sy-langu. &lt;/P&gt;&lt;P&gt;  TRANSLATE stru-text TO UPPER CASE. &lt;/P&gt;&lt;P&gt;ELSE. &lt;/P&gt;&lt;P&gt;  .... &lt;/P&gt;&lt;P&gt;ENDIF. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above solution ensures that only texts created in the logon language are edited. If you want, you can bundle all other text lines in another internal table using COLLECT and then convert them using the first solution above. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note &lt;/P&gt;&lt;P&gt;It is important to reset the language explicitly using SPACE, since SET LOCALE LANGUAGE also changes the system field sy-langu. Note also that a language key may not be meaningful, or a language may not be installed correctly, or you may not be able to edit data from a specific application server. In these special circumstances, the following function modules can be used: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCP_MIXED_LANGUAGES_1_INIT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCP_MIXED_LANGUAGES_1_SWITCH &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCP_MIXED_LANGUAGES_1_NORMAL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCP_MIXED_LANGUAGES_1_FINISH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jul 2006 11:52:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/request-to-let-me-know-replacement-command-for-the-translate-command/m-p/1436491#M208037</guid>
      <dc:creator>Laxmana_Appana_</dc:creator>
      <dc:date>2006-07-24T11:52:25Z</dc:date>
    </item>
  </channel>
</rss>

