cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP adapter fault

Former Member
0 Kudos

Hello,

I am trying to configure a simple scenarion:

http client > xi > w.s

The w.s was generated from a function module.

In sxmb_moni I receive the followin error:

<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>soap fault: Operation not supported</SAP:AdditionalText>

Also in the response payload I receive the following:

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

- <!-- Call Adapter

-->

- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<faultcode>SOAP:Client</faultcode>

<faultstring>Operation not supported</faultstring>

</SOAP:Fault>

The payload I am trying to send to the w.s is:

<LookForNewOrders>

<Refnumber>4</Refnumber>

<CustomerID>444</CustomerID>

<Material>dd</Material>

<Quantity>1</Quantity>

<Status>N</Status>

</LookForNewOrders>

The target url I put in the communication channel of the soap adapter is:

http://hp5474.gre.hp.com:8000/sap/bc/srt/rfc/sap/IF_Orders_Insert_1?sap-client=700

How do I go on from here?

Thanks

Boaz

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_grube
Active Contributor
0 Kudos

Hi Boaz,

when you create a web service from an inbound proxy, make sure, that the proxy code is implemented and active. Look in transaction code SICF, if the service <i>sap/bc/srt/rfc/sap/IF_Orders_Insert_1</i> is active. Check if the client is correct.

Hope that helps.

Stefan

Former Member
0 Kudos

Hi Boaz,

The Soap-Xml message which Xi is passing to WebService might not be acceptable to WebService.

Therefore you try to test your WebService using SOAP client. If you dont have Soap client you can download it from SAP site. Test ur WebService there and if its working fine then Compare the Request Schema of ur Soap client to that of the payload after message mapping step in SXMB_MONI.

Then you can change ur mapping program accordingly.

Regards,

Yomesh