Background work items stuck in process

[Schroeter, Brad]

Jocelyn,
Thanks for the info.  I had 13 background work items and I was able to
successfully re-process 12 of them using SWI1 and Edit => Work items =>
Execute batch item.  However, one of them had a problem.  It gave me an ABAP
runtime error in line 94 of function module SWP_WORKFLOW_WI_ERROR_SIGNAL: it
says parameter "WF" is missing when calling function module
SWP_WI_CALLBACK_SUSPEND.  This call to function module
SWP_WI_CALLBACK_SUSPEND was added on 4/19/2001 when I implemented OSS note
95859 ("Restarting work flow instances after system restart", version 9
dated 7/21/2000).  This specific work item was created on 8/8/2001.  Would
you have any idea why this one work item would get an error and the other 12
wouldn't?
 
-Brad
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Tuesday, October 30, 2001 9:02 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Background work items stuck in process
 
 
Hi Brad,
Long term approach sounds fine - adding the exceptions to the existing
method and creating a new workflow version
should be enough.
 
Short term - if you want to just close off the items (not re-execute them),
you should be able to do this by going to the
technical work item display of the relevant work item and using the Edit
>Change option - you should then be able to
complete manaully (if synchronous) or complete with event (if asynchronous).
(From memory those options are
available in 4.0B.)  Doublecheck that the workflow above continues correctly
after you have done that.
 
Later releases have an option in SWI1 to re-execute stuck batch items, but I
can't recall having that option in 4.0B,
so if you have to re-execute you might  have to do that manually and then
finish the workitem as above.
 
Regards,
 
 
 
Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
 
-----Original Message-----
From: Schroeter, Brad [mailto:BSchroeter at ti.com]
Sent: Wednesday, 31 October 2001 10:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Background work items stuck in process
 
 
 
I'm on 4.0B and I've got some workflows whose work items are stuck in
process (status = "STARTED").  This happened due to exceptions not being
defined in the method: the exceptions were in the method code via
"exit_return" but the corresponding exception was not defined in the actual
method's attributes.  So the work items have error OL818: Exception '9002'
is not defined for method 'COMPLETEECO' object type 'ZECO'.
 
Long-term:
Since our exceptions are not modeled in definition and they are temporary
errors, my plan is to create these missing temporary exceptions in the
actual method's attributes so that the system will attempt to restart the
work item and if necessary, send a notification to the Workflow
administrator.  So do I only need to create a new Workflow version (i.e. I
don't have to create a new method and a new task, do I)?
 
Short-term:
How do I go about getting these background work items unstuck?  Please note
that these do seem to be "temporary" errors since this has only happened on
a few (not all) Workflows.
 
 
Thanks,
Brad
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20011101/7c602de5/attachment.htm