Troubleshooting SOAP Call with ABAP Client Proxy

Question

Hello,
we want to make a synchronous call to a web service from ABAP via HTTP / SOAP. The third party system provides a WSDL which we have used to create a client proxy in ABAP.
The request call works fine, but we do not get any SOAP response.
The question now is which monitoring / debugging capabilties are recommended on the SAP system to track down the problem? Which transactions and monitoring functionalities should I use?
Thank you very much for your advise!
Edited by: Florian G. on Jun 6, 2010 2:47 PM

Answer 1

Hi Prasad,
Here is an example of each one... notice the difference between the Username elements in each of  the requests:
qualified -
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://somenamespace">
   <soapenv:Header/>
   <soapenv:Body>
      <ver:GetUserRequest>
         <ver:IdmRequestContext>
            <ver:UserName></ver:UserName>
         </ver:IdmRequestContext>
      </ver:GetUserRequest>
   </soapenv:Body>
</soapenv:Envelope>
unqualified -
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://somenamespace">
   <soapenv:Header/>
   <soapenv:Body>
      <ver:GetUserRequest>
         <ver:IdmRequestContext>
            <UserName></UserName>
         </ver:IdmRequestContext>
      </ver:GetUserRequest>
   </soapenv:Body>
</soapenv:Envelope>
If you have the option of the WSDL definition changing that attribute to unqualified then it should start working immediately.  If that is not an option then your ABAP mapping needs to handle the namespace insertion into the XML.  I achieved this in my requirement by using a graphical mapping instead because I imported the WSDL as an external definition and mapped my proxy 1:1 to each element in the external definition.
Regards,
Ryan Crosby