Controlling execution of branches in fork

[Mike Pokraka]

"From SAP help I could infer that we should not use event creator step in
one branch and wait for event in another branch of the same fork to achive
this purpose."

Where is this? Sounds like perfectly good design to me, or else I've been
doing it wrong all these years...


On Fri, September 11, 2009 5:01 am, akshay.bhagwat at wipro.com wrote:
> Hello Friends,
>
>  We have a scenario where workflow should process multiple types of Idocs
> e.g. 4 different types of IDOCs.
>
>  So I am planning to use a fork which will wait for all these events to
> start processing in branches of the fork as and when these Idocs are
> received.
>
>  But now the point is that the sequence of incoming Idocs is not fixed,
> whereas there is dependency between the execution of branches of this
> fork i.e. once branch 1 processing is finished, then branch 3 should be
> executed then branch 4 and then branch 2 etc.
>
>>From SAP help I could infer that we should not use event creator step in
>> one branch and wait for event in another branch of the same fork to
>> achive this purpose.
>
> In this case how can we achieve the dependency / synchronization of
> execution between branches of same fork?  (I am not sure if we can local
> events?)
>
>
>
> Appreciate any inputs on this front.
>
>
>
> Thanks and Regards,
>
> Akshay
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you
> are not the intended recipient, you should not disseminate, distribute or
> copy this e-mail. Please notify the sender immediately and destroy all
> copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>