Are there any cons of scheduling SWWERRE

[Edwin Mukusha]

The only items that come to mind are; 
- make sure that the job is running under wf-batch
- also make sure that you have maintained the workflow system 
administrator (tip: you can forward mails for items that go into errors to 
yourself)
- workitems that fail to be auto-restarted using SWWERRE will show up on 
transaction: SWI2_DIAG where you have the option of restarting them if it 
makes sense.

Lastly make good use of the power of this job by programming custom 
methods that may need to be restarted automatically in the event of a 
temporary error such as a locked record. To make the method eligible for 
auto-retries create an exception that is of type "temporary error". 
As a workflow beginner I would program my own loops to perform retries for 
recoverable errors, until I discovered this.

Personally, I would not want the retry value to be more than five and the 
job to run more often than 20 mins and in total  exceed more than 2 hours 
since this value is global for all workflows.

I hope this helps,


Edwin Mukusha
University of Nebraska




"Khanna, Manish" <manish.khanna at amd.com> 
Sent by: sap-wug-bounces at mit.edu
06/19/2006 11:52 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>


To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
Are there any cons of scheduling SWWERRE






Hi,
 
Is there something that we should take care of before scheduling SWWERRE 
in production? We are at 4.6c and planning to schedule the job with 
default values (20 min and 3 retries).
 
Regards,
Manish_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060623/1726204b/attachment.htm