<br><font size=2 face="sans-serif">Dear Sue,</font>
<br>
<br><font size=2 face="sans-serif">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 size=2 face="sans-serif">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 size=2 face="sans-serif">Some tips when transporting:</font>
<br><font size=2 face="sans-serif">- 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 size=2 face="sans-serif">- be careful on the order or objects</font>
<br><font size=2 face="sans-serif">- find a period when the system is quiet
(this can be a challenge!)</font>
<br><font size=2 face="sans-serif">- also generate any objects that you
have changed in tx swo1</font>
<br><font size=2 face="sans-serif">- run transaction tx. swu7 first before
trying to use the workflow</font>
<br><font size=2 face="sans-serif">- 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 size=2 face="sans-serif">- run the all important 'swu_obuf' transaction</font>
<br><font size=2 face="sans-serif">- exit and re-run swu7 and your errors
should disappear</font>
<br><font size=2 face="sans-serif">- 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 size=2 face="sans-serif">- 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 size=2 face="sans-serif">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 size=2 face="sans-serif">I hope this helps.</font>
<br>
<br>
<br><font size=2 face="sans-serif">all the best</font>
<br>
<br><font size=2 face="sans-serif">Edwin.</font>
<br><font size=2 face="sans-serif"> </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Sue Doughty" <Sue.Doughty@odfl.com></b></font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">03/31/2006 12:01 PM</font>
<br><font size=1 face="sans-serif">Please respond to "SAP Workflow
Users' Group"</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"SAP WF User Group \(E-mail\)"
<sap-wug@mit.edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
Multiple versions created when Workflow
template is transported</font></table>
<br>
<br>
<br><font size=2 face="Arial">We are on SAP Version 4.7, SAP Basis 6.20.</font><font size=3>
</font>
<p><font size=2 face="Arial">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 size=2 face="Arial">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 size=2 face="Arial">I have checked for any OSS notes on this issue,
but have found none.</font><font size=3> </font>
<p><font size=2 face="Arial">Has anyone else ever had this problem?</font><font size=3>
</font>
<p><font size=2 face="Courier New">Regards,</font><font size=3 face="Arial">
</font>
<p><font size=5 color=blue><b><i>Sue T. Doughty</i></b></font><font size=1 face="Courier New"><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>