Issue with chinese character in Idoc for R/3 4.6C

[sunilchandra007]

Hi,

We are working on a file to idoc scenario where in some of the fields coming is having chinese characters. In R/3, we noticed that the chinese characters got replaced with # and after the particular field having chinese characters, the other fields got shifed by some characters to next fields. The systems involved are PI 7.0 and R/3 4.6C.

Please let me know if you have come across such issues having multi language data with content shift in idoc fields.

Thanks,

Sunil Chandra

[markangelo_dihiansan · Accepted solution]

Hello,

Try to check the unicode settings of your SM59 type 3 connection to XI. The data shift might be happening because you are using non-unicode in R3. Now as for the Chinese characters, this could be related to your encoding type (try UTF-16).

Hope this helps,

Mark

Edited by: Mark Dihiansan on Mar 4, 2011 2:43 AM

[Former Member]

make the system unicode - go to SM59 - ABAP connection and select tab - MDMP & Unicode and select Comm type Unicode.

chirag

[Former Member]

the 4.6c is not a unicode system. you need a new rfc destination that has the log on language code ZH. check since you might also need to fix in the bit options in the rfc destination.

[Former Member]

HI,

this can be handling vai unicode settings at the RFC destination type used...

i.e you need to enable the unicode settings at the RFC destination created for both the systems..

HTH

Rajesh

[andreas_dahl]

Hi,

please look at the SAP note 1531714 which desribes the typical problems with sending chinese characters from

PI IDoc adapter to an none unicode system.

Most of the errors are:

- in the destination the logon language is not configured

- receiver system is a Unicode/ non unicode system => this must be correctly configured

- rfc-bit option not correctly set, described in the note, if several languages with different codepages

are installed on receiver system (non unicode system).

Kind regards,

Andreas

[deepak_shah]

Hi Sunil,

please check below thread

Regards,

Deepak