Multiple Events triggered - 'No receiver entered' message for one of them in SWEL

[Kjetil Kilhavn]

If you have not tried it yet you could try to create your first event
synchronously (start_recfb_synchron =3D 'X') and the second one asynchr=
onously.
The problem with that is probably that there are no guarantees then eit=
her. Even
if it should work perfectly in test it may work only 99% of the time in=
 
production. I suppose though that if the first step is the wait step (s=
eems a
little strange) OR all the preceding steps are synchronous, it should w=
ork
always.
 
In 4.6C (haven't noticed it before but it may have been there in 3.1, 4=
.0 or
4.5) there is also an input parameter start_with_delay.
Of course this is document well in SAP .... just kidding! Pressing the =
=ABFunction
module documentation=BB displays the familiar message about =ABlanguage=
 EN=BB, but
pressing F1 (with the cursor on the function name) displays ... the lis=
t of
parameters and nothing more.
 
However, a quick look at the code reveals that you may supply either tr=
ue or
false (default is false), and if you supply true a 10 minute delay is s=
et.
--
Kjetil Kilhavn
 
 
 
 
|--------+------------------------------>
|        |          David Weston        |
|        |          <weston at clockwork.ca|
|        |          >                   |
|        |          Sent by: SAP        |
|        |          Workflow            |
|        |          <Owner-SAP-WUG at MITVM|
|        |          A.MIT.EDU>          |
|        |                              |
|        |                              |
|        |          11.12.2001 02:32    |
|        |          Please respond to   |
|        |          "SAP Workflow Users'|
|        |          Group"              |
|        |                              |
|--------+------------------------------>
  >--------------------------------------------------------------------=
--------|
  |                                                                    =
        |
  |       To:     SAP-WUG at MITVMA.MIT.EDU                               =
        |
  |       cc:     (bcc: Kjetil Kilhavn)                                =
        |
  |       Subject:     Multiple Events triggered - 'No receiver entered=
'       |
  |       message for one              of them in SWEL                 =
        |
  >--------------------------------------------------------------------=
--------|
 
 
 
 
=
 
-------------- next part --------------
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
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20011211/f99724d6/attachment.htm
-------------- next part --------------
-------------------------------------------------------------------
Statoil: The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete this
message.
Thank you.