Application errors occured in ccBPM not restartable?

Question

hello experts,
We are using ccBPM for some of the integration scenarios and synchronously posting data to SAP R/3. When an BAPI returns an application error code (e.g. material locked by an user), we are unable to restart these messages from SXMB_MONI hence we have to manually edit and retransfer XML files. This is very cumbersome and error prone. We have informed the implementation partner but they are saying that application specific errors can not be restarted.
We have gone through the documentation http://help.sap.com/saphelp_nw04/helpdata/en/ea/2f053d39177608e10000000a114084/content.htm and it says :
"Application error (restart possible)
An application error occurred during message processing. For asynchronous processing, this status only occurs in the receiver system; for synchronous processing, it occurs in all systems involved."
We have also gone through the blog /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 by Shabarish Vijayakumar. We want the same result but we are using ccBPM send step to invoke a standard BAPI via RFC adapter instead of using ABAP server proxy.
Can someone please help us out? users are complaining the old R/3 LSWM uploads were much more feature rich & user friendly
thanks & regards,
Harsha.

Answer 1

Hi Uri,
thanks for the suggestion. I would assume this will require changes in the BPM. Why cant we simply catch the BAPI return code 'E' and mark the message as an application error, which is restartable?
This is a  very basic requirement and I am sure there must be a way of achieving what we want but I don't have enough knowledge on XI to do it.
Is there any place we can find a how-to guide?
thanks & regards,
Harsha.