<BODY><P></P>
<P><B>Hi Baskaran,</B></P>
<P><STRONG>There is also the UWL based substitutions that are user/logon id based and are not liked to the backend system.</STRONG></P>
<P><STRONG>Jerry</STRONG> </P>
<P><B>----- Original Message -----</B></P>
<P></P><B>From</B>: Rick Sample <Rick.Sample@gbe.com>
<P></P><B>Date</B>: Thursday, March 2, 2006 8:57 am
<P></P><B>Subject</B>: RE: Subsitution and possible agents
<P></P>
<P></P>> Baskaran, <BR>> Just to expand on this topic... <BR>> <BR>> 1. You can sub to anyone. <BR>> <BR>> 2. No authorization checks are made until task is executed. <BR>> <BR>> 3. The substitute may or may not have authorization for all tasks. <BR>> Here, you have <BR>> a few options that you implement to ensure WF does not error out <BR>> and/oruser does not see <BR>> certain tasks. Like HR WFs. <BR>> You can add "classifications" to the tasks and users can <BR>> substitute ALL <BR>> tasks or just these <BR>> specific classified tasks. <BR>> <BR>> If you do not use classifications, you will need to ensure that all <BR>> sub'd WFs have auth <BR>> checks (should be done anyway) and do something like display a message <BR>> that user <BR>> does not have auth for task. <BR>> <BR>> Also, two different types of substitutions exists. <BR>
> 1. Personal substitution. This is via UID and stored in HRUS_D2. <BR>> 2. Position substitution. HRP1001 <BR>> <BR>> Dig around a bit and let me know if you have any more questions. <BR>> There are reasons (which may not be readily apparent) why we have <BR>> different types. <BR>> <BR>> rick <BR>> <BR>> <BR>> >>> jocelyn.dart@sap.com 3/1/2006 23:57:02 >>> <BR>> Hi Baskaran, <BR>> Yes that is correct functionality. If you were expecting something <BR>> different then you haven't understood the substitution process <BR>> correctly. <BR>> The point of substitution is to allow someone to receive a work item <BR>> on <BR>> behalf of the original recipient - so effectively they are an <BR>> "implicit" <BR>> possible agent by their relationship to the original recipient. <BR>> <BR>> Forwarding is of course a completely separate issue - as then the <BR>
> recipient receives the work item on their own behalf, not on <BR>> behalf of <BR>> <BR>> someone else. <BR>> <BR>> Regards, <BR>> Jocelyn Dart <BR>> Senior Consultant <BR>> SAP Australia Pty Ltd. <BR>> Level 1/168 Walker St. <BR>> North Sydney <BR>> NSW, 2060 <BR>> Australia <BR>> T +61 412 390 267 <BR>> M + 61 412 390 267 <BR>> E jocelyn.dart@sap.com <BR>> http://www.sap.com <" target="l">http://www.sap.com/> <BR>> <BR>> The information contained in or attached to this electronic <BR>> transmission <BR>> is confidential and may be legally privileged. It is intended only for <BR>> the person or entity to which it is addressed. If you are not the <BR>> intended recipient, you are hereby notified that any distribution, <BR>> copying, review, retransmission, dissemination or other use of this <BR>> electronic transmission or the information contained in it is strictly <BR>
> prohibited. If you have received this electronic transmission in <BR>> error, <BR>> please immediately contact the sender to arrange for the return of the <BR>> original documents. <BR>> <BR>> Electronic transmission cannot be guaranteed to be secure and <BR>> accordingly, the sender does not accept liability for any such data <BR>> corruption, interception, unauthorized amendment, viruses, delays or <BR>> the <BR>> consequences thereof. <BR>> <BR>> Any views expressed in this electronic transmission are those of the <BR>> individual sender, except where the message states otherwise and the <BR>> sender is authorized to state them to be the views of SAP AG or <BR>> any of <BR>> its subsidiaries. SAP AG, its subsidiaries, and their directors, <BR>> officers and employees make no representation nor accept any liability <BR>> for the accuracy or completeness of the views or information contained <BR>
> herein. Please be aware that the furnishing of any pricing <BR>> information/ <BR>> business proposal herein is indicative only, is subject to change and <BR>> shall not be construed as an offer or as constituting a binding <BR>> agreement on the part of SAP AG or any of its subsidiaries to enter <BR>> into <BR>> any relationship, unless otherwise expressly stated. <BR>> <BR>> <BR>> <BR>> ________________________________ <BR>> <BR>> From: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] On <BR>> Behalf <BR>> Of Baskaran Aluru <BR>> Sent: Thursday, 02 March 2006 2:07 PM <BR>> To: SAP Workflow Users' Group <BR>> Subject: Subsitution and possible agents <BR>> <BR>> <BR>> Hi Everyone, <BR>> We have an issue in 4.7 with substitution. A substitute agent is able <BR>> to execute the workitem even though they do not belong to the possible <BR>> agents list. No errors or warnings. Task has "Forwarding not <BR>
> allowed" <BR>> set, possible agents come from a Role, and the substitute is not <BR>> assigned to that Role. <BR>> <BR>> Is this an authorization issue? Any clues would be appreciated. <BR>> <BR>> TIA, <BR>> Baskaran. <BR>> <BR>> <BR>> _______________________________________________ <BR>> SAP-WUG mailing list <BR>> SAP-WUG@mit.edu <BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug <BR>> </BODY>