<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Jocelyn,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I must have missed something in our system
because when I had played around with the UWL substitutions I didn’t see
the definitions in our ERP2005 system(NW2004S). Which backend tables are being
updated with the UWL generated substitutions?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I had also made a similar posting in SDN
where I was told that the UWL substitutions do not get saved in the backend
system(SRM5).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><a
href="https://forums.sdn.sap.com/thread.jspa?threadID=100918&messageID=1116270#1116270">https://forums.sdn.sap.com/thread.jspa?threadID=100918&messageID=1116270#1116270</a><o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Can you please clarify.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Jerry<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=3 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <st1:PersonName
w:st="on">sap-wug-bounces@mit.edu</st1:PersonName> [mailto:<st1:PersonName
w:st="on">sap-wug-bounces@mit.edu</st1:PersonName>] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Dart, Jocelyn<br>
<b><span style='font-weight:bold'>Sent:</span></b> March 2, 2006 10:33 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">SAP
Workflow Users' Group</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: RE: Subsitution and possible
agents</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Excuse me Jerry but yes they absolutely
ARE linked to the backend system. </span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>In fact when you create a substitute
through "Manage Substitutions" it attempts to create the substitution
in ALL linked backend systems.</span></font><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p><font size=1 face=Arial><span style='font-size:7.5pt;font-family:Arial'><!-- Converted from text/rtf format -->Regards,</span></font>
<br>
<b><font size=1 color=navy face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:navy;font-weight:bold'>Jocelyn Dart</span></font></b> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>Senior Consultant</span></font> <br>
<b><font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray;font-weight:bold'>SAP Australia Pty Ltd.</span></font></b> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>Level <st1:Street w:st="on"><st1:address w:st="on">1/168
Walker St</st1:address></st1:Street>.</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>North Sydney </span></font><br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>NSW, 2060</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>Australia</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>T +61 412 390 267</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>M + 61 412 390 267</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'>E jocelyn.dart@sap.com</span></font> <br>
<font size=1 color=gray face=Arial><span style='font-size:7.5pt;font-family:
Arial;color:gray'><a href="http://www.sap.com/">http://www.sap.com</a></span></font>
<o:p></o:p></p>
<p><font size=1 color=red face="Times New Roman"><span lang=EN-AU
style='font-size:7.5pt;color:red'>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. </span></font><o:p></o:p></p>
<p><font size=1 color=red face="Times New Roman"><span lang=EN-AU
style='font-size:7.5pt;color:red'>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.</span></font><o:p></o:p></p>
<p><font size=1 color=red face="Times New Roman"><span lang=EN-AU
style='font-size:7.5pt;color:red'>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. </span></font><o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=3 width="100%" align=center tabIndex=-1>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <st1:PersonName
w:st="on">sap-wug-bounces@mit.edu</st1:PersonName> [mailto:<st1:PersonName
w:st="on">sap-wug-bounces@mit.edu</st1:PersonName>] <b><span style='font-weight:
bold'>On Behalf Of </span></b>jerry martinek<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, 03 March 2006 4:41
AM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">SAP
Workflow Users' Group</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: RE: Subsitution and
possible agents</span></font><o:p></o:p></p>
<p><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-weight:bold'>Hi Baskaran,</span></font></b><o:p></o:p></p>
<p><strong><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>There
is also the UWL based substitutions that are user/logon id based and are
not liked to the backend system.</span></font></b></strong><o:p></o:p></p>
<p><strong><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Jerry</span></font></b></strong> <o:p></o:p></p>
<p><b><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-weight:bold'>----- Original Message -----</span></font></b><o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>From</span></font></b>: Rick Sample
<Rick.Sample@gbe.com> <o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>Date</span></font></b>: Thursday,
March 2, 2006 8:57 am <o:p></o:p></p>
<p class=MsoNormal><b><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-weight:bold'>Subject</span></font></b>: RE:
Subsitution and possible agents <o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> 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 <st1:Street w:st="on"><st1:address w:st="on">1/168 Walker St</st1:address></st1:Street>.
<br>
> North Sydney <br>
> NSW, 2060 <br>
> <st1:country-region w:st="on"><st1:place w:st="on">Australia</st1:place></st1:country-region>
<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: <st1:PersonName w:st="on">sap-wug-bounces@mit.edu</st1:PersonName> [<st1:PersonName
w:st="on">sap-wug-bounces@mit.edu</st1:PersonName>] On <br>
> Behalf <br>
> Of Baskaran Aluru <br>
> Sent: Thursday, 02 March 2006 2:07 PM <br>
> To: <st1:PersonName w:st="on">SAP Workflow Users' Group</st1:PersonName> <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>
> <o:p></o:p></span></font></p>
</div>
</body>
</html>