Best practice to manage error

[Former Member]

Hi all,

i would like to know how do you manage in general errors in Workflow ?

For example, in my process, a user must take a decision : Accepted or Rejected. If Accepted is chosen a background task is launched, but if it is in error, i would like to launch again.

Thanks for help.

[KKilhavn · Accepted solution]

Where I work we perform the Look_for_errors subroutine (form).

If nothing is returned by it everything is fine.

If something is returned we loop (ForEach) and call the Handle_error subroutine (form).

This is a quite generic form, trying to determine what is wrong before trying to fix the problem. Often it is enough to try a "Restart_workflow" call, and/or a "Reevaluate_agents" call.

[Former Member · Accepted solution]

Hi,

thanks to answer.

Look_for_errors subroutine and Handle_error subroutine is a part of a specific BOR ?

Other problem, imagine in your workflow there is a background task named 'MODIFYPID' to modify an accounting document, but this document is already blocked by an other user. I would like that when the other user frees the document the taks 'MODIFYPID' can run.

Well, my impression is that it's difficult to manage workflow error's.

Edited by: CECG on Jan 21, 2008 3:47 PM

[KKilhavn · Accepted solution]

Errors are often not very well handled, I must admit that.

You can define exceptions for your BOR Object methods, and these can be of different types. If you define e.g. a temporary error for a background method and raise this exception the system will retry the method again as per customizing settings. In your case, this would be a good solution. After a number of retries (also customizing) the workflow runtime engine gives up and flags the work item as having an error. Just go to the exceptions definition for a method and check the documentation. I think it is fairly well described.

[Former Member · Accepted solution]

Hello,

we are just migrating from 4.6c to ECC 6.0 and I have a couple of workflows to adopt.

For background steps I defined in the corresponding BOR methods an exception to be fired when no result is available (e.g. no mail address available). Normally, I defined them as temporary errors.

I activated in the WI outcome section the line for this exception and so the workflow processed this branch when the exception appeared. It worked fine.

Now, in ECC 6.0, the same workflow get stuck in the WI. The exception is fired (I can see it in the log as "Error message"), but the WI is still in status "in process". It doesn't continue with the error outcome branch.

Is this a new logic in ECC 6.0? Do you have any idea what to do? I used this logic some dozent times in different methods and workflows and it gives me a headache if I have to change everything ...

Thank you!

Best regards,

Thomas

[Former Member · Accepted solution]

First please look this http://help.sap.com/saphelp_nw70/helpdata/en/c5/e4aa7f453d11d189430000e829fbbd/frameset.htm

[Former Member · Accepted solution]

That's it!

Thank you!