Skip to Content
avatar image
Former Member

ABAP.DYNAMIC_CALL_ERROR in soap ui 4.5.0 while testing

Hi all,

I have developed a soap-proxy interface. When i test it in ESR, ID(test configuration) and RWB (send test message from RWB) its working fine and reaching the target system.

But when i trigger the same usingSOAP UI 4.5 then it aborts ongoing request (red colour button blinks) and it says the following error.

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

   <SOAP:Body>

      <SOAP:Fault>

         <faultcode>SOAP:Server</faultcode>

         <faultstring>System Error</faultstring>

         <detail>

            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

               <context/>

               <code>ABAP.DYNAMIC_CALL_FAILURE</code>

               <text/>

            </s:SystemError>

         </detail>

      </SOAP:Fault>

   </SOAP:Body>

</SOAP:Envelope>

Later when i had a check in SXMB_MONI, it shows system error and restart not possible.

Plz suggest me your opinion on the same

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 30, 2013 at 05:31 AM

    Hello,

    I have developed a soap-proxy interface. When i test it in ESR, ID(test configuration) and RWB (send test message from RWB) its working fine and reaching the target system.

    We need more information.

    Are you sending your payload in RWB with a SOAP Envelope?

    Are you using Do Not Use SOAP Envelope?

    Regards,

    Mark

    Add comment
    10|10000 characters needed characters exceeded

    • This seems synchronous call and seeing abap dynamic call failure. So I think some processing error in abap proxy logic side. So I might want you to test the abap proxy part within ECC first. See what error do you get ... This could be based on the data u send via soap sender.  SOAPUI might throw error while retrieving response back. First confirm with the same data within ECC testing abap proxy first.