RSWUWFML2 performance issue

Serge Boulay Serge.Boulay at n-spro.com
Mon Nov 15 11:03:33 EST 2004


Mark,
 
We did some testing using the options that you are suggesting but the =
thing
is that the high volume is on that one task for time sheet approval...
 
But like I said, it looks like it is the call to the function
SO_NEW_DOCUMENT_ATT_SEND_API1 that makes it slow.=20
 
Thanks.
 
Serge
 
-----Message d'origine-----
De=A0: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] De la part de
Griffiths, Mark
Envoy=E9=A0: 15 novembre 2004 10:40
=C0=A0: SAP-WUG at MITVMA.MIT.EDU
Objet=A0: Re: RSWUWFML2 performance issue
 
The report may take a long term to run the first time you use it.
 
Couple of ideas:
- Specify a start date in your variant - only check for items in the =
near
past when it is first run
- Use the job suffix function this means that when it runs it only gets
items since last time it ran.
- Restrict the task selection to only inform users for the tasks you are
actually using (and need notifying about).
- If you still have very high volumes create different variants based on
tasks, you can then spread the load between a couple of job runs.
 
Regards,
 
Mark
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Serge
Boulay
Sent: 15 November 2004 15:29
To: SAP-WUG at MITVMA.MIT.EDU
Subject: RSWUWFML2 performance issue
 
 
Hi All,
 
 
 
Does any one had an issue with the performance of RSWUWFML2 ? We had the
system with 17,000 work items in SWWWIHEAD and the program ran for ever. =
One
of the BASIS seems to think that it is the function
SO_NEW_DOCUMENT_ATT_SEND_API1.
 
 
 
I know that we could run the job more often but the client want to run =
it
once a day... And we are using CATS (time sheets) approval for around =
40,000
employees.
 
 
 
Any idea?
 
 
 
 
 
Thanks.
 
 
 
Serge Boulay
 
HR/Payroll & Workflow Consultant
 


More information about the SAP-WUG mailing list