Hi, In a IDOC --->XI(BPM)--->SOAP Sync Scenario failrure.

[Former Member]

Hi, In an IDOC ->XI(BPM)->SOAP Sync Scenario I observed recently messages are failing in SXMB_MONI with an error as:

com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://172.16.209.162/esdryrun/ContractData_Push. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)

friends, could u plz help on this.

Thanks,

satya.

[Former Member · Accepted solution]

Hello,

This indicates a configuration issue with this SOAP receiver adapter. Please check the on line help for the configuration of the SOAP adapter (the link is below). Please set the indicator in the "SOAP Action" field.

Configuring the Receiver SOAP Adapter

http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm

(Below is the extract from the link)

SOAP Action

Specify the SOAP action. The action specifies the value for the

SOAPAction in Web service messages; set the indicator.

Regards,

Sarah

[Former Member]

Hi Satya,

In SOAP action field provide the Web Serice Operation name, i gues in your case it might be 'ContractData_Push', Do not give url with host and port in the SOAP action, WSDL url or web serivice url you can provide it in Target URL, this will solve your problem.

Regards,

RK

[Former Member]

Thanks Sarah, Sreehari and RK ,

The isuue with the SOAP Action only, The client had changed SAOP Action at their end as http://172.16.209.161/esdryrun/ContractData_Push, After changing SOAP Action to http://172.16.209.162/esdryrun/ContractData_Push it worked.

Regards,

satya

[Former Member]

This is an issue with the channel configuration. You would want to verify the I/P address specified in the SOAP Action.