<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Tahoma
}
</STYLE>
<META content="MSHTML 6.00.2900.3354" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV dir=ltr align=left><SPAN class=594550616-11082008><FONT face=Arial
color=#0000ff>Thanks Mike,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=594550616-11082008><FONT face=Arial
color=#0000ff>I did not realize that you could change versions in Dev! I
suppose we never had a desire to do so. I've been developing workflows for
7 years and I am constantly learning new things from this
group.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=594550616-11082008><FONT face=Arial
color=#0000ff>Thanks Again,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=594550616-11082008><FONT face=Arial
color=#0000ff>Sherie</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Mike
Gambier<BR><B>Sent:</B> Monday, August 11, 2008 4:39 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Discrepancy of Workflow
Version<BR></FONT><BR></DIV>
<DIV></DIV>Sandy,<BR> <BR>The runtime Version number in your target
system will tend to be higher in your target system if the definition has ever
been kicked off as an instance or still has running instances when the Transport
is imported. <BR> <BR>This is because SAP's Transport mechanism creates
a temporary '9999' version (SWDSHEADER & HRS1205) each
time in the target environment and then decides whether: a) it can simply
overwrite the current active version of the definition with this, or b) it
should create a new version and try to make this the current active
version.<BR><BR>By the way, I have noticed that in ECC 6 (and presumably
this was 600 onwards) the runtime version number has found its way into
SWWWIHEAD. Before this was simply stored in SWP_HEADER. Now it appears in both
tables for some odd reason.<BR> <BR>Also note that the 'Original Version'
number from the source environment should still be kept in
SWDSHEADER-ORG_VERSION. This is the value shown in brackets when displaying the
WF definition in SWDD I believe.<BR> <BR>So I don't think Sherie's answer
below was quite right. If the Workflow being transported has not been used
in the target system then the '0000' version will probably be overwritten each
time, yes. But, if the definition is being used often and changed often, the
numbers will gradually become very different over time. This is particularly
true if a Transport fails to activate the definition properly but the
definition is kicked off frequently despite this failure. In this situation the
system can unfortunately try to turn the '9999' version into a proper
version and fail repeatedly but still bump up the version number each time
in the process.<BR> <BR>As an exmaple we have a WF Definition in our
development environment which is currently on version '0024' (remember that the
creation of WF versions in development is purely optional), whereas in our live
system the exact same definition has crept up to runtime version '0243'.
<BR> <BR>Regards,<BR> <BR>Mike GT<BR> <BR>
<HR>
<BR>Date: Mon, 11 Aug 2008 14:19:25 +0800<BR>From:
maorriyan.santoso@gmail.com<BR>To: sap-wug@mit.edu<BR>Subject: Re: Discrepancy
of Workflow Version<BR><BR><BR>
<DIV dir=ltr>Thanks Sherie.<BR>Is there any configuration to set the
increment?<BR><BR>I also check randomly all transported workflows, some of them
have same version as in Dev and some of them is different.<BR><BR>
<DIV class=EC_gmail_quote>2008/8/11 Munday,Sherie J. <SPAN dir=ltr><<A
href="mailto:MUNDAYSJ@airproducts.com">MUNDAYSJ@airproducts.com</A>></SPAN><BR>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial
color=#0000ff>Sandy,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff>The version in
Dev will always be 000. As you transport into the other systems, the
count in those systems will increment.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff>Best
Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial
color=#0000ff>Sherie</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff>Sherie
Munday</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff>Workflow
Developer/ Analyst</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff>Air Products
& Chemicals, Inc.</FONT></SPAN></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><B>From:</B> <A
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A> [mailto:<A
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A>] <B>On
Behalf Of </B>Sandy<BR><B>Sent:</B> Sunday, August 10, 2008 10:51
PM<BR><B>To:</B> SAP Workflow - MIT<BR><B>Subject:</B> Discrepancy of Workflow
Version<BR></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=EC_Wj3C7c>
<DIV></DIV>
<DIV dir=ltr>Dear all.<BR>We're transporting worflows from development client
into QA client.<BR>In development has version 0000 but when it reached QA, the
version in 0005.<BR><BR>Does any body know which settings related with this
issue? I believe workflow version between source client and target client
should be in sync.<BR><BR><BR>Many
Thanks<BR></DIV></DIV></DIV></DIV><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"
target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV><BR>
<HR>
Get fish-slapping on Messenger! <A
href="http://clk.atdmt.com/UKM/go/101719805/direct/01/" target=_new>Play Now</A>
</BODY></HTML>