Skip to Content
May 14, 2018 at 10:38 AM

How to identify what the actual error is when a new workflow doesn't work when tested in SWDD?

2209 Views Last edit May 14, 2018 at 11:02 AM 2 rev

Hi Folks,

a while ago Mike Pokraka was kind enough to walk me through an example about how to set up a simple workflow to prompt (new) developers to read our development guidelines. Even though I don't know much about Workflow and ABAP OO, with his help I managed to get this to work in a sandbox system.

Last week I finally started to retrace the steps outlined in Mike's chapter in the Workflow book and "copied" the workflow definition and needed classes/methods from the sandbox-system into the actual development system. Everything generated okay but when I test the workflow from within SWDD, I'm getting several error messages instead of the pop-up message.

From SWIA_DIAG (with message ID/number):

  • Error when creating a work item - (SWP044)
  • Error when creating a component of type 'Step' - (SWP087)
  • Error when processing node '0000000004' (ParForEach index 000000) - (SWP088)
  • Error when starting work item 000000600098 - (SWP085)
  • Deadline determination failed - (SWF_RUN539)
  • Work item 000000600098: Object FLOWITEM method EXECUTE cannot be executed - (WL821)

Most of them don't have a long description and even if there is one, I have a hard time with a) interpreting what it means and b) identifying which of them is the actual "culprit" for the string of messages. The same goes for the search results I found when looking for mentions of the various messages.

Here is how the step history for the failed test looks like:

I already compared the workflow- and task-definitions as well as the classes and methods between the sandbox and the development system and just cannot see a difference. So, perhaps I'm just not interpreting the errors correctly and/or I'm looking in the wrong place(s) for the underlying issue.

Not sure if this is perhaps related but when I defined the task as a standard task in the dev-system, this message was displayed when a customizing transport was created:

"Check the object list of the order (inconsistency in SOBJ)" - (5A378)

I didn't get this message in the sandbox system, so I'm not sure why it got triggered in the dev-system and we (meaning our basis team) haven't yet determined if the indicated report RHSOBJCH can be safely run in the system and what the consequences of that might be as far as transports into the subsequent systems goes.

Can anybody point me in the right direction?

Thanks much and Cheers