Workflow Restart after System Problem

[Gregory Utley]

Hi Jocelyn,

 

Yes, I have.  The underlying problem is that the last step of the
workflow is in COMPLETED status and the next step was never triggered.
I tried the RESUME wapi, restarting in the last step without success.
Until I saw your note, I had not tried executing RESUME against the
workitem id of the workflow itself.  (I assumed RESUME applied to the
step to be restarted.)  Anyway, I tried it against the top workflow
workitem id, and it appears to work fine - some of the time.  (Some wf's
go to completion; stop stop with unusual errors.)

 

I haven't had the time to analyze the errors completely, but you put me
on the right track.  RESUME should be executed against the workflow, not
the individual task step.

 

Thanks,

Greg Utley

CiTR!X Systems, Inc.

SAP Development Team

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, December 08, 2005 3:04 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow Restart after System Problem

 

SAP_WAPI_ADM_WORKFLOW_RESUME should do a step restart by default ... -
i.e. it should find the step to restart in your WF instance on its own -
have you tried it?

 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Stephens, Monique S L
Sent: Thursday, 08 December 2005 7:18 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow Restart after System Problem

We had a somewhat similar problem when WF-BATCH was accidentally deleted
in our SRM system.  All carts could not continue the workflow process.
We actually ran SWU2 for that specific date and executed the LUWs.
Don't know if this will help your situation.

 

Monique Stephens

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Gregory Utley
Sent: Wednesday, December 07, 2005 1:53 PM
To: SAP Workflow Users' Group
Subject: RE: Workflow Restart after System Problem

 

Sorry for the response delay.  I've been out of the office.

 

Thanks Alon, but that won't work.  I can force the workflow into ERROR
status, but I can't change the status of the last step that executed
because it has already completed.  The SWPR restart results in a runtime
error while trying to find the individual workitem in ERROR status;
there is none.  Again, in earlier versions, modification of the callback
flag would allow a restart in a step that has already completed.  Anyone
know how to do it in SRM 4.0?

 

Greg Utley

CiTR!X Systems, Inc.

SAP Development Team

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Alon Raskin
Sent: Tuesday, November 29, 2005 6:16 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Workflow Restart after System Problem

 

Why not just force the status of the WF into ERROR (WORKITEM.SetStatus)
and then go to SWPR and restart them?

 

Alon Raskin

e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 

p: +1 207 409 4983 (please note new number)

f:  +61 3 8610 1239 

w: http://www.3i-consulting.com <http://www.3i-consulting.com/> 

 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Gregory Utley
Sent: Monday, November 28, 2005 5:51 PM
To: SAP Workflow Users' Group
Subject: Workflow Restart after System Problem

All,

 

Over the weekend, we experienced tablespace errors during which several
workflows stopped running.  These workflows are not in error status -
they simply stopped with the last executed step in COMPLETED status
without triggering a subsequent step.  All lights are green - no
messages.  The tablespace problems were resolved; workflows in process
before and after the problem occurred are running normally or have
completed successfully.

 

I've done as complete a search of the WUG archives as I can and have
unearthed one message that seems to precisely mimic the problem
described above (although it was posted a few years back).  After
several responses from different participants, Jocelyn finally
recommended contacting OSS, so I'm not optimistic that there is a quick
solution to this one.  But again, the message is dated, and we're now
running the current version of SRM in the portal.  There may now be more
options.

 

I've tested all SAP_WAPI funmods that look appropriate (workitem
execute, resume, restart, etc.) but none will restart the workflows.
The common complaint from the programs is that the last step that
executed is COMPLETED and not in ERROR status.  I've also tried
transactions SWIA and SWPC to no avail.

 

Back in the old days, we could execute SWP_WORKITEM_CALLBACK_REPEAT,
reset the callback flag, and the workflow would restart.  I have a note
that SAP_WAPI_ADM_WORKFLOW_RESUME replaces SWP_WORKITEM_CALLBACK_REPEAT
in SRM, but it doesn't appear to be as flexible in terms of resetting
completion status or in which step to affect the restart.  (Bear in mind
that I need a step-restart.  If I do a workflow restart, I lose all
interim approvals.)

 

It's a dilemma.

 

Greg Utley

CiTR!X Systems, Inc.

SAP Development Team

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051209/a1aea320/attachment.htm