Help with workflow deadlines

[Sherman S. Wright]

Hi Jocelyn (and all) -
 
Thanks to you (and David and Peter) for your help and suggestions.  However, I'm
still having problems getting this implemented.  For testing purposes, I have
changed the deadlines to hours, instead of days, but I'm getting no results.
 
Let's just concentrate on the Latest End for this mail (I'll probably need a
separate one for the Requested End...).  I modified our task Requisition Release
to have a Latest End of Work item creation + 45 hours.  The modeled event name
was Latest End Reached, which then continues to a Process control step called
Requisition Item Rejected, which has the process control function of "Cancel
Work Item" with the workflow step 125, which is "Requisition Release Refused".
The subsequent event is "Requisition Item Rejected".
 
 I have processed over 100 PR lines, which all show in SWI2_DEAD, but they are
all still in "READY" status.  The SWWDHEX job is definitely running.  What am I
missing?
 
Thanks for any help you can offer...
 
Regards,
Sherman
 
 
"Dart, Jocelyn" wrote:
 
> Hi Sherman,
> As a variation on David and Peter's suggestions how about:
>
> 1) Using a modeled deadline on REQUESTED END after workitem + 3 days to loop
> through
>    the send mail notification with requested start of workitem + 3 days.
> You could perhaps loop until a valid
>    approve/reject value has been returned to the workflow container.
>
> 2) Using a modeled deadline on LATEST END after workitem + 45 days to kill
> the original workitem (thereby triggering
>    the processing obsolete event) and set the status to rejected after
> processing obsolete. Setting the status to
>    rejected would then terminated the requested end loop.
>
> This is similar to Peter's approach but has the advantage of not starting
> the loop at all
> unless the agent fails the first deadline, resulting in less workitems being
> created if the
> agent reacts in a timely manner in the first place.
>
> 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: Roehlen, Peter [mailto:PRoehlen at powercor.com.au]
> Sent: Wednesday, 11 April 2001 3:39 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Help with workflow deadlines
>
> Hi Sherman,
>
> You could create a fork with two parrallel branches (with one branch
> required to finish.)  In one branch you put your approval step with the
> deadline monitoring set to the 45 days maximum after which the workitem is
> cancelled.  In the other branch, you have a send mail step in a loop.  You
> need to create a date and time container that you initialise before and
> inside the loop to the current system date/time.  Then in your send mail
> step you have the requested start set to your container values + 3 days.
>
> Every three days the send mail step will be processed until the workitem in
> the other branch is completed (which will terminate the fork).
>
> Hope this is of value.
>
> Cheers
>
> Peter Roehlen
> Team Lead - SAP Technical & Development
> Powercor Australia Ltd
> (03) 5430 4704 / 0409 950 263
>
> -----Original Message-----
>> From: Sherman S. Wright [mailto:swright at lsil.com]
> Sent: Wednesday, 11 April 2001 7:59
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Help with workflow deadlines
>
> Hi -
>
> We have a workflow for approval of Purchase Requisition lines, that
> currently is set to send a deadline notification after 72 hours.  What
> we'd like to do is have it send a notification every 3 days (3, 6, 9,
> 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, and 42 days) to someone who is
> not processing a work item.  Then we'd like the item automatically
> rejected if there is no activity (work item not completed) at 45 days.
> Anyone have any idea how we could accomplish both of these?  Any help
> would be greatly appreciated, since I'm trying to get this done in
> development by April 20...
>
> Regards,
> Sherman
> **********************************************************************
> Powercor Australia Ltd. This email and any file attachments 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 tell us immediately by return email and delete the
> document.
> **********************************************************************