- Start condition for wf anf transport

[Mike Pokraka]

Hi Srinivasan,
I don't know if this is specific to your case, but there are various
buglets that come about when you use different transactions to maintain
start conditions.
If you go to the start condition via the WF builder and then make
changes/activate it in SWB_COND or similar things it can go a bit wobbly
and the type of stuff you describe can happen.
The best answer here is to pick one method and stick to it - personally I
prefer SWB_COND simply because it's also the transaction that can be used
to maintain it in other systems.
If this applies to your case, make a chance, deactivate and reactivate it
using ONE of the methods mentioned and retransport and check it using the
SAME method.
Cheers,
Mike


> Hi WUG,
> I am in vicious circle now. I tranposrted a WF template in 4.6C / 620. But
> the start condition for the workflow did not get transported.
> I re-defined the start condition in dev system for the wf template and it
> created wf customizing CR. I transported the same to test system. But it
> still did get into my wf template . I could check this in wf template
> header. Binding exists, but start condition is blank.
> Can you tell me what am I doing wrong ?
>
> I need you guys input in this.
>
> thanks and regards
> Srinivasan
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>