Multiple versions created when Workflow template is transported

Tue Apr 4 10:18:39 EDT 2006

I would add one more to the list ... bounce the buffers after the
transport is complete.  (swu_obuf)

Best Regards,
Sherie

Sherie Munday
Workflow Developer/ Analyst
Air Products & Chemicals, Inc.

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Edwin Mukusha
Sent: Tuesday, April 04, 2006 10:08 AM
To: SAP Workflow Users' Group
Subject: Re: Multiple versions created when Workflow template is
transported

Dear Sue, 

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. 

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. 

Some tips when transporting: 
- 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 
- be careful on the order or objects 
- find a period when the system is quiet (this can be a challenge!) 
- also generate any objects that you have changed in tx swo1 
- run transaction tx. swu7 first before trying to use the workflow 
- 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 
- run the all important 'swu_obuf' transaction 
- exit and re-run swu7 and your errors should disappear 
- 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. 
- 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??? 

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. 

I hope this helps. 

all the best 

Edwin. 

	"Sue Doughty" <Sue.Doughty at odfl.com> 
Sent by: sap-wug-bounces at mit.edu 

03/31/2006 12:01 PM 
Please respond to "SAP Workflow Users' Group" 

        To:        "SAP WF User Group \(E-mail\)" <sap-wug at mit.edu> 
        cc:         
        Subject:        Multiple versions created when Workflow template
is transported

We are on SAP Version 4.7, SAP Basis 6.20. 

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. 

This does not happen all the time -- it is sporadic -- and it does not
happen when we promote the transport to the Production system. 

I have checked for any OSS notes on this issue, but have found none. 

Has anyone else ever had this problem? 

Regards, 

Sue T. Doughty
Workflow Specialist
Old Dominion Freight Lines, Inc.
Office:(336)822-5189 Fax:(336)822-5149
sue.doughty at odfl.com 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060404/01676d7c/attachment.htm