Changes to WF Start Conditions were not reflected to the targ et s ystem after transport

Rivera, Raul Raul.Rivera at absu.accenture.com
Fri Jul 2 11:54:26 EDT 2004


Thanks for your reply Mike.
 
I refreshed the buffer and checked the transport logs before sending the
message to the group. Today, I checked the subject start conditions and they
are still not reflected.
 
Raul
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Michael Pokraka
Sent: Thursday, July 01, 2004 1:58 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Changes to WF Start Conditions were not reflected to the target
s ystem after transport
 
Hi Paul,
Need I mention SWU_OBUF? Also, remember that they are client-dependent, so
check you're in the correct clients. Check the transport logs too...
Cheers
Mike
 
Rivera, Raul wrote:
> We are in 4.6C.
>
>
>
> Workflow start conditions for existing and new custom workflows were
created
> in DEV. A transport was created for each of the new start conditions.
>
>
>
> These transports were then released to our Staging client together with
all
> related transports for the modifications. In the target system (STG), the
> creation/modification to the start conditions were NOT reflected.
>
>
>
> Did anyone had this experience before or was it something I might have
> missed?
>
>
>
> Thanks,
>
>
>
> Raul
>
>
 


More information about the SAP-WUG mailing list