topic Re: Unicode to Non-Unicode in Application Development and Automation Discussions

Unicode to Non-Unicode

Former Member — Wed, 04 Jan 2006 06:34:29 GMT

I'm working on a non-unicode system and trying to read unicode data (Arabic) through RFCs in character based parameters ... The problem I'm facing now is that I'm getting the characters as (###) .. Is there any way to convert the returned unicode data to non-unicode?

Thanks,

F.D.

Re: Unicode to Non-Unicode

Former Member — Wed, 04 Jan 2006 07:52:24 GMT

Hi,

Arabic codes are unicode! then you'r non unicode system will not handle it!

Maybe create you're own conversion method ?

cheerz

Re: Unicode to Non-Unicode

Former Member — Wed, 04 Jan 2006 08:37:38 GMT

Hi FD,

<b>RFC from a Unicode System into a Non-Unicode System</b>

The following errors may occur:

1. The non-Unicode system returns incorrect results data.

2. A text language is unknown.

3. The Unicode system sends characters that cannot be converted into the required non-Unicode code page.

4. The receiver buffer of the non-Unicode system overruns.

In the calling system, the reaction to conversion errors can be configured separately for each destination.

See transaction SM59 Defining Remote Destinations.

For the system being called, a conversion error is not visible. The calling Unicode system identifies errors in the input data before it triggers an action on the called page; the calling Unicode system only identifies errors in the output data if the called context has already been disconnected.

For further information refer below links.

http://help.sap.com/saphelp_nw04/helpdata/en/86/e4e5a89461cd4587a71c52e927f2fc/frameset.htm

/people/thomas.jung3/blog/2004/06/24/bsp-150-a-developer146s-journal-part-v-xml-for-rfcs

In the above web blog you can find info about serialization from unicode to non unicode data.

Dont forget to reward pts if it helps ;>)

Regards,

Rakesh.

Re: Unicode to Non-Unicode

Former Member — Wed, 04 Jan 2006 10:06:57 GMT

Thank you very much for your assistance Rakesh and Stephan. To be clearer in my problem, I'm required to write an Arabic Crystal report from the data being fed by RFC calls (keeping in mind that I'm working in a non-unicode system). I was thinking that the RFC can have the parameters in type Hexa (to ensure that the data doesn't get corrupted). From my side I can receive it in Hexa as well and then transfer the data with an interface object or so to write the report in Arabic.

I know it sounds very complicated that makes the upgrading to unicode easier! But please if anyone has any idea it would be much appreciated.

Thanks.