Workflow: How to re-schedule wi's not executed

Thu Feb 9 16:40:50 EST 2006

Ah - don't think you have the critical terminating event functions at the workflow header level in 4.6C.
Again - always helpful to tell us what release you are on whenever you post a question.

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 

Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.

Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Glauco Kubrusly
Sent: Thursday, 09 February 2006 11:55 PM
To: SAP Workflow Users' Group
Subject: RE: Workflow: How to re-schedule wi's not executed

Jocelyn,

I'm developing in a 4.6c system. 

I'm trying the Trygve's solution for a while.
Do you know if your solution will work fine here ? I had already reard about it.

Thanks,
Glauco

"Dart, Jocelyn" <jocelyn.dart at sap.com> escreveu:

	There's a much better way than that if you are in a 6.20 system (e.g. R/3 4.7) or above, as follows:

	a) create a multiline container element to hold your agents
	b) start by filling it with the original agent
	c) use the multiline container element (via the expression option) as the agents of your step
	d) create an event e.g. "MoreAgentsAdded" and in the BASIC DATA (hat icon in SWDD) of your workflow
	use the version-dependent > Events tab to listen for this event and respond by "re-evaluating agents in active work items"
	e) use modelled deadline on requested end of your step to add the supervisor to the multiline container element
	and raise your "MoreAgentsAdded" event.
	f) use modelled dealine on latest end of your step to add the manager to the multiline container element and 
	raise your "MoreAgentsAdded" event again. 

	Much cleaner and simpler, no nasty forks or loops, everything is nicely and clearly logged, plus the original agent can still see and action the task even when escalated - which is much more useful as instead of having only one person looking at it at any one time, you have more people who can action it as the work item becomes increasingly overdue. 

	Also as a general recommendation I would talk to your users about their escalation process - if a supervisor is busy, then his/her manager is even more busy. In general its better to send it to group of "shared services" people than up the management hiera! rchy. 

	Regards,
	Jocelyn Dart
	Senior Consultant
	SAP Australia Pty Ltd.
	Level 1/168 Walker St.
	North Sydney 
	NSW, 2060
	Australia
	T +61 412 390 267
	M + 61 412 390 267
	E jocelyn.dart at sap.com
	http://www.sap.com

	The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 
	Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.
	Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 

	-----Original Message-----
	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Trygve Leivestad
	Sent: Thursday, 09 February 20! 06 7:47 PM
	To: sap-wug at mit.edu
	Subject: RE: Workflow: How to re-schedule wi's not executed

	Hi !

	One suggestion :

	You could make a 3 branch fork, one necessary.
	Branch 1 : The ordinary task to analyst.
	Branch 2 : Task sent to supervisor, use requested start to delay it the 
	wanted days.
	Branch 3 : Task sent to manager, use requested start to delay it the wanted 
	days.

	As soon as one have performed the task the other two get logically deleted.

	Regrds
	Trygve

	>From: Glauco Kubrusly 
	>Reply-To: "SAP Workflow Users' Group" 
	>To: Process Control Step 
	>Subject: Workflow: How to re-schedule wi's not executed
	>Date: Wed, 8 Feb 2006 21:02:47 +0000 (GMT)
	>
	>Friends,
	>
	>I need to use a 3 stage re-schedule wi's not executed.
	>That's it:
	>
	>If the analyst didn't executed the wi, I have to re-sched! ule it to his 
	>supervisor, and if the manager didn't executed its wi, re-schedule it to 
	>his manager.
	>
	>how can I do that ?
	>
	>
	>
	>
	>Glauco S. Kubrusly
	>
	>---------------------------------
	> Yahoo! Search
	> Dê uma espiadinha e saiba tudo sobre o Big Brother Brasil.

	>_______________________________________________
	>SAP-WUG mailing list
	>SAP-WUG at mit.edu
	>http://mailman.mit.edu/mailman/listinfo/sap-wug

	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug

________________________________

Yahoo! doce lar. Faça do Yahoo! sua homepage. <http://us.rd.yahoo.com/mail/br/tagline/homepage_set/*http://br.yahoo.com/homepageset.html> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060210/24f5521d/attachment.htm