Old Error'd WF and how to handle them question

Michael Pokraka workflow at quirky.me.uk
Wed Jun 4 11:49:41 EDT 2003


Cancel them. Later versions of SWI2_DIAG (from some 4.6c hotpack onwards) doesn't even start with a default date range - thus making it a PITA to work with once you reach over 50,000 errors (current day's errors takes 70-90 seconds, over a month's date range and we start to hit timeouts).
In fact most admin-type transactions, as well as SBWP start to crawl.
 
I've created a custom report to do a SWW_WI_ADMIN_CANCEL on old items as they will only then be archived.
 
Cheers
Mike
 
 
On Wed, Jun 04, 2003 at 09:02:29AM -0500, Rick Sample wrote:
> We have been live for a few months. We have many error'd Wfs for many
> reason.
> What is the normal procedure for handling these? Like old Sale Orders
> Wf that
> are just sitting in error status but these Sales Orders are completed.
>
> Just leave them in error'd state, archive, what?
> Performance issues?
 


More information about the SAP-WUG mailing list