<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=100020717-11112005><FONT face=Arial color=#0000ff size=2>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).
</FONT></SPAN></DIV>
<DIV><SPAN class=100020717-11112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=100020717-11112005><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=100020717-11112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=100020717-11112005><FONT face=Arial color=#0000ff size=2>Hope
that helps.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<P><B><I><FONT face=Arial color=#000080>Dan Stoicof</FONT></I></B><I></I>
<BR><FONT face=Arial color=#000080 size=2>SAP Workflow/ABAP Team</FONT>
<BR><FONT face=Arial color=#000080 size=2>GREAT-WEST LIFE and ANNUITY</FONT>
</P>
<P><FONT face=Arial color=#0000ff size=2></FONT><BR><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]<B>On Behalf Of </B>Munday,Sherie
J.<BR><B>Sent:</B> Friday, November 11, 2005 9:59 AM<BR><B>To:</B> SAP Workflow
Users' Group<BR><B>Subject:</B> Workflow moves from Active to Runtime
Exists<BR><BR></P></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Hello fellow
workflowers,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=115015216-11112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>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?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=115015216-11112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Many thanks to
those of you who are much wiser than me.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=115015216-11112005>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=115015216-11112005>Sherie</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=115015216-11112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Sherie
Munday</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Workflow
Development</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Support &
Competency Center</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=115015216-11112005>Air Products &
Chemicals, Inc.</SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>