RFC Exception handling in BPM

[Former Member]

Hi All,

I currently have a scenario where I receive an IDoc, then need to make an RFC call to another R/3 system to get some additional data, and then transform and send the resulting message out to another system. There is a possible case where the R/3 system will send back a fault message with some meaningful text which we would like to map to a Status IDoc to send back to the source system. The problem is, I can't seem to find a way to be able to use the fault message in a map in the BPM.

Is this a limitation of XI, or is there some way to get this fault message into the BPM?

[Shabarish_Nair]

do you see a error or fault message for the RFC once you have imported it to XI along with the request and response structures?

you can try using that fault structure in your mapping.

[Former Member]

Yes, the fault message is available, however I need to capture the response and use it in a transformation step in the exception branch of my BPM. Unfortunately, I can't seem to define a message interface for the fault message.

[Former Member]

Hi All,

I'm still looking for a solution here, or a confirmation that it is a limitation of XI. Thanks!

[Shabarish_Nair]

you will need to introduce a transformation step that captures the fault also

some pointers can be found here - /people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

[Former Member]

Yes, I have the fault message mapped and it is allowing me to go into the exception branch in my BPM. However, I am looking to take the detail from that fault message and create a Status IDoc to send back to the the source R/3 system. I read through the comments section of that blog and I saw a couple that indicated that this is not possible. Has this functionality been added since the writing of that blog in 2007?

[former_member200962]

Fault message propagation still functions the same for BPM....now instead of populating it as a Fault message can you ask the end system to populate the error (if any) as a response....may be the response RFC will be required to have the error structure.

Now in BPM decide whether this is an error....if yes then create the IDOC....if not then discard the message.

In one of my project requirements we had a similar req wherein there was proxy at receiving end....we updated the proxy (ASYNC) and if any error then another proxy would be populated giving error details (in case there was an error)....both the flows ASYNC....once we got the details we would do further processing.

Regards,

Abhishek.