Old version becomes active after retransport

[Alon Raskin]

We had these problems at a site but that may have to do with the fact
that the target system was a different date/time. I assume this was not
a problem at your site. The other issue is that if somebody has manually
activated the workflow in the target system. This puts a different
date/time stamp on the workflow which can 'screw up' the logic used to
activate the workflows. Why don't you make a small change to the
workflow and re-transport? 


Alon Raskin
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Michael Pokraka
Sent: 01 April 2005 04:58
To: SAP Workflow User Group
Subject: Old version becomes active after retransport

Good morning all,
 
I've encountered bit of versioning hell: 

A WF was transported and all was more or less well, it happily activated
and ran a new version 0004. The transport was repeated a few days later
and the WF activated version 0000. 

Has anyone encountered this and/or have any clue why it would do that?
Transport logs are all fine, and no other transports relating to this WF
were transported in between. 

Happy Friday,
Mike

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug