<!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 5.00.3103.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><BR><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>Hi
Pallavika,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>From a
previous reply:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=329390422-22082001>Remember that for this to work you must be running the
deadline monitoring<BR>job SWWDHEX (which you can set up via transactions SWU3
or SWWA and SWWB). <BR>Also remember that the task won't be started exactly on
the 30 minutes due <BR>to the way deadlines work. </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>You
have to think of it like this:<BR>a) Task scheduled to start in Time + 30
minutes.<BR>b) Option 1: Deadline runs on a case by case basis - deadline job
scheduled<BR>to run just after Time + 30 minutes, job actually runs at Time + 30
minutes<BR>+ time waiting in batch queue <BR>c) Option 2: Deadline runs
periodically - e.g. every 15 minutes. Best case<BR>- job runs just after
Time + 30 minutes, job actually runs at Time + 30 minutes<BR>+ time waiting in
batch queue. Worst case - job ran just before Time + 30 minutes,<BR>so
deadline is picked up by next job at Time + 45 minutes, job actually runs at
<BR>Time + 45 minutes + time waiting in batch queue.</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=329390422-22082001>Remember that if you are setting and checking a lot of
deadlines that periodic<BR>monitoring has performance advantages.
</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=329390422-22082001>Whether you are already using deadlines or not, it
might be wise to read up on the<BR>R/3 library info in this area. In
particular if you are currently on case by case<BR>monitoring you might want to
do some calculations to see whether this new deadline<BR>means you should swap
to periodic monitoring. </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>If you
are not sure, suggest you and your workflow administrator keep an eye on the
<BR>deadline job when your new workflow goes live to see if you are flooding the
system<BR>with deadline jobs. </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>It
might be wise to discuss how well the batch queue is performing in production
with<BR>your system administrator also. <BR>Regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=329390422-22082001>
<DIV style="HEIGHT: 90px; WIDTH: 374px"><FONT size=2>
<TABLE>
<TBODY>
<TR>
<TD></TD></FONT>
<TD>
<DIV><FONT size=2><FONT color=#0000ff>Jocelyn Dart</FONT> <BR><FONT
color=#0000ff>Consultant (EBP, BBP, Ecommerce, Internet Transaction
Server, Workflow)</FONT> <BR><FONT color=#0000ff>SAP
Australia</FONT></FONT></DIV>
<DIV><FONT color=#0000ff><FONT size=2>Email </FONT><A
href="mailto:jocelyn.dart@sap.com"><FONT
size=2>jocelyn.dart@sap.com</FONT></A><BR><FONT size=2>Tel: +61<SPAN
class=153385400-09052000> 412 390 267</SPAN><BR>Fax: +61 2 9935
4880</FONT></FONT></DIV></TD></TR></TBODY></TABLE></DIV></SPAN></FONT></DIV>
<BLOCKQUOTE>
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Pallavika Patel
[mailto:PATEL_PALLAVIKA_P_NONLILLY@LILLY.COM]<BR><B>Sent:</B> Thursday, 23
August 2001 12:05 AM<BR><B>To:</B> SAP-WUG@MITVMA.MIT.EDU<BR><B>Subject:</B>
Re: WS Workflow Template transport problem.<BR><BR></DIV></FONT><BR><FONT
face=sans-serif size=2>Hello workflow Gurus</FONT> <BR><FONT face=sans-serif
size=2> I am not sure what is going on.</FONT> <BR><FONT
face=sans-serif size=2>I have a requested start date in my workflow
single step task. Basically I would like to wait for couple minute
before the next step takes place.</FONT> <BR><FONT face=sans-serif size=2>So,
I have created a single step task with the requested start with
Refer.date/time = Work item creation and time = 3 minutes.</FONT>
<BR><BR><FONT face=sans-serif size=2>Everything was working fine. Step
was waiting 3 minuets before it starts. But lately it takes
around 20 minutes or so to start.</FONT> <BR><FONT face=sans-serif size=2>And
what has happened is for some reason dead line monitoring job SWWDHEX was
cancelled and I had to restart.</FONT> <BR><BR><FONT face=sans-serif size=2>Is
this the job which takes care of requested start also? I am not using actual
dead line feature for any work items. I am just using few steps with requested
start. (Delay start by couple minutes)</FONT> <BR><BR><FONT face=sans-serif
size=2>How can I set up workflow so that task with requested start 3 minutes
actually starts after 3 minutes instead of 20 minutes????</FONT> <BR><BR><FONT
face=sans-serif size=2> Schedule backgr. job for case-specific d</FONT>
<BR><FONT face=sans-serif size=2> Optional: Schedule permanent deadline
monitoring</FONT> <BR><BR><FONT face=sans-serif size=2>I have used Optional
with
</FONT><BR><FONT face=sans-serif size=2> Periodic dead line
monitoring flag checked and
</FONT> <BR><FONT face=sans-serif size=2> Interval until next
deadline check = 20 minutes ( I think that is the recommendation)</FONT>
<BR><BR><FONT face=sans-serif size=2>should I use instead Schedule backgr. job
for case-speciffic deadline monitoring???</FONT> <BR><BR><FONT face=sans-serif
size=2>Any help will be appreciated.</FONT> <BR><FONT face=sans-serif
size=2>
</FONT> <BR><FONT face=sans-serif size=2>Pallavika
Patel<BR>433-3157</FONT></BLOCKQUOTE></BODY></HTML>