on 10-27-2015 4:27 PM
Hi All,
We have one scenario that is IDOC to SOAP.
In Receiver Down Stream system we are getting Special Characters.
I have attached 3 screen shots
1) IDOC screen shot
2) Adapter Engine Screen Shot
3) Down Stream System Screen Shot.
In IDOC and AE it is showing same value, But in Down Stream System it is showing Some extra Characters.
In IDOC the field name is "ORT01" and value is "SANTO ANDRÉ".
In AE the filed name is "cod_cidade" and value is "SANTO ANDRÉ".
But In Down Stream System filed name is "cidade" and value is "SANTO ANDRÉ".
Why we are getting this special characters?
What are the possible ways and how can we resolve this?
Please help me.
Thanks & Regards,
Vishnu Pallamreddy.
Hi Vishnu
I'd suggest that you check with the down stream system technical team what type of encoding does their web service expect. I'm suspecting that they are expecting ISO-8859-1 but PI by default sends UTF-8.
Once they confirm that you can try adding parameter XMBWS.XMLEncoding = iso-8859-1 in the SOAP receiver channel.
Refer to question "What character encoding is supported by the SOAP receiver adapter?" in SAP Note 856597.
Another way you can test is by downloading the AE payload and using SOAP UI to send directly to the web service. Try changing the encoding attribute in the XML header to see what happens in the receiver system.
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I mentioned, try adding that parameter or test it out using SOAP UI. That's the only way you will find out. I can only suggest as I have no access to your system to test it out.
It does not matter what language, when "talking" from computer to computer, it's the encoding that is important. Ask the other team what they are expecting.
Hi Vishnu
From the screenshot, in the XML declaration, the encoding is not specified, so by default it will be UTF-8 which is causing the problem.
Can you clarify whether the XML from the down stream you provided is before or after you added the XMBWS.XMLEncoding in the SOAP channel?
If you add the parameter correctly, the Content-Type and XML declaration should have the ISO-8859-1 mentioned as shown below:-
I'd also suggest that you try using the following feature to trace the SOAP call. It will help you troubleshoot further if required.
Rgds
Eng Swee
User | Count |
---|---|
78 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.