WS Workflow Template transport problem.

[Dart, Jocelyn]

Hi Pallavika,
>From a previous reply:
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 (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
-----Original Message-----
From: Pallavika Patel [mailto:PATEL_PALLAVIKA_P_NONLILLY at LILLY.COM]
Sent: Thursday, 23 August 2001 12:05 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WS Workflow Template transport problem.
 
 
 
Hello workflow Gurus
    I am not sure what is going on.
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.
So, I have created a single step task with the requested start with
Refer.date/time = Work item creation and time = 3 minutes.
 
Everything was working fine. Step  was waiting  3 minuets  before it starts.
But lately it takes around 20 minutes or so to start.
And what has happened is for some reason dead line monitoring job SWWDHEX
was cancelled and I had to restart.
 
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)
 
How can I set up workflow so that task with requested start 3 minutes
actually starts after 3 minutes instead of 20 minutes????
 
 Schedule backgr. job for case-specific d
 Optional: Schedule permanent deadline monitoring
 
I have used Optional with
 Periodic dead line monitoring flag checked and
 Interval until next deadline check = 20 minutes ( I think that is the
recommendation)
 
should I use instead Schedule backgr. job for case-speciffic deadline
monitoring???
 
Any help will be appreciated.
 
Pallavika Patel
433-3157
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010823/5e620605/attachment.htm