SAP-WUG Digest, Vol 6, Issue 9

[Peter Roehlen]

Hi Alon,
 
Just thought I'd kick in my two cents :)
 
I've had a quick look at program RSWWDHEX (the Deadline monitoring job) which I beleive is the relevant one for your proposed 2 year wait job.  It seems to be very efficient and only reads table SWWWIDH using a date (with an index) to see which work items have reached their deadline.  I can't see how you could write something that was much more efficient than this.  
 
The only caveat I add to this is that the deadline monitoring job typically runs several times an hour as opposed the 'nightly batch job' you referred to.  I wouldn't be too concerned about this unless the volume of waiting workflows is huge.
 
Cheers
 
Peter Roehlen.

 
Date: Thu, 5 May 2005 07:55:48 -0400
From: "Alon Raskin" <araskin at 3i-consulting.com>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Subject: 2 year wait vs Batch Report

Hi Everyone,

I would love to hear peoples opinions on this issue.

We have a situation where a workflow has to do update a field and then wait for 2 years before clearing that field. There are two possibilities to this issue.

1. Put in a 2 year wait step
2. Terminate the workflow and run a nightly batch job which would query some table and determine if 2 years have passed and then reset the field accordingly.

Currently I am leaning towards option 1 as I really don't see a difference in option 1 and option 2. Ultimately they are all just batch jobs which check dates and then do some processing. The volumes here are very low.

Your thoughts?

Alon Raskin
e: araskin at 3i-consulting.com 
w: http://www.3i-consulting.com
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



---------------------------------
Find local movie times and trailers on Yahoo! Movies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050505/cc452bde/attachment.htm