topic Re: Translate statement and Unicode in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872602#M367275 <HTML><HEAD></HEAD><BODY><P>TRANSLATE ... TO UPPER/LOWER CASE</P><P>TRANSLATE ... USING</P><P>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 &#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.</P><P>TRANSLATE ... CODEPAGE ...</P><P>TRANSLATE ... NUMBER FORMAT ...</P><P>The above statements are not allowed in Unicode programs.</P><P></P><P>I hope this helps</P><P></P><P>Regards</P><P>Sunil</P></BODY></HTML> Fri, 19 Jan 2007 10:02:40 GMT Former Member 2007-01-19T10:02:40Z Translate statement and Unicode https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872601#M367274 <HTML><HEAD></HEAD><BODY><P>Hi All,</P><P></P><P>Is there any impact of Unicode upgrade on Translate statement.</P><P></P><P>Will Translate field1 to upper/lower case work as it is after Unicode upgrade?</P><P></P><P>Amogh</P></BODY></HTML> Fri, 19 Jan 2007 09:43:28 GMT https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872601#M367274 Former Member 2007-01-19T09:43:28Z Re: Translate statement and Unicode https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872602#M367275 <HTML><HEAD></HEAD><BODY><P>TRANSLATE ... TO UPPER/LOWER CASE</P><P>TRANSLATE ... USING</P><P>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 &#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.</P><P>TRANSLATE ... CODEPAGE ...</P><P>TRANSLATE ... NUMBER FORMAT ...</P><P>The above statements are not allowed in Unicode programs.</P><P></P><P>I hope this helps</P><P></P><P>Regards</P><P>Sunil</P></BODY></HTML> Fri, 19 Jan 2007 10:02:40 GMT https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872602#M367275 Former Member 2007-01-19T10:02:40Z Re: Translate statement and Unicode https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872603#M367276 <HTML><HEAD></HEAD><BODY><P>TRANSLATE ... TO UPPER/LOWER CASE</P><P>TRANSLATE ... USING</P><P>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 &#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.</P><P>TRANSLATE ... CODEPAGE ...</P><P>TRANSLATE ... NUMBER FORMAT ...</P><P>The above statements are not allowed in Unicode programs.</P><P></P><P>I hope this helps</P><P>Regards</P><P>Sunil</P></BODY></HTML> Fri, 19 Jan 2007 10:03:39 GMT https://community.sap.com/t5/application-development-and-automation-discussions/translate-statement-and-unicode/m-p/1872603#M367276 Former Member 2007-01-19T10:03:39Z