WF Start Condition could not be added in target system

[Raju Omkaram]

Raul,
 
It did happen to me twice in the past. Due to time cruch for
troubleshooting, I had the target system opened and made changes
directly. I thought I would go back to troubleshoot when I got a
chance but I never got to it.
 
Thanks
Raju
 
On Fri, 3 Dec 2004 13:43:57 -0800, Rivera, Raul
<raul.rivera at absu.accenture.com> wrote:
> We are in 4.6C
>
> I have created a new custom WF that has a triggering event and start
> condition. When the transport requests related to the WF were moved to the
> target system, the Start Condition is missing from the WF Basic data or
> SWB_COND.
>
> I then went back to the source system, made some dummy changes on the start
> condition to create a new transport and released the transport request to
> the target system. The start condition is still not reflected in the target
> system either in the WF definition or in SWB_COND. I have also refreshed the
> buffer.
>
> Has anybody experienced this before? Creating or changing start conditions
> was seamless before and this is the first time I have seen this.
>
> Any input will be appreciated.
>
> Regards,
>
>
> Raul
>