Waiting step

[Christophe Compain]

Hi Jocelyn,
 
thanks to you (and to the other persons who replied to my message) for your
quick response.
 
Actually, I didn't explain my issue quite well :
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.
The problem was that the 'Requested start' functionality made me wait 30 minutes
even the first time the activity was executed (what I didn't want to occur).
 
I had a look to the Event Receiver functionality, but I had to specify an event
not a amount of time.
 
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.
 
Nevertheless, I really appreciated your idea of scheduled deadline job.
 
Regards,
Christophe
 
 
 
"Dart, Jocelyn" wrote:
 
> Hi Christophe,
> Alon means you want to make these settings in the "Requested Start"
> deadline area of the step you want to delay.
> I.e. You don't want the step to start until 30 minutes after it has
> been created.
>
> Remember that for this to work you must be running the deadline monitoring
> job SWWDHEX (which you can set up via transactions SWU3 or SWWA and SWWB).
> Also remember that the task won't be started exactly on the 30 minutes due
> to the way deadlines work.
>
> You have to think of it like this:
> a) Task scheduled to start in Time + 30 minutes.
> b) Option 1: Deadline runs on a case by case basis - deadline job scheduled
> to run just after Time + 30 minutes, job actually runs at Time + 30 minutes
> + time waiting in batch queue
> c) Option 2: Deadline runs periodically - e.g. every 15 minutes.  Best case
> - job runs just after Time + 30 minutes, job actually runs at Time + 30
> minutes
> + time waiting in batch queue.  Worst case - job ran just before Time + 30
> minutes,
> so deadline is picked up by next job at Time + 45 minutes, job actually runs
> at
> Time + 45 minutes + time waiting in batch queue.
>
> Remember that if you are setting and checking a lot of deadlines that
> periodic
> monitoring has performance advantages.
>
> Whether you are already using deadlines or not, it might be wise to read up
> on the
> R/3 library info in this area.  In particular if you are currently on case
> by case
> monitoring you might want to do some calculations to see whether this new
> deadline
> means you should swap to periodic monitoring.
>
> If you are not sure, suggest you and your workflow administrator keep an eye
> on the
> deadline job when your new workflow goes live to see if you are flooding the
> system
> with deadline jobs.
>
> It might be wise to discuss how well the batch queue is performing in
> production with
> your system administrator also.
>
> Regards,
>         Jocelyn Dart
> Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
> SAP Australia
> Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
> Tel: +61 412 390 267
> Fax: +61 2 9935 4880
>
> -----Original Message-----
>> From: Raskin Alon x8008 [mailto:ARaskin at Citipower.com.au]
> Sent: Tuesday, 13 March 2001 10:30 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Waiting step
>
> Hi Christophe,
>
> I think this will do what you want:
>
> *       Find the step in your WF which you want to start in 30 mins
> *       Select Creation of WI
> *       Type in 30 into offset and make sure that minutes is selected.
>
> Activate your WF
>
> Have a good day,
>
> Alon
>
>                 -----Original Message-----
>                 From:   Christophe Compain
> [mailto:Christophe.Compain at cie.etat.lu]
>                 Sent:   Monday, 12 March 2001 11:47 PM
>                 To:     SAP-WUG at MITVMA.MIT.EDU
>                 Subject:        Waiting step
>
>                 Hi.
>
>                 My question is very simple : What is the best way to
> implement a waiting
>                 step of 30 minutes in my workflow ?
>                 Actually, I don't want it to be event-driven.
>
>                 Has somebody got an idea ?
>
>                 Thanks in advance,
>                 Christophe
>
>                 --
>                 Christophe Compain
>                 SAP consultant
>                 Deloitte Consulting Luxembourg
>                 Til. : + 352 22 99 90 203
>                 Fax  : + 352 22 99 90 240
>                 email: Christophe.Compain at cie.etat.lu
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This email message has been swept for the presence of computer viruses.
>
> CitiPower Pty ACN 064 651 056
> **********************************************************************
 
--
Christophe Compain
SAP consultant
Deloitte Consulting Luxembourg
Til. : + 352 22 99 90 203
Fax  : + 352 22 99 90 240
email: Christophe.Compain at cie.etat.lu
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010315/7615db34/attachment.htm