Workflow moves from Active to Runtime Exists

[Stoicof, Dan]

I have recently had exactly the same problem (we're in 4.7).  What I found, was that some tasks were left behind in the source system.  Funny, that there was to error during transport (when the WF gets activated).   
 
What you need to do to find out what's wrong is to go in the destination system (the one with "runtime available, saved") , open the workflow builder and run a check.  It'll tell you what's missing and you can take it from there.
 
Hope that helps.
 

Dan Stoicof 
SAP Workflow/ABAP Team 
GREAT-WEST LIFE and ANNUITY 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of Munday,Sherie J.
Sent: Friday, November 11, 2005 9:59 AM
To: SAP Workflow Users' Group
Subject: Workflow moves from Active to Runtime Exists



Hello fellow workflowers,
 
We are using 4.6C and have run into an anomoly with workflow.  On occasion a transport will move from one system to another (Dev to ITG or Prod Support to Production), and the Activation of the workflow is somehow lost.  In the sending client the workflow shows "Active, Saved" but in the receiving client the workflow indicates "Runtime Exists, Saved".  The only fix we have found is to go back to Dev and de-activate and re-activate the workflow and then transport back through all of the clients.  Does anyone know what causes this and how we can avoid it in the future?
 
Many thanks to those of you who are much wiser than me.
Regards,
Sherie
 
Sherie Munday
Workflow Development
Support & Competency Center
Air Products & Chemicals, Inc.

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