Workflow Restart after System Problem

[Stephens, Monique S L]

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/20051207/b0d6d7e9/attachment.htm