<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=909543921-09022006><FONT face=Arial
color=#0000ff size=2>Ah - don't think you have the critical terminating event
functions at the workflow header level in 4.6C.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=909543921-09022006><FONT face=Arial
color=#0000ff size=2>Again - always helpful to tell us what release you are on
whenever you post a question.</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>The
information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the person
or entity to which it is addressed. If you are not the intended recipient, you
are hereby notified that any distribution, copying, review, retransmission,
dissemination or other use of this electronic transmission or the information
contained in it is strictly prohibited. If you have received this electronic
transmission in error, please immediately contact the sender to arrange for the
return of the original documents. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Electronic
transmission cannot be guaranteed to be secure and accordingly, the sender does
not accept liability for any such data corruption, interception, unauthorized
amendment, viruses, delays or the consequences thereof.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Any views
expressed in this electronic transmission are those of the individual sender,
except where the message states otherwise and the sender is authorized to state
them to be the views of SAP AG or any of its subsidiaries. SAP AG, its
subsidiaries, and their directors, officers and employees make no representation
nor accept any liability for the accuracy or completeness of the views or
information contained herein. Please be aware that the furnishing of any pricing
information/ business proposal herein is indicative only, is subject to change
and shall not be construed as an offer or as constituting a binding agreement on
the part of SAP AG or any of its subsidiaries to enter into any relationship,
unless otherwise expressly stated. </FONT></SPAN></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Glauco
Kubrusly<BR><B>Sent:</B> Thursday, 09 February 2006 11:55 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Workflow: How to re-schedule wi's
not executed<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Jocelyn,</DIV>
<DIV> </DIV>
<DIV>I'm developing in a 4.6c system. </DIV>
<DIV> </DIV>
<DIV>I'm trying the Trygve's solution for a while.</DIV>
<DIV>Do you know if your solution will work fine here ? I had already reard
about it.<BR></DIV>
<DIV>Thanks,</DIV>
<DIV>Glauco</DIV>
<DIV><BR><B><I>"Dart, Jocelyn" <jocelyn.dart@sap.com></I></B>
escreveu:</DIV>
<BLOCKQUOTE class=replbq
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">There's
a much better way than that if you are in a 6.20 system (e.g. R/3 4.7) or
above, as follows:<BR><BR>a) create a multiline container element to hold your
agents<BR>b) start by filling it with the original agent<BR>c) use the
multiline container element (via the expression option) as the agents of your
step<BR>d) create an event e.g. "MoreAgentsAdded" and in the BASIC DATA (hat
icon in SWDD) of your workflow<BR>use the version-dependent > Events tab to
listen for this event and respond by "re-evaluating agents in active work
items"<BR>e) use modelled deadline on requested end of your step to add the
supervisor to the multiline container element<BR>and raise your
"MoreAgentsAdded" event.<BR>f) use modelled dealine on latest end of your step
to add the manager to the multiline container element and <BR>raise your
"MoreAgentsAdded" event again. <BR><BR><BR>Much cleaner and simpler, no nasty
forks or loops, everything is nicely and clearly logged, plus the original
agent can still see and action the task even when escalated - which is much
more useful as instead of having only one person looking at it at any one
time, you have more people who can action it as the work item becomes
increasingly overdue. <BR><BR>Also as a general recommendation I would talk to
your users about their escalation process - if a supervisor is busy, then
his/her manager is even more busy. In general its better to send it to group
of "shared services" people than up the management hiera! rchy.
<BR><BR><BR>Regards,<BR>Jocelyn Dart<BR>Senior Consultant<BR>SAP Australia Pty
Ltd.<BR>Level 1/168 Walker St.<BR>North Sydney <BR>NSW, 2060<BR>Australia<BR>T
+61 412 390 267<BR>M + 61 412 390 267<BR>E
jocelyn.dart@sap.com<BR>http://www.sap.com<BR><BR>The information contained in
or attached to this electronic transmission is confidential and may be legally
privileged. It is intended only for the person or entity to which it is
addressed. If you are not the intended recipient, you are hereby notified that
any distribution, copying, review, retransmission, dissemination or other use
of this electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error, please
immediately contact the sender to arrange for the return of the original
documents. <BR>Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.<BR>Any views expressed in this electronic transmission
are those of the individual sender, except where the message states otherwise
and the sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
employees make no representation nor accept any liability for the accuracy or
completeness of the views or information contained herein. Please be aware
that the furnishing of any pricing information/ business proposal herein is
indicative only, is subject to change and shall not be construed as an offer
or as constituting a binding agreement on the part of SAP AG or any of its
subsidiaries to enter into any relationship, unless otherwise expressly
stated. <BR><BR><BR>-----Original Message-----<BR>From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf Of Trygve
Leivestad<BR>Sent: Thursday, 09 February 20! 06 7:47 PM<BR>To:
sap-wug@mit.edu<BR>Subject: RE: Workflow: How to re-schedule wi's not
executed<BR><BR>Hi !<BR><BR>One suggestion :<BR><BR>You could make a 3 branch
fork, one necessary.<BR>Branch 1 : The ordinary task to analyst.<BR>Branch 2 :
Task sent to supervisor, use requested start to delay it the <BR>wanted
days.<BR>Branch 3 : Task sent to manager, use requested start to delay it the
wanted <BR>days.<BR><BR>As soon as one have performed the task the other two
get logically deleted.<BR><BR>Regrds<BR>Trygve<BR><BR><BR>>From: Glauco
Kubrusly <GLAUCOKUBRUSLY@YAHOO.COM.BR><BR>>Reply-To: "SAP Workflow Users'
Group" <SAP-WUG@MIT.EDU><BR>>To: Process Control Step
<SAP-WUG@MIT.EDU><BR>>Subject: Workflow: How to re-schedule wi's not
executed<BR>>Date: Wed, 8 Feb 2006 21:02:47 +0000
(GMT)<BR>><BR>>Friends,<BR>><BR>>I need to use a 3 stage
re-schedule wi's not executed.<BR>>That's it:<BR>><BR>>If the analyst
didn't executed the wi, I have to re-sched! ule it to his <BR>>supervisor,
and if the manager didn't executed its wi, re-schedule it to <BR>>his
manager.<BR>><BR>>how can I do that
?<BR>><BR>><BR>><BR>><BR>>Glauco S.
Kubrusly<BR>><BR>>---------------------------------<BR>> Yahoo!
Search<BR>> Dê uma espiadinha e saiba tudo sobre o Big Brother
Brasil.<BR><BR><BR>>_______________________________________________<BR>>SAP-WUG
mailing
list<BR>>SAP-WUG@mit.edu<BR>>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></BLOCKQUOTE>
<DIV><BR></DIV>
<P>
<HR SIZE=1>
Yahoo! doce lar. <A
href="http://us.rd.yahoo.com/mail/br/tagline/homepage_set/*http://br.yahoo.com/homepageset.html">Faça
do Yahoo! sua homepage.</A></BODY></HTML>