Skip to Content

Issue with CX_BO_ERROR Messages Showing up in Workflow Logs

Feb 22 at 05:23 PM


avatar image

We have a custom workflow process which has tasks linked to ABAP Objects class methods. Within these methods, we've defined a custom exception class that inherits from CX_BO_ERROR to capture process-specific exceptions. Whenever we test the methods by themselves (e.g. in the test tool), the exception class shows the proper message as expected. However, when the same exception is raised in a workflow process, the text that shows up is a generic SY/530 - An exception was raised. Has anyone seen that before? This is a pretty basic setup, so I can't imagine where that message is coming from.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Mike Pokraka Feb 23 at 11:56 AM

This should work out the box, there’s even examples in “The Book”. Are you using text IDs? If not, try it and see if it works.

RAISE EXCEPTION TYPE zcx_late_for_work
      EXPORTING textid = zcx_late_for_work=>dog_ate_alarm_clock.

Or try the MESSAGE addition to RAISE EXCEPTION, I haven't used it with WF so don’t know if it works.

If it works with a text ID, I’d consider it a bug worth reporting to OSS if you have the time. I would expect it to revert to the default text if none is specified (assuming you have defined one?).

10 |10000 characters needed characters left characters exceeded
Anjan Paul Feb 23 at 09:03 AM


I am not sure, but it might possible another unexpected exception raised before your custom exception. Please share some screenshots.


10 |10000 characters needed characters left characters exceeded