cancel
Showing results for 
Search instead for 
Did you mean: 

XI, unable to receive SOAP response message

Former Member
0 Kudos

Hi dear experts,

I have scenario Proxy -> XI -> SOAP (through https)

I am able to send Soap message to external system, where message is correctly processed within few seconds,

but I am not able to receive regular response message.

Instead, I am getting following response:

Do you have any idea why?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

  <SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: A server error occurred</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

   </SAP:Error>

Accepted Solutions (0)

Answers (2)

Answers (2)

vivek_vishal
Advisor
Advisor
0 Kudos

Hi Marek,

On an initial insight, this looks like additional soap headers from the External System in the response/acknowledgement message. The External system, if not an SAP system can shoot additional SOAP headers that may be alien to an SAP system -In this case your SAP PI system.

You could do the following.

1. Switch of these additional SOAP headers on the external systems. Provide the External Party a sample SOAP message from the SAP PI which can be analyzed by the external party and used to send the appropriate content to the PI system.

2. Write a Java mapping internally in the PI system that can map this additional header fields to the appropriate fields in the SOAP Message/Header understandable to an SAP PI system.

Hope that helps.

BR, Vivek

Former Member
0 Kudos

Hello,

still facing this the same problem.. (SSL Https synchronous communication from XI to ExtSystem)

Message from XI is successfully passing into External System where is processed.

But when response is coming back, is not reaching XI, but is returning back to webservice of external system.

Response that is External system trying to send back to XI (response in synchronous message)

  <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<invoiceResponse xmlns="*************************">

<MESSAGE>Invoice 111007076733 saved</MESSAGE>

</invoiceResponse>

</soap:Body>

</soap:Envelope>

But this is coming back to them (don't know why.. they just send response to my message)

<?xml version='1.0' encoding='utf-8'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>

<SOAP:Header/>

<SOAP:Body>

<invoiceResponse xmlns='****************************' xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'>

  <MESSAGE>Invoice 111007076733 saved</MESSAGE>

</invoiceResponse>

</SOAP:Body>

</SOAP:Envelope>

and of course webservice can't process this message and return fault message.. and this one is reaching XI without complications..

  <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<soap:Fault>

<faultcode>soap:Client</faultcode>

<faultstring>A server error occurred</faultstring>

</soap:Fault>

</soap:Body>

</soap:Envelope>

Could it be certification issue? or proxy? firewall?
Message goes out without compliaction, just with returning message there seems to be a problem.

But message looks to be valid.. And is synchronous channel, so it should come back with the same way. Any idea?

Kind regards,

Marek

Former Member
0 Kudos

Hi,

We often face these kind of issues.

Share the input payload ,configured url ,error message screen shot to target system folks .

Ask them to check the above ( url ,message (they will have test suite to test a message)) .

Regards

Venkat