Skip to Content
avatar image
Former Member

How to catch SAP application errors in BPM.


I have a IDOC to Soap Sync Scenario where I send the message to a Webservice. I have used a BPM since we need to catch the resposne of this message and map it to a RFC. For ex if I get a success resposne I need to map success if not than I need to catch the error and map it to the RFC. Now here in some cases like if the target system (webservice) is down than XI raises a sap application error:

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

- <!-- Inbound Message


-" xmlns:SOAP="" SOAP:mustUnderstand="1">



<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText> Connection refused (errno:239)</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />



Normally XI stops the process in these cases and does not proceed to the next step but I need to catch this message and map the content in the AdditionalText to the target RFC. Can anyone let me know how to catch this SAP Application Error in BPM and map it to the RFC.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Nov 19, 2008 at 09:06 PM


    Define an exception in your ccBPM (step) and then handle it.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      HI Bhargav

      Basically after getting the fault message response you map it to trigger any exception. This can trigger the BPM to proceed furthur. More over if this doesnt work then you can write ABAP report to trigger the Workflow for some condition. Now when you get this fault message let the report based on the conditoon you set, trigger the BPM again to move the message furthur.

      Give it a try