cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Fault not detected by ICO (ABAP proxy to SOAP java only scenario)

Former Member
0 Kudos

Hi there,

We are experiencing an issue with a synchronous java-only scenario between an ABAP Proxy and a SOAP receiver.

When we receive a SOAP fault from the SOAP receiver, we get an error like this on the response side:

06.08.2012 16:36:40.977ErrorTransmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: No matching mapping found.
06.08.2012 16:36:40.980ErrorThe message status was set to FAIL.
06.08.2012 16:36:40.981ErrorReturning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: No matching mapping found

When we test the same scenario but then using a traditional configuration via the ABAP stack, the SOAP fault is properly interpreted and passed to the ABAP proxy calling the webservice. In both cases we use the same SOAP receiver communication channel.

We found the following SAP note (1556428) which exactly describes the issue but unfortunately the problem persists also after having applied it.

We are running PI 7.11 SP7

Any other ideas what could be causing the problem with this ICO java only scenario?

Accepted Solutions (0)

Answers (1)

Answers (1)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

You might want to raise an OSS note or talk to SAP. Looks like still Soap sender using xi mode for abap proxy does not seem work as sap note described.