cancel
Showing results for 
Search instead for 
Did you mean: 

Encoding issues

Former Member
0 Kudos

Hi all,

we have implemented RFC -> XI -> SOAP scenario, connection works fine. But we have a problem with local characters (czech language). When we are sending to an external system strings containing local characters, third party complains, that local characters are not transferred (encoded) correctly (encoding issue???) ... outgoing encoding should be UTF-8 (default charset). When I look at send messages in SXMB_MONI, all seems to be fine (local characters are displayed correctly) ...

Can any help me how could I find out, where is a problem? Is there any other way how to see, how messages were processed by SOAP adapter and how they looked like, when they were sent to the external system? Or SXMB_MONI is the only tool, where to see processed messages?

Are there any special rules required to be met to have proper unicode connection between SAP R/3 and SAP XI via RFC?

Thank you very much for any help which could move me on ... I really do not know where should be the problem

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_grube
Active Contributor
0 Kudos

The SOAP adapter uses UTF-8, so the payload of the message should be the same as in sxmb_moni.

If the receiver does not understand UTF-8, you can put the parameter XMBWS.XMLEncoding for the SOAP adapter standard bean in the SOAP adapter channel under modules.

See also note 856597.

Ask, which codepage the receiver accepts. It could be for example ISO-8859-2 (eastern europe).

Regards

Stefan

Former Member
0 Kudos

do the following on the sender side... i think this is problem on the receiver side...let's us know..

Former Member
0 Kudos

Anand,

I was trying to configure RFC destination in SM59, but I am not able to setup flag "Use Found Communication Code Page", I always get a message "Your selection is restricted" ... I tried to combine this flag with the others, as described in long text, but nothing helped

Stefan,

I know about the possibility to define XMBWS.XMLEncoding for the SOAP adapter standard bean in the SOAP adapter channel under modules. I tried it, no change ... External system should not have a problem with UTF-8. What is strange, that in SXMB_MONI the sent mesage has in header <...encoding="UTF-8">. But when i right-click on the message and select "View source code", in HEX mode I can see, that the encoding is in fact UTF-16 ... is it normal???

stefan_grube
Active Contributor
0 Kudos

> What is strange, that in SXMB_MONI the sent mesage has in header <...encoding="UTF-8">. But when i right-click on the message and select "View source code", in HEX mode I can see, that the encoding is in fact UTF-16 ... is it normal?

That is not possible. If you have UTF-16 and the XML declaration states UTF-8, then every second char is displayed as box.

It might happen during download. And: Every character is infected, not only the czech ones.

Does the receiver have a trace where you can look at the message, how it arrives? If the characters are displayed correctly in SXMB_MONI, then there is no issue in the RFC connection.

Regards

Stefan