<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>I would add one more to the list ... bounce the buffers
after the transport is complete. (swu_obuf)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>Best Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>Sherie</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>Sherie Munday</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>Workflow Developer/ Analyst</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=150151714-04042006><FONT face=Arial
color=#0000ff size=2>Air Products & Chemicals, Inc.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Edwin
Mukusha<BR><B>Sent:</B> Tuesday, April 04, 2006 10:08 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: Multiple versions created when
Workflow template is transported<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Dear Sue,</FONT> <BR><BR><FONT
face=sans-serif size=2>We too are on the same version as you. I have
experienced the problem in our Quality as you describe it. I have had
multiple non-active transport versions created when there was a problem at
activation time as the final step of the transport process. If for example
I transported my workflow definition ahead of other objects the workflow would
fail to generate at some moment during process. However by the time I came
in to do a 'syntax check' all the programming objects were there and
it seemed odd why the new version was not being used. In such a case
I fixed this problem in Quality by sending through another transport. I
wish though I could simple go to the workflow builder and access the menu option
Workflow->Activation->Generate and Activate Runtime version.
</FONT><BR><BR><FONT face=sans-serif size=2>Another situation was at upgrade
time (and one other time unrelated to one), I believe we had a couple of
instances where there was a version gap in the Quality system for whatever
reason. So our latest changes were not being picked up in since UNQ was
expecting version 007 and we were clear back to version 001. To fix this
we just transported the same workflow 6 times to bring us back to right level.
I also remember multiple version gaps in the rare case I used an SAP
delivered workflow template.</FONT> <BR><BR><FONT face=sans-serif size=2>Some
tips when transporting:</FONT> <BR><FONT face=sans-serif size=2>- after
transporting don't always expect that all the tables will be updated instantly
there is some buffering that can cause delays, basis can help in extreme cases
of delayed updates</FONT> <BR><FONT face=sans-serif size=2>- be careful on the
order or objects</FONT> <BR><FONT face=sans-serif size=2>- find a period when
the system is quiet (this can be a challenge!)</FONT> <BR><FONT face=sans-serif
size=2>- also generate any objects that you have changed in tx swo1</FONT>
<BR><FONT face=sans-serif size=2>- run transaction tx. swu7 first before trying
to use the workflow</FONT> <BR><FONT face=sans-serif size=2>- if you find errors
in tx. swu7 , simply double click the workflow no. to drill down into the
workflow builder. this will force the system to read the new workflow
definition</FONT> <BR><FONT face=sans-serif size=2>- run the all important
'swu_obuf' transaction</FONT> <BR><FONT face=sans-serif size=2>- exit and re-run
swu7 and your errors should disappear</FONT> <BR><FONT face=sans-serif size=2>-
to find which version is being used by a workflow in any system just view the
latest wf log: from the workitem display goto Extras->Technical Data there
you will find the Definition Version.</FONT> <BR><FONT face=sans-serif size=2>-
also an important view for the actual version information is on the first screen
before the workflow builder if you use tx pftc: goto
Utilities->Technical Information scroll down in the window and you will find
more detailed version information compared to the dropdown on the workflow
builder screen. This information can differ???</FONT> <BR><BR><FONT
face=sans-serif size=2>This might all seem kind of 'hokey' but I am sure you can
understand that depending on the your system configuration, buffering cycles and
system load; a lot has to happen in harmony if your workflow is to arrive in one
piece.</FONT> <BR><BR><FONT face=sans-serif size=2>I hope this helps.</FONT>
<BR><BR><BR><FONT face=sans-serif size=2>all the best</FONT> <BR><BR><FONT
face=sans-serif size=2>Edwin.</FONT> <BR><FONT face=sans-serif
size=2> </FONT> <BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<TD><FONT face=sans-serif size=1><B>"Sue Doughty"
<Sue.Doughty@odfl.com></B></FONT> <BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>03/31/2006 12:01 PM</FONT> <BR><FONT
face=sans-serif size=1>Please respond to "SAP Workflow Users'
Group"</FONT> </P>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
"SAP WF User Group \(E-mail\)" <sap-wug@mit.edu></FONT>
<BR><FONT face=sans-serif size=1> cc:
</FONT> <BR><FONT face=sans-serif size=1>
Subject: Multiple versions
created when Workflow template is
transported</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT face=Arial size=2>We
are on SAP Version 4.7, SAP Basis 6.20.</FONT><FONT size=3> </FONT>
<P><FONT face=Arial size=2>We have an issue where transporting a modified
workflow template to the Quality system sometimes causes multiple versions to be
created in Runtime available, Saved status. The changes made that are
being transported are in the Runtime available, Saved versions so we are not
able to execute the workflow with the new changes. Every time you go into
the Workflow builder to look at the template in the Quality system, the number
of versions increases. I transported one today that was Version 0001 and
is now up to Version 59 in the Quality system.</FONT>
<P><FONT face=Arial size=2>This does not happen all the time -- it is sporadic
-- and it does not happen when we promote the transport to the Production
system.</FONT>
<P><FONT face=Arial size=2>I have checked for any OSS notes on this issue, but
have found none.</FONT><FONT size=3> </FONT>
<P><FONT face=Arial size=2>Has anyone else ever had this problem?</FONT><FONT
size=3> </FONT>
<P><FONT face="Courier New" size=2>Regards,</FONT><FONT face=Arial size=3>
</FONT>
<P><FONT color=blue size=5><B><I>Sue T. Doughty</I></B></FONT><FONT
face="Courier New" size=1><BR>Workflow Specialist<BR>Old Dominion Freight Lines,
Inc.<BR>Office:(336)822-5189
Fax:(336)822-5149<BR>sue.doughty@odfl.com</FONT><FONT size=3> </FONT>
<P><TT><FONT size=2>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT></TT>
<P></P></BODY></HTML>