on 09-24-2008 7:32 PM
Hello there!
My XI scenario is as follows:
SOAPRequest-->XI--->R3 (Idoc)
The soap request contains some croatian characters which are "propperly" handled by XI. On the XI monitor tool I can see that those characters are shown propperly using UTF-8 encoding.
On the other hand, when I check the information in R3 some problematic characteres are shown as "#"
On XI transaction SM59 I can see that the RFC destination uses "HR" as logon language (croatian).
Besides, If I change the value of the error conversion indicator (error indicator="#") in that transaction, I can see in R3 that the
problematic characteres are shown with that value.
This means that the conversion error is inside XI.
How can XI possibly show the problematic characteres propperly while using XI monitoring tool and sends this problematic characteres as "#"?
What can I do to solve this issue?
Thank you very much in advance, Raú
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
I solved this issue by selecting:
SM59->Special Options->RFC Bit Options->Use found Communication Code Page
Thanks for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This may be helpful to you
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what are these problematic characters ? Are these special characters?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.