<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Jocelyn,
<p>thanks to you (and to the other persons who replied to my message) for
your quick response.
<p>Actually, I didn't explain my issue quite well :
<br>I wanted an activity to be executed, and, in case it failed (because
of a blocked document that is used by this activity), I wanted my WF to
wait 30 minutes and start again to carry on the activity.
<br>The problem was that the 'Requested start' functionality made me wait
30 minutes even the <u>first time</u> the activity was executed (what I
didn't want to occur).
<p>I had a look to the Event Receiver functionality, but I had to specify
an event not a amount of time.
<p>I thought it over again and I finally added an activity with an 'empty'
method and used the 'Requested start' functionality. It is now running
in our productive run.
<p>Nevertheless, I really appreciated your idea of scheduled deadline job.
<p>Regards,
<br>Christophe
<br>
<br>
<p>"Dart, Jocelyn" wrote:
<blockquote TYPE=CITE>Hi Christophe,
<br>Alon means you want to make these settings in the "Requested Start"
<br>deadline area of the step you want to delay.
<br>I.e. You don't want the step to start until 30 minutes after it has
<br>been created.
<p>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.
<p>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
<br>minutes
<br>+ time waiting in batch queue. Worst case - job ran just before
Time + 30
<br>minutes,
<br>so deadline is picked up by next job at Time + 45 minutes, job actually
runs
<br>at
<br>Time + 45 minutes + time waiting in batch queue.
<p>Remember that if you are setting and checking a lot of deadlines that
<br>periodic
<br>monitoring has performance advantages.
<p>Whether you are already using deadlines or not, it might be wise to
read up
<br>on the
<br>R/3 library info in this area. In particular if you are currently
on case
<br>by case
<br>monitoring you might want to do some calculations to see whether this
new
<br>deadline
<br>means you should swap to periodic monitoring.
<p>If you are not sure, suggest you and your workflow administrator keep
an eye
<br>on the
<br>deadline job when your new workflow goes live to see if you are flooding
the
<br>system
<br>with deadline jobs.
<p>It might be wise to discuss how well the batch queue is performing in
<br>production with
<br>your system administrator also.
<p>Regards,
<br> Jocelyn Dart
<br>Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
<br>SAP Australia
<br>Email jocelyn.dart@sap.com <<a href="mailto:jocelyn.dart@sap.com">mailto:jocelyn.dart@sap.com</a>>
<br>Tel: +61 412 390 267
<br>Fax: +61 2 9935 4880
<p>-----Original Message-----
<br>From: Raskin Alon x8008 [<a href="mailto:ARaskin@Citipower.com.au">mailto:ARaskin@Citipower.com.au</a>]
<br>Sent: Tuesday, 13 March 2001 10:30 AM
<br>To: SAP-WUG@MITVMA.MIT.EDU
<br>Subject: Re: Waiting step
<p>Hi Christophe,
<p>I think this will do what you want:
<p>* Find the step in your WF which
you want to start in 30 mins
<br>* Select Creation of WI
<br>* Type in 30 into offset and make
sure that minutes is selected.
<p>Activate your WF
<p>Have a good day,
<p>Alon
<p>
-----Original Message-----
<br>
From: Christophe Compain
<br>[<a href="mailto:Christophe.Compain@cie.etat.lu">mailto:Christophe.Compain@cie.etat.lu</a>]
<br>
Sent: Monday, 12 March 2001 11:47 PM
<br>
To: SAP-WUG@MITVMA.MIT.EDU
<br>
Subject: Waiting step
<p>
Hi.
<p>
My question is very simple : What is the best way to
<br>implement a waiting
<br>
step of 30 minutes in my workflow ?
<br>
Actually, I don't want it to be event-driven.
<p>
Has somebody got an idea ?
<p>
Thanks in advance,
<br>
Christophe
<p>
--
<br>
Christophe Compain
<br>
SAP consultant
<br>
Deloitte Consulting Luxembourg
<br>
Til. : + 352 22 99 90 203
<br>
Fax : + 352 22 99 90 240
<br>
email: Christophe.Compain@cie.etat.lu
<p>**********************************************************************
<br>This email and any files transmitted with it are confidential and
<br>intended solely for the use of the individual or entity to whom they
<br>are addressed. If you have received this email in error please notify
<br>the system manager.
<p>This email message has been swept for the presence of computer viruses.
<p>CitiPower Pty ACN 064 651 056
<br>**********************************************************************</blockquote>
<p>--
<br>Christophe Compain
<br>SAP consultant
<br>Deloitte Consulting Luxembourg
<br>Tél. : + 352 22 99 90 203
<br>Fax : + 352 22 99 90 240
<br>email: Christophe.Compain@cie.etat.lu
<br> </html>