2 year wait vs Batch Report

[Tiwari, Rammanohar]

I think there might be another option ( Not sure though ) :
 
Just after that step in your workflow put another step which will schedule a Batch Job (FM BP_JOB_CREATE)  with release date = sy-datum + 2 years.
I am not sure but system restart should not affect it. 
 
The Batch job will then trigger an event ( after two years )  to re-start the terminated workflow.
 
Thanks,
Ram
 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of Alon Raskin
Sent: Thursday, May 05, 2005 5:26 PM
To: SAP Workflow Users' Group
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:  <mailto:araskin at 3i-consulting.com> araskin at 3i-consulting.com

w: http://www.3i-consulting.com


This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050505/4d385778/attachment.htm