Discrepancy of Workflow Version

[Mike Gambier]

Sandy,
 
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. 
 
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.
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.
 
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.
 
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.
 
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'. 
 
Regards,
 
Mike GT
 



Date: Mon, 11 Aug 2008 14:19:25 +0800From: maorriyan.santoso at gmail.comTo: sap-wug at mit.eduSubject: Re: Discrepancy of Workflow Version
Thanks Sherie.Is there any configuration to set the increment?I also check randomly all transported workflows, some of them have same version as in Dev and some of them is different.
2008/8/11 Munday,Sherie J. <MUNDAYSJ at airproducts.com>


Sandy,
The version in Dev will always be 000.  As you transport into the other systems, the count in those systems will increment.
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 SandySent: Sunday, August 10, 2008 10:51 PMTo: SAP Workflow - MITSubject: Discrepancy of Workflow Version




Dear all.We're transporting worflows from development client into QA client.In development has version 0000 but when it reached QA, the version in 0005.Does any body know which settings related with this issue? I believe workflow version between source client and target client should be in sync.Many Thanks_______________________________________________SAP-WUG mailing listSAP-WUG at mit.eduhttp://mailman.mit.edu/mailman/listinfo/sap-wug
_________________________________________________________________
Win New York holidays with Kellogg’s & Live Search
http://clk.atdmt.com/UKM/go/107571440/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080811/3cb77676/attachment.htm