<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Event Queues - Comments on Pros & Cons?</TITLE>
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D203185106-20092001><FONT face=3DArial =
color=3D#0000ff size=3D2>Hi=20
Andrew,</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001>I go into more detail about the =
recommendations about=20
when to use the event queue and when not to in the "what's new to=20
6.10" virtual classroom presentation in SAPNet. I admit =
this is=20
the last place that you'd expect information about older Releases but =
there you=20
have it.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001>Only the events that error out within the =
receiver are=20
added to the error queue. E.g. problems starting the flow because the =
object=20
does not yet exist or a table space filled up. The evaluation of the =
check=20
functions including start conditions takes place beforehand so if the =
condition=20
is false (or your check routine returns an exception) the =
event is not=20
added to the queue. </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001>I'm not sure why you would want to restart =
events where=20
they have been configured to evaporate without any consequences (via =
the=20
conditions). For debugging purposes you can view such events in the =
event trace=20
but there'd be little point in restarting=20
them.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001>Kind =
regards,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001>
<P><B><FONT face=3DArial color=3D#000080>Alan Rickayzen</FONT></B> =
<BR><FONT=20
face=3DCourier color=3D#808080>WebFlow Product Manager</FONT> =
<BR><B><FONT=20
face=3DCourier color=3D#808080 size=3D1>SAP AG</FONT></B> </P>
<P><FONT face=3DCourier color=3D#808080 size=3D1>Techdev</FONT><B></B> =
<BR><FONT=20
face=3DCourier color=3D#808080 size=3D1>Neurottstra=DFe 15 =
</FONT><BR><FONT face=3DCourier=20
color=3D#808080 size=3D1>69190 Walldorf </FONT><BR><BR><FONT =
face=3DCourier=20
color=3D#808080 size=3D1>E-mail =
alan.rickayzen@sap.com</FONT> </P>
<P><FONT face=3DCourier color=3D#808080 size=3D1><A target=3D_blank=20
href=3D"http://service.sap.com/webflow">http://service.sap.com/webflow</=
A></FONT>=20
</P></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001></SPAN></FONT></FONT></FONT><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203185106-20092001> </SPAN></FONT></FONT></FONT><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Rankin, Andrew AJ=20
[mailto:Andrew.J.Rankin@BHPBilliton.com]<BR><B>Sent:</B> Donnerstag, =
September=20
20, 2001 4:45 AM<BR><B>To:</B> =
SAP-WUG@MITVMA.MIT.EDU<BR><B>Subject:</B> Event=20
Queues - Comments on Pros & Cons?<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<P><FONT face=3DArial size=3D2>Hi all,</FONT> </P>
<P><FONT face=3DArial size=3D2>From what I have read, event queues =
are available=20
to assist with performance where there is a likelihood of a large =
number of=20
the same event being created in a very short space of time. To date, =
I haven't=20
used them and haven't had problems, and I don't expect that to =
change. However=20
the other thing that also interests me is that you can use the event =
queue to=20
manage the case where event linkages end in an error, so that with =
the correct=20
settings in the event linkage, if necessary these events can be =
resubmitted=20
once the problem is fixed.</FONT></P>
<P><FONT face=3DArial size=3D2>We had the situation a while ago where =
a small=20
number of event linkage instances went into error because a table =
space was=20
filled. Fortunately it was picked up early, and I only had to =
recreate a small=20
number of these events by hand. If the number was large, I don't know =
how I=20
would manage to kick off all the worklfows required without spending =
many=20
tedious hours doing it manually. Perhaps this was a freak occurrence, =
but it=20
makes me think that I should switch on the event queue for =
everything, to=20
cover this risk in the future. So what is the downside to using the =
event=20
queue, if any?</FONT></P>
<P><FONT face=3DArial size=3D2>The other thing I'm wondering though =
is if I do=20
switch it on, will it see event linkages that end with exception due =
to a=20
start condition killing it (which we want to happen)? What else do I =
need to=20
consider?</FONT></P>
<P><FONT face=3DArial size=3D2>I thank you for any expert =
advice.</FONT> </P>
<P><FONT face=3DArial size=3D2>Andrew Rankin.</FONT> </P><BR>
<P><FONT face=3DArial size=3D2>EOM </FONT></P>
<P><FONT face=3DArial size=3D2>NOTICE - This message and any attached =
files may=20
contain information that is confidential and/or subject of legal =
privilege=20
intended only for use by the intended recipient. If you are not the =
intended=20
recipient or the person responsible for delivering the message to the =
intended=20
recipient, be advised that you have received this message in error =
and that=20
any dissemination, copying or use of this message or attachment is =
strictly=20
forbidden, as is the disclosure of the information therein. If =
you have=20
received this message in error please notify the sender immediately =
and delete=20
the message.</FONT></P></BLOCKQUOTE></BODY></HTML>