Old Error'd WF and how to handle them question

[Michael Pokraka]

Of course I couldn't agree more and perhaps I should add a disclaimer that I'm talking from a 4.6c system at the moment :-)
 
Thanks for the update.
 
Cheers
Mike
 
 
On Thu, Jun 05, 2003 at 02:06:40AM +0200, Dart, Jocelyn wrote:
> Hi Everyone,
> FYI Please note that there is a new WAPI in R3E that provides similar functionality to the internal function module mentioned
> below. That is - SAP_WAPI_ADM_WORKFLOW_CANCEL.
>
> As a general rule you should always use a WAPI rather than an internal function module as WAPIs are
> released for customer and supported across releases.  If you use SAP internal function modules there is
> always a significant risk that the function module will change without warning e.g. in a hotpack or on upgrade
> in ways that may either stop it working or even cause damage (e.g. if it needs to be used in a certain sequence
> or is made obsolete and does not update new/existing tables in synch with other changes to the system).
>
> The number of WAPIs available has significantly increased in R3E - its about double the number of routines available
> in 4.6C including a bunch of administrator functions.  So please everyone, if you are using custom programs or
> user-exits and using internal function modules, make sure you flag these to be reviewed on upgrade.
>
> Regards,
>         Jocelyn Dart
> Consultant (SRM, EBP, Workflow)
> and co-author of the book
> "Practical Workflow for SAP"
> SAP Australia
> email: jocelyn.dart at sap.com
> phone: +61 412 390 267
> fax:   +61 2 9935 4880
>
>
>
>
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Thursday, 5 June 2003 1:50 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Old Error'd WF and how to handle them question
>
>
> 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?