Termination event is created before work item completion

[Rick Sample]

Also, if you need to wait a few seconds for other forks to complete you
can slow it 
down by creating a task with a obj-method that calls FM RZL_SLEEP at
the end of fork. 

Example, wait for a send message(s) to complete. Of course you could
create a terminating events 
on other tasks and make more robust, but this works fine for me.

CALL FUNCTION 'RZL_SLEEP'
     EXPORTING
          SECONDS        = 5
     EXCEPTIONS
          ARGUMENT_ERROR = 01
          OTHERS         = 02.

============
Had this problem and worked around it. 

When you execute the Terminating event, it does not wait for other
forks, 
processing blocks, etc. to complete. It just terminates. 

We create a separate fork(s) for events, let whatever needs to process
like 
send a messages, etc. and let the WF end. 

Rick


>>> solenkahraman at hotmail.com 10/19/2005 14:54:46 >>>

Hi,

We are experiencing some problems with terminating events in our
production 
environment. We didn't come across to those problem neither in dev nor
in QA 
environment.

According to the workflow logs, work item execution is completed after

terminating event creation .That work item is awaiting for a
terminating 
event but that terminatinf event has already been created before it is

completed so the result is it stays in user's inbox .

Has anybody else had that problem before? The only solution I can think
of 
is to activate event queues for that work item but if anybody else have
a 
more robust solution , please advice.

Thanks for your help.

_________________________________________________________________
MSN Messenger 7.5 is now out. Download it for FREE here. 
http://messenger.msn.co.uk 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu 
http://mailman.mit.edu/mailman/listinfo/sap-wug