<html><body>
<p>Hi All,<br>
<br>
Just to add to the subject.<br>
Our substitution process operates in the following manner<br>
1. Substitution workflow is triggered on creation of an absence record.<br>
2. If absence is in the past the workflow or person that will be absence (Appointee) does not have an active SAP login the workflow will end.<br>
3. Workflow goes the Appointee with the following options<br>
3.1 Select A Substitute<br>
3.2 No Substitute Required <br>
4. The workflow is then routed to the Appointee's superior to will the following options<br>
4.1 Approve Substitute Selected<br>
4.2 Choose Another substitute<br>
4.3 No Substitute Required<br>
5. If option 4.3 is selected the workflow will end.<br>
6. if 4.1 or 4.2 is selected the workflow will then perform the following<br>
6.1 Compare the profiles of the Appointee and the Substitute and create composite profile consisting only difference<br>
This composite profile has the conforms to the naming convention of Z:"USER LOGIN", e.g. Z:DNAT<br>
6.2 This profile is then linked to the Substitute for the period on absence.<br>
7. Profile is remove on the following conditions<br>
7.1 Substitution period ends<br>
7.2 Deletion of Absence<br>
7.3 Substitute is changed.<br>
<br>
<br>
Regards<br>
<br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<br>
Fax : +27 031 902 9633<br>
E-mail : ngovender4@toyota.co.za<br>
==================================================================<br>
Forgiveness is when one relinquishes the option to hurt the person that hurt you.<br>
Remember not to forget that which you do not need to know.<br>
==================================================================<br>
<img src="cid:10__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" width="16" height="16" alt="Inactive hide details for "Rick Sample" <Rick.Sample@gbe.com>">"Rick Sample" <Rick.Sample@gbe.com><br>
<br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td style="background-image:url(cid:20__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za); background-repeat: no-repeat; " width="40%">
<ul>
<ul>
<ul>
<ul><b><font size="2">"Rick Sample" <Rick.Sample@gbe.com></font></b><font size="2"> </font><br>
<font size="2">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size="2">2006/03/02 06:57 PM</font>
<table border="1">
<tr valign="top"><td width="168" bgcolor="#FFFFFF"><div align="center"><font size="2">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></td></tr>
</table>
</ul>
</ul>
</ul>
</ul>
</td><td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">To</font></div></td><td width="100%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">sap-wug@mit.edu</font></td></tr>
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">cc</font></div></td><td width="100%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
</td></tr>
<tr valign="top"><td width="1%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="58" alt=""><br>
<div align="right"><font size="2">Subject</font></div></td><td width="100%"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""><br>
<font size="2">RE: Subsitution and possible agents</font></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="58"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td><td width="336"><img src="cid:30__=CDBBFBB5DFB5A6518f9e8a93df9@toyota.co.za" border="0" height="1" width="1" alt=""></td></tr>
</table>
</td></tr>
</table>
<br>
<tt>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 and/or<br>
user does not see <br>
certain tasks. Like HR WFs. <br>
You can add "classifications" to the tasks and users can 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 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>
</tt><tt><a href="http://www.sap.com">http://www.sap.com</a></tt><tt> <</tt><tt><a href="http://www.sap.com/">http://www.sap.com/</a></tt><tt>> <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 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 [<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>] 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>
</tt><tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></tt><tt><br>
</tt><br>
</body></html>
<table><tr><td bgcolor=#ffffff><font color=#000000>This message is a privileged and private communication and may be read, copied and used only by
the intended recipient(s). If you are not an intended recipient, please let us know by return email.
Please then delete the message and do not disclose its contents to any person. Neither the sender nor
Toyota South Africa Motors accepts any liability whatsoever as a result of the further dissemination
of this message. Whilst all reasonable steps are taken to avoid corruption of data or information,
we do not accept any liability should such corruption occur.
</font></td></tr></table>