START_WITH_DELAY in SWE_EVENT_CREATE.... function modules

[Patrick Green]

Hello David,
 
If you would like to submit this as an ASUG development request (knowin=
g
that you are a member in impeccable standing :o)  ), the procedure woul=
d be
to float the suggestion through an OSS message first.  That will give t=
he
developers in Walldorf the chance to address it first via OSS note &/or=
 
support package.  If SAP's reply to your message indicates this would b=
e
better handled within the SAPNet Enhancements Request process (a.k.a.
Continuous Improvement DRQ), I would be glad to help set it up & submit=
 to
SAP for consideration.
 
Your friendly Influence Chair,
ASUG Workflow/Webflow Interest Group
-- Patrick Green
Phone:  918-925-7396
Email:    patrick.d.green at us.pwcglobal.com
 
 
 
 
 
"Becker Stephan (extern)" <Stephan.Becker.ext at mchw.siemens.de>
@MITVMA.MIT.EDU> on 12/20/2001 03:33:50 AM
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:  Re: START_WITH_DELAY in SWE_EVENT_CREATE.... function modules=
 
 
David,
 
you're right, the time is hard-coded, so this would be a case for Alan =
:-)
 
Stephan
-----Original Message-----
From: David Weston [mailto:weston at clockwork.ca]
Sent: Thursday, December 13, 2001 3:42 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: START_WITH_DELAY in SWE_EVENT_CREATE.... function modules
 
 
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 li=
ke
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
 
----- Original Message -----
From: Becker Stephan (extern)
To: SAP-WUG at MITVMA.MIT.EDU
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_tas=
k
function module for one of your event creations, that will delay the
creation of that event for 10 minutes without slowing down the dialog t=
ask.
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=A0does the follow=
ing :-
 
1. Uses SWE_EVENT_CREATE to trigger the event 'Created' and a WS workfl=
ow
is started. In this workflow there is a wait step based on an event cal=
led
'Responsibility'.
2. The function module could also trigger the event 'Responsibility' us=
ing
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 simultaneousl=
y
and the wait step in the workflow has not been=A0created yet=A0!
 
I have put=A0in 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
 
 
 
 
 
----------------------------------------------------------------
The information transmitted is intended only for the person or entity t=
o
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, o=
r
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you rece=
ived
this in error, please contact the sender and delete the material from a=
ny
computer.=