Wait for event conundrum

[David Weston]

Yep its active, just tried putting a breakpoint at the function module =
SWE_EVENT_CREATE_IN_UPD_TASK, hit Continue and it found the waited event =
10 minutes later and all is well in SWEL.
 
Removed the breakpoint so no "COMMIT WORK" interruption and it doesn't =
work. Strange.
 
Set the breakpoint again, stops at the breakpoint, does a forced "COMMIT =
WORK" and it works again !!
I tried coding an explicit COMMIT WORK before the function module call =
and after it and that doesn't work either.
 
Set the breakpoint again, wait 10 minutes and lo and behold it works.
 
Now I am intrigued !! Any ideas ?
 
Dave
 
  ----- Original Message -----=20
  From: Becker Stephan (extern)=20
  To: SAP-WUG at MITVMA.MIT.EDU=20
  Sent: Wednesday, December 19, 2001 10:30 AM
  Subject: Re: Wait for event conundrum
 
 
 
  Dave,
  is the event linkage active for the instance linkage in SWEINST?
  Stephan
    -----Original Message-----
    From: David Weston [mailto:weston at clockwork.ca]
    Sent: Wednesday, December 19, 2001 3:54 PM
    To: SAP-WUG at MITVMA.MIT.EDU
    Subject: Wait for event conundrum
 
 
    Hi folks,
 
    I have a workflow with a wait for event step in it. The "waited" =
event gets triggered after 10 minutes using the "start with delay =
option" but in the SWEL log I get 'No receiver entered" found. This used =
to work last week. The wait step has a latest end deadline that gets =
triggered after 12 minutes as I am using the "start with delay" feature =
of the SWE_EVENT_CREATE_IN_UPD_TASK function module.
 
    The event gets triggered by :-
 
    call function 'SWE_EVENT_CREATE_IN_UPD_TASK'
 
        EXPORTING
 
            objtype =3D 'PDOTYPE_O'
 
            objkey =3D my_objkey
 
            event =3D 'RESPONSIBILITY'
 
            creator =3D l_event_creator
 
            start_with_delay =3D 'X'
 
        TABLES
 
            EVENT_CONTAINER =3D event_container.
 
      =20
 
    When I look at the instance type linkages in SWEINST I see my =
object, the correct key and the correct receiver id (work item id).
 
    No errors in SM21, SM58 either.
 
    Any ideas out there as to what might be the cause ?.
 
    Cheers
 
    Dave
 
 
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20011219/1f4d2d8c/attachment.htm