Wait step triggered by event raised within current workflow i nstance

[Breslavets, Sergey]

Hi Peter,
 
when the event is raised there is no way to tell whether the "event creator"
(ME22N) was called from SWL_WI_EXECUTE of via a transaction call. Even if you
use user-exit to raise the event you can only "guess" from analysing Wf tables
if the transaction is running 'standalone' or from a workitem (and possibly
raise different events)...
 
What are you trying to achieve in terms of the business functionality? Maybe
there is another way to do it..
 
Regards,
Sergey
 
 
-----Original Message-----
From: Peter Abram [mailto:peterabram at hotmail.com]
Sent: Tuesday, January 14, 2003 7:52 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Wait step triggered by event raised within current workflow
instance
 
 
A parallel (fork) branch of the workflow contains a wait step listening for
event BUS2012 SIGNIFICANTLYCHANGED - with the intention of terminating the
current instance if significant changes are made to the purchase order
outside of the current workflow instance.
 
The event BUS2012 SIGNIFICANTLYCHANGED event can be raised within the
current workflow instance because there is a step referencing transaction
ME22N.
 
How do I prevent the branch containing the wait step from reacting to the
execution of the ME22N work item within the current workflow instance
(assuming the agent does make a significant change)?
 
 
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus