Control characters/ ASCII code/ non printable characters in response of an Synchronous SOAP call.

[Former Member]

Hello!

I have a simple pass through synchronous scenario wherein standard enterprise service have been used.

It is a SOAP-->PI-->ECC (Proxy)  synchronous call.

The response XML of few Sales orders contain characters like &#x1A which are un-parseable by UTF-8 encoding.

Hence, I am getting an error: "Character reference "&#x1A" is an invalid XML character".

I tried to changed the Endpoint in SOAP UI by appending the attribute "&xmlenc=iso-8859-1" , but the error still persists:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=TPBS_XX&receiverParty=&rece...

Please suggest!

Thanks,

Indu Khurana.

[RaghuVamseedhar]

Indu,

Reason for this error: Bad data in SAP ECC, sales order tables.

Option 1 (recommended): Request SAP functional team to fix the data (delete non printable characters) in SAP for those particular sales orders.

Option 2:

[Former Member]

Hi Raghu

Yes, the data in sap tables is the issue, but the data is being updated by two or three different interfaces at runtime.

[Former Member]

Hi Indu

Where are u getting the error ? is it in SXMB_MONI?

The response mapping is failing for the &#x1A ?

Looks like your abap program for proxy is returning the invalid characters. Try to change the encoding in abap program.

Character encoding conversion - ABAP Development - SCN Wiki

Thanks,

Indrajit

[Former Member]

Hi Indrajit,

It is PI7.3 single stack. I'm getting error in SOAP UI while executing the SOAP call.

No mapping has been used for this scenario.

I tried by changing the encoding in end point by appending the attribute for encoding as "&xmlenc=iso-8859-1but still it is not working.

Thanks,

Indu K.