RE: RE : P. requisition - release refused

[Mark Pyc]

G'day Zsolt,

If you wish changes not relevant to the release strategy to trigger new 
instances of the Workflow you need to handle it yourself. The classic for 
this is Purchasing Group which is important in terms of Agents but not 
necessarily included in the Release Strategy.

If you have a look through the archives, you may find a few discussions on 
this.

You need to decide which changes are relevant to the WF process, and how the 
process should react. It may be that you can filter and ignore some changes 
all together. Others will only require agent redetermination (possible in 
version 610 upwards I think). If you do need to restart the process you'll 
need to either raise the ReleaseStepCreated event yourself within the 
workflow or possibly define another custom event which will also trigger the 
Workflow.

There is no standard solution for this one.

Have fun,
Mark

From: Márton Zsolt <Zsolt.Marton at t-systems.co.hu>
Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Subject: RE:  RE : P. requisition - release refused
Date: Mon, 13 Dec 2004 16:10:36 +0100

Hi Thomas!
I know that and my aim is to find just only one specific user who can work 
with the work item. The problem is: after executing the workitem no other 
workflow is started, because the strategy is the same. He's only modifying 
the purchasing date which is not relevant in the strategy.


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of 
Thomas Verhulst
Sent: Monday, December 13, 2004 3:23 PM
To: SAP Workflow Users' Group; Workflow fórum
Subject: RE : P. requisition - release refused

Hi Zsolt,

The role defines responsible agents for the task out of a set of possible 
agents. By defining that the task is a general one, you set the possible 
agents set to all the users. Means that the role will select a group of 
agent inside the set of all the users. So you have to put general task 
anyway, otherwise it will try to select responsible agents out of nothing--> 
no agent found for this task.

Regards,

Thomas Verhulst
OpenHR

	-------- Message d'origine--------
	De: Márton Zsolt [mailto:Zsolt.Marton at T-SYSTEMS.CO.HU]
	Date: lun. 13/12/2004 14:33
	À: Workflow fórum
	Cc:
	Objet: P. requisition - release refused



	Hi all!



	We are in 4.6c and  are using the standard workflow for the requisition 
relese, with exeption: the TS20000161 task is not a general task, is 
assigned to a developed role.

	As I know, if the requisition is refused and after that changed, a new 
workflow must be started. But after the change of the requisition nothing 
happens.

	It's could be something in the MM customizing or in the workflow.



	Regards

	Zsolt


_______________________________________________
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