Discrepancy of Workflow Version

[Mike Pokraka]

Hi Sherie,

Whilst on the learning curve, it is a *very* good idea to generate a new
version before each major change. It has no impact on the transported
versions but will enable you to revert back and/or see what changed.

It also helps safeguard against corruptions - if it starts spewing strange
errors just open previous version, generate a new one and redo whatever.
You can even copy/paste steps between versions.

Cheers,
Mike

On Mon, August 11, 2008 5:09 pm, Munday,Sherie J. wrote:
> Thanks Mike,
> 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.
> Thanks Again,
> Sherie
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Gambier
> Sent: Monday, August 11, 2008 4:39 AM
> To: SAP Workflow Users' Group
> Subject: RE: Discrepancy of Workflow Version
>
>
> 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 +0800
> From: maorriyan.santoso at gmail.com
> To: sap-wug at mit.edu
> Subject: 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 Sandy
> 	Sent: Sunday, August 10, 2008 10:51 PM
> 	To: SAP Workflow - MIT
> 	Subject: 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 list
> 	SAP-WUG at mit.edu
> 	http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
>
> ________________________________
>
> Get fish-slapping on Messenger! Play Now
> <http://clk.atdmt.com/UKM/go/101719805/direct/01/>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>