<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Loren,<br>
<br>
The default 'All' profile comes from the UWL Ad-hoc connector for
UWL collaboration tasks. It can be hidden with UWL configuration or
you can disallow the 'ALL' profile in the substitute BAdI
implementation. Please see SAP KBA/Note <font color="#ff0000"><b>1577579
- Facts and limitations about Substitution in the Universal
Worklist</b><b> </b></font>and the the two additional notes
mentioned in the See Also section.<br>
<br>
Cheers,<br>
Ramki.<br>
<br>
<br>
<div class="moz-cite-prefix">On 2/24/15, 7:49 PM, Bratzler, Loren
wrote:<br>
</div>
<blockquote
cite="mid:D093F74E504B0745917E905C9FC31F2D117351E542@GATUCEXCH07ASV.nscorp.ad.nscorp.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (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]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Courier New";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Thank
you everyone for the replies. Thanks to what Kjetil
mentioned about “General” substitution, I now see what is
happening.<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">When
our users create a substitution rule through the UWL, the
screen initially defaults to the profile “ALL”:<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><img id="Picture_x0020_1"
src="cid:part1.01070101.00060003@erpworkflow.com"
width="818" height="382"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The
user can use the drop-down to select one of the other
profiles if they want to, but it will not allow them to
leave the profile blank:<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><img id="Picture_x0020_2"
src="cid:part2.09050504.09020501@erpworkflow.com"
width="395" height="92"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The
issue occurs when they do choose the “ALL” profile. The
resulting table entry in HRUS_D2 ends up with the profile
field being blank:<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><img id="Picture_x0020_4"
src="cid:part3.04060605.07020301@erpworkflow.com"
width="574" height="136"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">This
then treats the newly created substitution rule as “General”
substitution.<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">If
I use a back-end utility to change the profile field from
blank to “ALL”, then the new task classification does get
excluded from the substitute’s view.<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">So
does this imply that the default profile of “ALL” that shows
up in the Manage Substitution Rules screen is really the
“General” profile and not our custom defined profile named
“ALL”? Or is it possible there is some kind of bug in the
UWL substitution function that is not passing the “ALL”
profile to the backend table?<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Loren
Bratzler<o:p></o:p></span></p>
<p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Norfolk
Southern Corporation<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: <a class="moz-txt-link-abbreviated"
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[<a class="moz-txt-link-freetext"
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>]
On Behalf Of Kjetil Kilhavn<br>
Sent: Tuesday, February 24, 2015 6:01 AM<br>
To: SAP Workflow Users' Group<br>
Subject: [EXTERNAL] Re: Task Classification and Substitution
Profiles</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Tirsdag 24. februar 2015 09.19.05 skrev
Dart, Jocelyn:<o:p></o:p></p>
<p class="MsoPlainText">> Hi Kjetil<o:p></o:p></p>
<p class="MsoPlainText">> No not harsh just grimly realistic.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> Biggest problem with task profiles
to me is you can only assign 1 task <o:p></o:p></p>
<p class="MsoPlainText">> classification per substitute. So
if you want to assign eg travel <o:p></o:p></p>
<p class="MsoPlainText">> tasks & budget tasks to the
same substitute that's not permitted.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I assume you mean profiles here -
because a profile with both travel tasks and budget tasks can
be created so the substitute would only have to be defined
once to get both types of tasks.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">But I agree that this can be a problem,
as an organization using a wide variety of workflow tasks may
end up with an unmanageable number of substitution profiles
since you have to create a substitution profile for every
combination of classfication someone will want to assign.
Thorough analysis is necessary to reduce the number of
profiles as much as possible.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Combined with good assignment of
possible agents it should be manageable with quite a few task
classes I would think, but perhaps not when you exceed 10-15.
<o:p></o:p></p>
<p class="MsoPlainText">I don't have any experience with a high
number of task classes, but with five classes it is at least
not a problem. We actually ended up with fewer profiles than
task classes there - but it will depend on policies and a lot
of factors.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> I have seen some sites create
wrappers for task launch to recheck the <o:p></o:p></p>
<p class="MsoPlainText">> executing users authority before
launching the application itself.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">There are as always many roads leading
to Rome.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> Others have created their own
substitution checks. Eg in BADIs that <o:p></o:p></p>
<p class="MsoPlainText">> only permit users to assign a
substitute of equal or greater authority <o:p></o:p></p>
<p class="MsoPlainText">> or limit substitutes to managers in
the same reporting line<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> I'm still hoping for better answers<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It would be an improvement if the
substitute could be assigned to selected substitution profiles
instead of just one. One could probably remove the entire
profile concept, and let the substitute be assigned directly
to selected task classes. Not a minor change though...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> Rgds<o:p></o:p></p>
<p class="MsoPlainText">> Jocelyn<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> Sent from my iPhone with many
apologies for the spelling, grammar and <o:p></o:p></p>
<p class="MsoPlainText">> any other deficiencies<o:p></o:p></p>
<p class="MsoPlainText">> > On 23 Feb 2015, at 10:40 pm,
Kjetil Kilhavn <<a moz-do-not-send="true"
href="mailto:list.sap-wug@vettug.no"><span
style="color:windowtext;text-decoration:none">list.sap-wug@vettug.no</span></a>><o:p></o:p></p>
<p class="MsoPlainText">> > wrote:<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Don't be so harsh on SAP
Jocelyn - they try their best ;-)<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > The main problem is that task
classification is not obligatory, and <o:p></o:p></p>
<p class="MsoPlainText">> > that it is not mandatory to
select a substitution profile (in GUI <o:p></o:p></p>
<p class="MsoPlainText">> > the lack of a profile is
accompanied by the description “General <o:p></o:p></p>
<p class="MsoPlainText">> > substitution”, I guess this is
equivalent to the “All tasks” <o:p></o:p></p>
<p class="MsoPlainText">> > selection in the UWL although
it appears as if you select a profile in the UWL).<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > You *can* solve your problem
by doing the following:<o:p></o:p></p>
<p class="MsoPlainText">> > 1) Implement a measure (I
don't know if there are any explicit <o:p></o:p></p>
<p class="MsoPlainText">> > enhancement<o:p></o:p></p>
<p class="MsoPlainText">> > possibilities) to ensure that
“All tasks”/“General substitution” is <o:p></o:p></p>
<p class="MsoPlainText">> > not an accepted choice of
substitution profile.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > 2) Assign classification to
all tasks in use, and create the <o:p></o:p></p>
<p class="MsoPlainText">> > substitution profiles for all
required combinations of task classes.<o:p></o:p></p>
<p class="MsoPlainText">> > Even if you don't have to
assign task classification to a task for <o:p></o:p></p>
<p class="MsoPlainText">> > which substitution should not
be possible I would recommend creating <o:p></o:p></p>
<p class="MsoPlainText">> > a class that makes it obvious
that it is excluded from substitution.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > The “General substitution”
profile is the only profile that allows a <o:p></o:p></p>
<p class="MsoPlainText">> > substitute to see tasks
without classification, so both steps are <o:p></o:p></p>
<p class="MsoPlainText">> > required.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > I have not implemented such
solutions (customer did not want to), <o:p></o:p></p>
<p class="MsoPlainText">> > but it would be a permanent
and proper solution to the problem which <o:p></o:p></p>
<p class="MsoPlainText">> > could be applied to any number
of tasks without requiring further <o:p></o:p></p>
<p class="MsoPlainText">> > development. It would also
(and I would argue this is equally <o:p></o:p></p>
<p class="MsoPlainText">> > important) force users to
actively make a choice of substitution <o:p></o:p></p>
<p class="MsoPlainText">> > profile. They often don't,
even if the substitute should only handle <o:p></o:p></p>
<p class="MsoPlainText">> > e.g. approval of purchases and
invoices.<o:p></o:p></p>
<p class="MsoPlainText">> > <o:p></o:p></p>
<p class="MsoPlainText">> > Lørdag 21. februar 2015
08.17.11 skrev Dart, Jocelyn:<o:p></o:p></p>
<p class="MsoPlainText">> >> Hi Loren<o:p></o:p></p>
<p class="MsoPlainText">> >> Unfortunately I suspect
what you are missing is the reality check <o:p></o:p></p>
<p class="MsoPlainText">> >> on task classification
capabilities or lack thereof - perhaps try <o:p></o:p></p>
<p class="MsoPlainText">> >> work item exit or a
wrapper function or the Substitution BADIs <o:p></o:p></p>
<p class="MsoPlainText">> >> instead Rgds Jocelyn<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Sent from my iPhone with
many apologies for the spelling, grammar <o:p></o:p></p>
<p class="MsoPlainText">> >> and any other deficiencies<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> On 21 Feb 2015, at 8:08
am, Bratzler, Loren <o:p></o:p></p>
<p class="MsoPlainText">> >> <<a
moz-do-not-send="true"
href="mailto:Loren.Bratzler@nscorp.com%3cmailto:Loren.Bratzler@nscorp.com"><span
style="color:windowtext;text-decoration:none">Loren.Bratzler@nscorp.com<mailto:Loren.Bratzler@nscorp.com</span></a>>>
wrote:<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Hello Wuggers!<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> We have a situation here
where the business realized that Annual <o:p></o:p></p>
<p class="MsoPlainText">> >> Performance Reviews can be
opened and read by UWL Substitutes. <o:p></o:p></p>
<p class="MsoPlainText">> >> They want us to exclude
tasks related to the Annual Appraisal <o:p></o:p></p>
<p class="MsoPlainText">> >> process from a UWL
Substitute’s view when they are working on items <o:p></o:p></p>
<p class="MsoPlainText">> >> on behalf of someone else.<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> I found this very good
article on SCN that explains the process for <o:p></o:p></p>
<p class="MsoPlainText">> >> creating task
classifications and assigning those classifications <o:p></o:p></p>
<p class="MsoPlainText">> >> to substitution profiles:<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> <a moz-do-not-send="true"
href="http://wiki.scn.sap.com/wiki/display/HOME/Link+Substitution,+Classi"><span
style="color:windowtext;text-decoration:none">http://wiki.scn.sap.com/wiki/display/HOME/Link+Substitution,+Classi</span></a><o:p></o:p></p>
<p class="MsoPlainText">> >> ficati<o:p></o:p></p>
<p class="MsoPlainText">> >> on+ and+Profiles<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> However, I am struggling
to make this work.<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Our situation is that we
basically have two Substitution profiles. <o:p></o:p></p>
<p class="MsoPlainText">> >> One is named “ALL” (for
all tasks) and the other is named <o:p></o:p></p>
<p class="MsoPlainText">> >> “TRAVEL_APPRO” (for only
approving travel related tasks). What I <o:p></o:p></p>
<p class="MsoPlainText">> >> tried to do was define a
new Classification for performance reviews <o:p></o:p></p>
<p class="MsoPlainText">> >> named “PDR” (Personal
Development Review). We use the standard <o:p></o:p></p>
<p class="MsoPlainText">> >> appraisal workflow,
WS12300110, which has standard task TS12300115 <o:p></o:p></p>
<p class="MsoPlainText">> >> for the employee to read
and respond to their performance review. <o:p></o:p></p>
<p class="MsoPlainText">> >> I assigned task TS12300115
to the new “PDR”<o:p></o:p></p>
<p class="MsoPlainText">> >> classification. But then
I did not assign “PDR” as a <o:p></o:p></p>
<p class="MsoPlainText">> >> classification for the
“ALL” substitution profile. PDR is not assigned to any
profile.<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> My thinking was that if
the new classification is not included in <o:p></o:p></p>
<p class="MsoPlainText">> >> any profile, then the
tasks assigned to that classification would <o:p></o:p></p>
<p class="MsoPlainText">> >> not show up in the
substitutes’ queue, regardless of which profile they were
using.<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Am I missing something
here?<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Any help is greatly
appreciated!<o:p></o:p></p>
<p class="MsoPlainText">> >> <o:p></o:p></p>
<p class="MsoPlainText">> >> Loren Bratzler<o:p></o:p></p>
<p class="MsoPlainText">> >> Norfolk Southern
Corporation<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">>
_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">> SAP-WUG mailing list<o:p></o:p></p>
<p class="MsoPlainText">> <a moz-do-not-send="true"
href="mailto:SAP-WUG@mit.edu"><span
style="color:windowtext;text-decoration:none">SAP-WUG@mit.edu</span></a><o:p></o:p></p>
<p class="MsoPlainText">> <a moz-do-not-send="true"
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><span
style="color:windowtext;text-decoration:none">http://mailman.mit.edu/mailman/listinfo/sap-wug</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">Kjetil Kilhavn / Vettug AS (<a
moz-do-not-send="true" href="http://www.vettug.no"><span
style="color:windowtext;text-decoration:none">http://www.vettug.no</span></a>)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">SAP-WUG mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a moz-do-not-send="true"
href="mailto:SAP-WUG@mit.edu"><span
style="color:windowtext;text-decoration:none">SAP-WUG@mit.edu</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a moz-do-not-send="true"
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><span
style="color:windowtext;text-decoration:none">http://mailman.mit.edu/mailman/listinfo/sap-wug</span></a><o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SAP-WUG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
</pre>
</blockquote>
<br>
</body>
</html>