Error : "soap" for element "soap:Fault" is not bound.

[Former Member]

Hi Gurus,

I have created proxy(SAP CRM) to webservices(third party) scenario in ICO.

Sender channel details:

Adapter type: SOAP

Message Protocol: XI 3.0

As third party is using SOAP 1.2 , I have configured below details

Receiver channel details:

Adapter type: WS_AAE

Message Protocol: SOAP

Target URL: http://<IPAddress>/SAPAdapterService/SAPProfileService.svc?wsdl

HTTP basic authentication: User name and password

Address:

Enable WS addressing:ticked

Addressing version: http://www.w3.org/2005/08/addressing

SOAP version: 1.2

MApping:

Request/Response graphical mapping.

But when I trying to send message from SAP CRM , messages are failing in PI with below error:

Exception when executing application mapping program com/sap/xi/tf/_MM_Responsemapping_; Details: com.sap.aii.utilxi.misc.api.BaseRuntimeException; The prefix "soap" for element "soap:Fault" is not bound.

Please help me resolving this issue?

Thanks in advance ,

Let me know in case any other info is required from my end.

Regards,

Sarv

[former_member183816]

You are trying "Synchronous (Best Effort)", communication in your receiver channel. So when your receiver web service is throwing soap fault, it is trying to invoke fault message mapping, which you haven't configure in your service interface.

[Former Member]

hi Sarvjeet,

I am getting exactly the same error: soap for element soap:fault is not bound.

I am using WS_AAE.

Could you please let me know if you managed to make it working ?

If it is working:

a) how does the soap fault response you are getting from a web service looks like ( especially detail element ) ?

b) also how does external definition look like for the soap fault in PI ?

Kind regards

Agni

[former_member186851]

Hello Sarvjeet,

Something wrong in the reponse mapping.

[arunneerolil]

Sarv,

Looks like you will have to adjust the response data type.

Test the mapping independently using the response message from the third party system.

You should be identify the error once you paste it in the mapping test / tree view.

Enable the ICO logging/staging to get the details of message payload.

Arun