START_WITH_DELAY in SWE_EVENT_CREATE.... function modules

[David Weston]

Hi Stephan,
 
Thanks for this....learn something new all the time, isn't life great !!
OK here's another question....can this time be configured ? It looks =
like its
hard coded to me in the function modules. 10 minutes seems a trifle =
excessive.
 
Alan....looks like a development request to me ? Could we make this =
configurable ?
Can't hurt to ask right....:)
 
Happy holidays.
 
Cheers
Dave=20
     =20
  ----- Original Message -----=20
  From: Becker Stephan (extern)=20
  To: SAP-WUG at MITVMA.MIT.EDU=20
  Sent: Tuesday, December 11, 2001 3:24 AM
  Subject: Re: Multiple Events triggered - 'No receiver entered' message =
for one of them in SWEL
 
 
  dave,
  use the parameter "start_with_delay" in the =
swe_event_create_in_upd_task function module for one of your event =
creations, that will delay the creation of that event for 10 minutes =
without slowing down the dialog task. when you are starting event =
creation in the dialog task, always use the _in_update_task function =
module, as otherwise you have an event and no corresponding document on =
the database in case of an update failure.
  stephan
    -----Original Message-----
    From: David Weston [mailto:weston at clockwork.ca]
    Sent: Tuesday, December 11, 2001 2:32 AM
    To: SAP-WUG at MITVMA.MIT.EDU
    Subject: Multiple Events triggered - 'No receiver entered' message =
for one of them in SWEL
 
 
    Hi group,
 
    I have a tricky question for the group. Using table T779X to trigger =
a function module when an org unit
    is created to trigger a workflow, the function module does the =
following :-
 
    1. Uses SWE_EVENT_CREATE to trigger the event 'Created' and a WS =
workflow is started. In this workflow there is a wait step based on an =
event called 'Responsibility'.
    2. The function module could also trigger the event 'Responsibility' =
using SWE_EVENT_CREATE immediately after the 'Created' event.
 
    Here's the issue: the wait step for the event 'Responsibility' does =
not find a receiver because the 2 events are almost triggered =
simultaneously and the wait step in the workflow has not been created =
yet !
 
    I have put in the ABAP code the command 'WAIT UP TO n SECONDS' after =
the event 'Created' is triggered but hate this as it slows the dialog =
transaction !! I have tried using SWE_EVENT_CREATE_IN_UPD_TASK but that =
doesn't help either.
 
    Has anyone else had this sort of problem, if so how did you go about =
solving it ?.
 
    Cheers
    Dave Weston
    Clockwork.ca =20
      =20
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20011213/e80237e1/attachment.htm