cancel
Showing results for 
Search instead for 
Did you mean: 

SAP CPI Odata adapter error 'WstxUnexpectedCharException'

Muska18
Discoverer
0 Kudos

Hello SAPians,

While trying to connect with S4Hana Public cloud through Sales Order Odata v2 API , I'm getting the WstxUnexpectedCharException error ,attached the image below.

Muska18_0-1711702116993.png

Our odata API url - https://XXXX/sap/opu/odata/sap/API_SALES_ORDER_SRV/A_SalesOrder.

Muska18_1-1711702290221.png

I am stuck here now for a few days trying, googling, checking help documentation, but there is no clear description/explanation available.

Can someone help me here . 

Regards,

Muskan

SAP Integration Suite  OData API  SAP BTP, ABAP environment SAP S/4HANA Public Cloud 

Ryan-Crosby
Active Contributor
0 Kudos
Check the logs to see the URL that is being invoked because it indicates an incorrect & character at position 128.

Accepted Solutions (0)

Answers (3)

Answers (3)

Dinu
Contributor
0 Kudos

You have to create a communication user and use that for the integration. You can find several resources in the community and in other SAP assets for this.

Dinu
Contributor
0 Kudos

You are seeing this issue because authentication is failing. The server is responding with a page to login. The adapter is failing to parse the html page.

Solution is to fix authentication. 

Muska18
Discoverer
0 Kudos

Thank you for the reply

Muska18
Discoverer
0 Kudos

Hi Dinu

We are passing the required authentications, you could see that in Screenshot below

Muska18_1-1711951651177.png

we are getting the same unexpectedcharacterexception error

Muska18_2-1711951696311.png

but when we are using local emdx file it is accepting the Connection, but the iflow gets fail in the triggering throwing same error.

Could you highlight if we are doing something wrong??

 

Dinu
Contributor
0 Kudos
You have to create a communication user and use that for the integration. You can find several resources in the community and in other SAP assets for this.
carlosrpereira
Explorer
0 Kudos

One of the your query parameters was not preceded by "&", you will need check your endoint call to find it.