2 year wait vs Batch Report

[Tiwari, Rammanohar]

But then in that case, I think you need to run it daily and can't be run with an interval of a week or a month.

If you run it monthly then there is a chance that a few of your workflow instances might miss the deadlines ( might get delayed by 29 days in the worst case scenario ).

I think, scheduling the same batch report after 2 years from the date of first instance ( run )of workflow, and to be run daily from that time onwards, can be a good option.
As per the requirement, running this report, before completing 2 years from the first wf run, is a wastage. And running it everyday after 2 years ( from the first workflow run ) is essential.

But the first schedule will require a manual intervention. Put it somewhere in the project plan :-)

Thanks,
Ram
www.rmtiwari.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Workflow
Sent: Friday, May 06, 2005 12:16 PM
To: SAP Workflow Users' Group
Subject: AW: 2 year wait vs Batch Report


Alon,
I agree with Jeff here.  A batch job which is scheduled in two years time
and/or a workflow waiting to react after two years would be prone to getting
cleaned up or weeded out by a well intentioned system or workflow
administrator.  Batch jobs can also be reset into planned mode after release
upgrades and would have to be re-released occasionaly during that two year
wait period.

-----Ursprüngliche Nachricht-----
Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]Im Auftrag
von Jeff Rappaport
Gesendet: Donnerstag, 5. Mai 2005 23:47
An: SWUG
Betreff: Fw: 2 year wait vs Batch Report



-----Original Message-----
From: "Rappaport, Jeff " <jrappaport at mh.co.durham.nc.us>
Date: 	Thu, 5 May 2005 13:28:51
To:<Jeff at Business-Workflow.com>
Subject: RE: 2 year wait vs Batch Report

Alon,

   Read a few of the other replies that focused on the resources used,
which was great, but the first thought that went through my mind when I
read your questions was more on daily reporting. If reports/tranx are
run on all WF's they will keep appearing & may need to be constantly
weeded out. I would opt for the regular Batch Pgm. without using WF.
Since these things only get deleted every 2 years, maybe you wouldn't
even have to run the Pgm. every day, maybe once a week or month will be
good enough. Just my 2 cents....

Jeff Rappaport
www.Business-Workflow.com


-----Original Message-----
From: "Alon Raskin" <araskin at 3i-consulting.com>
Date: Thu, 5 May 2005 07:55:48
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 <mailto: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


Jeffrey A. Rappaport
Business Workflow, LLC
voice: (732)355-0123
fax:   (509)757-4144
email: Jeff at Business-Workflow.com
web:   www.Business-Workflow.com




Jeffrey A. Rappaport
Business Workflow, LLC
voice: (732)355-0123
fax:   (509)757-4144
email: Jeff at Business-Workflow.com
web:   www.Business-Workflow.com
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug




_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

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.