<?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: Replacement code for Translate statement in latest version in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393174#M532379</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt; TRANSLATE ... TO UPPER/LOWER CASE&lt;/P&gt;&lt;P&gt;TRANSLATE ... USING&lt;/P&gt;&lt;P&gt;The arguments of these instructions must be single fields of type C, N, D, T or STRING or purely character-type structures. There is a syntax or runtime error if arguments of a different type are passed. A subset of this function is provided with the addition IN BYTE MODE for processing byte strings &amp;#150; that is, operands of type X or XSTRING. A statement such as CONCATENATE a x b INTO c is thus no longer possible when a, b, and c are all character-type, but x is of type X.&lt;/P&gt;&lt;P&gt;TRANSLATE ... CODEPAGE ...&lt;/P&gt;&lt;P&gt;TRANSLATE ... NUMBER FORMAT ...&lt;/P&gt;&lt;P&gt;The above statements are not allowed in Unicode programs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jun 2007 09:14:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-18T09:14:15Z</dc:date>
    <item>
      <title>Replacement code for Translate statement in latest version</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393172#M532377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Replacement code for&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES XXXX  USING &amp;lt;r&amp;gt; LIKE &amp;lt;r&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSLATE &amp;lt;r&amp;gt;-&amp;lt;fieldname&amp;gt; TO UPPER CASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;r&amp;gt; is a structure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 07:58:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393172#M532377</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-18T07:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement code for Translate statement in latest version</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393173#M532378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sample code  in the latest version ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA text TYPE string. 
text = `Careful with that Axe, Eugene`. 
TRANSLATE text TO UPPER CASE. 
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 09:08:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393173#M532378</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-18T09:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: Replacement code for Translate statement in latest version</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393174#M532379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt; TRANSLATE ... TO UPPER/LOWER CASE&lt;/P&gt;&lt;P&gt;TRANSLATE ... USING&lt;/P&gt;&lt;P&gt;The arguments of these instructions must be single fields of type C, N, D, T or STRING or purely character-type structures. There is a syntax or runtime error if arguments of a different type are passed. A subset of this function is provided with the addition IN BYTE MODE for processing byte strings &amp;#150; that is, operands of type X or XSTRING. A statement such as CONCATENATE a x b INTO c is thus no longer possible when a, b, and c are all character-type, but x is of type X.&lt;/P&gt;&lt;P&gt;TRANSLATE ... CODEPAGE ...&lt;/P&gt;&lt;P&gt;TRANSLATE ... NUMBER FORMAT ...&lt;/P&gt;&lt;P&gt;The above statements are not allowed in Unicode programs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2007 09:14:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replacement-code-for-translate-statement-in-latest-version/m-p/2393174#M532379</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-18T09:14:15Z</dc:date>
    </item>
  </channel>
</rss>

