Funny Workflow Versions
John A Haworth
jhoworth at csc.com
Fri Oct 15 05:23:22 EDT 2004
HI
If you dont use PFTC_CHG to go into change mode for your workflow, what=
s
the alternative way that you use, that doesn't enable versioning??
John
-----------------------------------------------------------------------=
-----------------
This is a PRIVATE message. If you are not the intended recipient, pleas=
e
delete without copying and kindly advise us by e-mail of the mistake in=
delivery. NOTE: Regardless of content, this e-mail shall not operate to=
bind CSC to any order or other contract unless pursuant to explicit wri=
tten
agreement or government initiative expressly permitting the use of e-ma=
il
for such purpose.
-----------------------------------------------------------------------=
-----------------
=
"Chatterjee, =
Partha (US - San To: SAP-WUG at MITVMA.=
MIT.EDU
Ramon)" cc: =
<pchatterjee Subject: Re: Funny Workf=
low Versions
@deloitte.com> =
Sent by: SAP =
Workflow =
<Owner-SAP-WUG =
=
=
14/10/2004 18:35 =
Please respond =
to "SAP Workflow =
Users' Group" =
=
=
Hi Alon,
In the example I was speaking of, I turned workflow versioning on witho=
ut
realizing it troubleshooting a problem I was having. Subsequently, eve=
ry
time I regenerated and transported, a new version was created in both
source and target systems with different version numbers in both source=
and
target systems. This caused a certain level of perturbance for me ...
In subsequent implementations, I am careful not to use Workflow version=
ing
(this is turned on IF and ONLY IF use the option under t-code PFT_CHG -=
->
Workflow --> Generate version). If I never use this function, I never =
have
any version other than 0000 for my workflows in both source and target
instances.
Once you have turned on versioning (PFT_CHG --> Workflow --> Generate
version), it automatically generates a new version every time you trans=
port
your workflow template across instances.
This is consistent with the behavior that Heinz spoke of also. The poi=
nt
is (and I have had an SAP Platinum Consultant tell me the same thing) i=
t is
better not to turn on versioning unless it is truly serving some sort o=
f
useful purpose.
If you have turned it on already, then generally speaking your latest
version in your source system will correspond with your latest version =
in
your target system.
Hope this explanation is clearer,
Partha
________________________________
From: SAP Workflow on behalf of Alon Raskin
Sent: Thu 10/14/2004 11:56 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Funny Workflow Versions
Hi Partha,
Thank you for your email. I am not sure I have understood properly. Wha=
t do
you mean by 'not using workflow versioning'. The versions are created i=
n
the QA system when we transport. We do not create versions ourselves. I=
belive this is the way it works:
When the workflow is transported, SAP checks if there are currently act=
ive
instances of the workflow. If there are then it will create a new versi=
on
so that subsequent triggers of the WF will use the new version (while n=
ot
interfering with the older versions). If there are not instances then I=
believe that the current version is simply overwritten (ie. no new vers=
ion
is created).
Is that not right?
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
w: http://www.3i-consulting.com
________________________________
From: SAP Workflow on behalf of Chatterjee, Partha (US - San Ramon)
Sent: Thu 14/10/2004 17:47
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Funny Workflow Versions
Hi Alon/Heinz,
I have experienced the same thing in a 4.6c implementation. And I beli=
eve
Heinz's explanation is absolutely accurate.
One thing I have done on subsequent implementations is to NOT use workf=
low
versioning. In my experience, it is not worth the confusion it causes =
when
you start interacting with the transport system and the actual version =
that
becomes active in your target system.
If you cannot get away from using it, in general, the latest version in=
your source system corresponds to the latest version in your target sys=
tem
even if the actual version numbers are different across instances.
With regards,
Partha Chatterjee
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Schmidinger, Heinz (Unaxis IT BZ)
Sent: Wednesday, October 13, 2004 11:27 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Funny Workflow Versions
Hi Alon,
the reason could be:
You are developing /desinging a WF-Def. in System A/Clt. 1. You are tes=
ting
your definition in Sys A /Clt. 2.
If you change the Definition and test it again, you get a new
runtime-version, if a Def is still active ...
So you can create new Defs-Versions in Sys A/clt. 1, in Clt.2 the
runtime-versions will be increased and so on.
Than you transport your defiitions to System B. The last active Version=
will
be transported (e.g. Version 6.) The first execution of the WF-Definiti=
on
will create rtv 1.
So you change your WF again in Sys A whith creation of new Versions twi=
ce,
you will have Version 8. IF this Version is transported to Sys B and
executed, it will be rtv 2.
Confusing ? me too.
regards an a nice day.
Heinz
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Alon Raskin
Gesendet am: Donnerstag, 14. Oktober 2004 05:36
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Funny Workflow Versions
Hi Richard,
Thanks for this. Its really quite scary for us as it doesn't give us an=
y
confidence that when we rebuild a system (and we do it quite frequently=
in
our testing clients), the workflow will be 'ready to go'. We have quite=
a
few workflows and even more sub-workflows and they all seem to be
displaying
different versions.
Would you say that this is a bug (having 8 versions and having version =
2
the
active one) ?
Regards,
Alon Raskin
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Richard Marut
Sent: Thursday, October 14, 2004 4:18 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Funny Workflow Versions
Lon,
I had this happen one time back in 3.1H. I verified that the active ver=
sion
was the actual the one right one and then I generated a new version. Al=
l
was
okay after that.
Richard...
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of A=
lon
Raskin
Sent: Wednesday, October 13, 2004 11:46 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Funny Workflow Versions
In our testing environments we have some strange going-ons.... Was hopi=
ng
someone could shed some light on this.
When I display a workflow, I can see that it has 8 versions yet version=
2
is
the active one. How can that be? I thought SAP creates a new version wh=
en
there is a current instance of the currnet active version but how can i=
t be
that there are 8 versions and version 2 is the active one.
Any thoughts/suggestions are welcome
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
w: http://www.3i-consulting.com
This message (including any attachments) contains confidential informat=
ion
intended for a specific individual and purpose, and is protected by law=
.
If you are not the intended recipient, you should delete this message. =
Any
disclosure, copying, or distribution of this message, or the taking of =
any
action based on it, is strictly prohibited.
This message (including any attachments) contains confidential informat=
ion
intended for a specific individual and purpose, and is protected by law=
.
If you are not the intended recipient, you should delete this message. =
Any
disclosure, copying, or distribution of this message, or the taking of =
any
action based on it, is strictly prohibited.
=
More information about the SAP-WUG
mailing list