Old version becomes active after retransport

Alon Raskin araskin at 3i-consulting.com
Fri Apr 1 09:01:42 EST 2005


I cant be certain that this is your problem but I know we had hell when we tried to transport to systems with different time zones.... 
 
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 
p: +61 3 9625 2189 (Head Office)
f:  +61 3 8610 1239 
c:  +1 207 756 0370
w: http://www.3i-consulting.com

________________________________

From: sap-wug-bounces at mit.edu on behalf of Michael Pokraka
Sent: Fri 4/1/2005 08:37
To: SAP Workflow Users' Group
Subject: RE: Old version becomes active after retransport



Hi Alon,
Good point about the time, it was first transported before and then again after
we changed to summer time. Hmmmm, an obscure bug with time zones?

Getting it fixed is a no brainer, but the customer is asking why and that is
also something I'd like to know....?

Thanks
Mike

--- Alon Raskin <araskin at 3i-consulting.com> wrote:
> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6273 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050401/2716349a/attachment.bin


More information about the SAP-WUG mailing list