Versioning Issues with Custom Workflows

[Omkaram, Raju]

Hello fellow workflow gurus,
 
I had the same issue but in EBP. For some reason my custom worklfows, upon
transport to other systems, never carried the changes. The only to way to
circumvent this issue, under lot of time line pressure, we recreated as new
and transported them then it worked.
 
Raju
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Wednesday, May 26, 2004 10:55 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Versioning Issues with Custom Workflows
 
 
Hi Paul,
As regulars of the SAP-WUG are aware, 4.6C initially had a number of
problems with the change
in how workflows were transported.
Check your support packs are up-to-date and search OSS for notes in
component BC-BMT-WFM with keyword "transport" and your release level.
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Rivera, Raul
Sent: Thursday,27 May 2004 1:35 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Versioning Issues with Custom Workflows
 
 
We are on 4.6c. Thanks
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Dart,
Jocelyn
Sent: Tuesday, May 25, 2004 9:45 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Versioning Issues with Custom Workflows
 
And the lucky SAP release in which you are having these problems is....?
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Rivera, Raul
Sent: Wednesday,26 May 2004 6:11 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Versioning Issues with Custom Workflows
 
 
We have just applied SAP Support packages in all of our environments except
Production. We are having versioning issues with our custom Workflows in our
DEV/TST/STG systems. For example, custom WF WS90000001 uses version 8
instead of the current version 11. The WF Builder sees version 11 but for
reasons unknown to us, it is using version 8 instead as its active version.
The same is true for other custom workflows.
 
What I've noticed is that active version the Staging client uses what is the
LATEST version number in Development. In the example above WS90000001's
latest DEV version is 8. Same is true for WS90000002 whose latest DEV
version is 1 and uses version 1 in Staging (instead of 3).
 
We are in touch with SAP Support with this problem and posted this question
to the group to see if others had this experience before.
 
Thanks everyone.