on 12-22-2005 6:52 AM
Hi,
we are calling an RFC synchronously from BPM. This is a standard BAPI, that does not have any RFC exception message (BAPI_IPAK_START and BAPI_ISREQUEST_GETSTATUS). We are only able to catch system errors, since no RFC exception message is avaiable for which we could define a different exception branch.
If an error happens in the RFC, an application error is thrown, which is not catched in the exception branch defined to handle the system error. After the application error, the process simply terminates- that's it.
Why is an application error not catched as system error? Is there any way to catch an application error and let the business process continue?
Your help will be rewarded,
Volker
Hi Volker,
a BAPI does not throw any exception, therefore you cannot catch any.
- You could write a wrapper RFC around the BAPI which interprets the RETURN structure and throws exception in case of an error.
- You could have a fork in the BPM depending of the entries in RETURN.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.