Unusual Workflow execution times

[Munday,Sherie J.]

Ashish,
You might want to look at OSS Note 943270.  Don't know if it is relevant, but it has to do with timestamps.  We had to apply that note recently after updating our system with the latest support packs.  (We are on ECC 5)  The logs were not listing work items chronologically and SAP responded that they were experiencing time stamp problems.  The note has solved our issues. 
Best Wishes,
Sherie
 
Sherie Munday
Workflow Developer/Analyst
Air Products & Chemicals, Inc.
 
________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Glauco Kubrusly
Sent: Monday, December 11, 2006 4:08 PM
To: SAP Workflow Users' Group
Subject: Re: Unusual Workflow execution times


Hi,
 
I think if no problem about the workflow, it can happen with heavy systems I think.
 
You can use SWWL, SWWH and SWW_SARA, respective to choose if you want delete work items, work items history and archive work items. I think it can help you if your workflows trigger a lot of workitems and if they can have a lot of tasks and element containers...you can use it. But I've heard that is not sugestible using SWWL and SWWH because it can help on audit cases.
 
Then you can use SWW_SARA to archiving the work items with cancelled and completed status.
 
I think that BASIS can configure the maximum number of process running per time or maximum too....Try to see about it too. Because I think it can do the process run slow too or cause event losts.
 
good luck!

Ashish Paranjpe <aaparanjpe at gmail.com> escreveu:

	HI All,
	Please take a look at the attachment. The workflow background workitem was created at 14:31:33, execution started automatically at 14:31:33, the business logic should hardly take 5 seconds to execute.
	 
	But as seen in the log, There are two entries 
	Execution started at 18:43:47
	Workitem processing complete at 18:43:48
	 
	 
	What are the sort of system issues which could cause such a delay of 4 hrs. As said earlier, the business logic takes only 5 secs to execute.
	 
	This I believe is something to do with the workflow runtime performance.
	 
	 
	The problem is happening for all workflows irrespective of the business module.
	 
	If anyone of you has faced such a problem before, please let me know the solution to this.
	 
	Thanks in advance,
	Ashish
	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	


________________________________

Yahoo! Acesso Grátis <http://us.rd.yahoo.com/mail/br/tagline/freeisp/*http://br.acesso.yahoo.com>  - Internet rápida e grátis. Instale o discador agora! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061211/bd5675bd/attachment.htm