Restarting background work items

[Kjetil Kilhavn]

Thanks for your (and other) suggestions. Unfortunately I am still not able to
process these, so a logical delete and new triggering is the next step.
 
Yes, our WF administrator received messages about the WIs, so everything has
worked fine. There are no particular messages in the log, and the work items all
are in status STARTED. The only strange thing, which indicates problems, is the
last line in the workflow log. Its executed action is
SWW_WI_ERROR_MESSAGE_SEND_S, yet it has a green light in the "traffic light"
section. The green light could mean that the message was sent OK though.
 
I was sure I had heard about a way to restart the work items (or continue
processing). Must have been a dream about SAP R/4  :-)
 
When we upgraded the basis people wanted a "clean" system, so one of our last
actions was to clean out failed RFC calls. Among them were probably the RFC
calls for this step. Those that could be executed were executed (these ones
could not because SU01 was still closed), the remaining ones were deleted. Could
that be the reason for either the strange log or the fact that the steps are
just stopped and won't continue.
--
Kjetil Kilhavn
 
 
 
 
|--------+------------------------------>
|        |          "Bertrand, Scott"   |
|        |          <scott.bertrand at sap.|
|        |          com>                |
|        |          Sent by: SAP        |
|        |          Workflow            |
|        |          <Owner-SAP-WUG at MITVM|
|        |          A.MIT.EDU>          |
|        |                              |
|        |                              |
|        |          24.07.2001 14:39    |
|        |          Please respond to   |
|        |          "SAP Workflow Users'|
|        |          Group"              |
|        |                              |
|--------+------------------------------>
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     SAP-WUG at MITVMA.MIT.EDU                                       |
  |       cc:     (bcc: Kjetil Kilhavn)                                        |
  |       Subject:     Re: Restarting background work items                    |
  >----------------------------------------------------------------------------|
 
 
 
Kjetil,
 
Is the WF administrator getting a message that these WIs cannot be started?
Messages in the step log?  If not, then RSWWERRE is not selecting the WIs
for retry.  If this is the case, I would create an OSS customer message.  I
am not aware of any other method of restarting the WIs.
 
By the way, if the workitem started to execute and then experienced an
enqueue problem, was a temporary error forced? How was the workitem status
changed back to 'READY'?
 
Scott
 
 
-----Original Message-----
From: Kjetil Kilhavn [mailto:KJETILK at statoil.com]
Sent: Tuesday, July 24, 2001 7:14 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Restarting background work items
 
 
This job was running already, it was set up again after the upgrade (stopped
one
hour before shutdown for upgrade). It does not restart them.
I'm going to wait until tomorrow to see if someone has any ideas, but I
can't
let the users wait any longer than that.
--
Kjetil Kilhavn
 
 
 
 
|--------+------------------------------>
|        |          "Bertrand, Scott"   |
|        |          <scott.bertrand at sap.|
|        |          com>                |
|        |          Sent by: SAP        |
|        |          Workflow            |
|        |          <Owner-SAP-WUG at MITVM|
|        |          A.MIT.EDU>          |
|        |                              |
|        |                              |
|        |          23.07.2001 19:24    |
|        |          Please respond to   |
|        |          "SAP Workflow Users'|
|        |          Group"              |
|        |                              |
|--------+------------------------------>
 
>---------------------------------------------------------------------------
-|
  |
|
  |       To:     SAP-WUG at MITVMA.MIT.EDU
|
  |       cc:     (bcc: Kjetil Kilhavn)
|
  |       Subject:     Re: Restarting background work items
|
 
>---------------------------------------------------------------------------
-|
 
 
 
 
Kjtetil,
 
Go to the workflow customizing, there is a line to setup monitoring for
workitems with errors.  Execute this transaction and make sure there is an
entry in interval (like 20 minutes) and an entry in repeat counter (2 or 3).
You can also have the system monitor temporary errors by selecting the
checkbox.  Save your entries.
 
This will start job SWWERRE in your system, which should restart those
workitems.
 
Hope this helps,
Scott
 
 
Scott Bertrand
Technical Consultant
SAP America Inc
 
 
 
-----Original Message-----
From: Kjetil Kilhavn [mailto:KJETILK at statoil.com]
Sent: Monday, July 23, 2001 9:47 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Restarting background work items
 
 
We have upgraded our production system to 4.6C this weekend (hooray) and I
have
only one small problem left.
 
I have some batch work items left in status STARTED because they were trying
to
execute a transaction which was locked. I was sure there was a way to
restart
these, but I can't find out how. The closest I have come is the menu choice
in
Work item selection: Edit, Work item, Execute background work item. That
does
however not help a bit.
 
>From the documentation it seems that these should be handled (restarted) by
the
system, but the system has been up for a day now without that happening (and
the
transaction was closed a day before the system was shut down).
 
I could kill the workflows (logical delete) and restart them, but if
possible I
would like to avoid that.
Does anyone know how to restart these manually or if there is any other
solution?
--
Kjetil Kilhavn
 
 
-------------------------------------------------------------------
Statoil: The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete this
message.
Thank you.