<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thaks Jocelyn! This is very good info. Personalization seems to be a
great fit for an approval process I am currently involved with.<br>
<br>
Thanks John, for bringing up the subject!<br>
<br>
Best Regards,<br>
Ramki Maley.<br>
<br>
<br>
Dart, Jocelyn wrote:
<blockquote cite="mid:2EAD340DEF223745B1AC9A10B49FBB4701DB9513@sgsine13.sin.sap.corp" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.3314" name="GENERATOR">
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Hi John, </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">I think you must be looking at
the wrong doco. Personalization object keys have NOTHING to do with
Portal iviews. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Look at transaction PERSREG and
transaction SPERS_MAINT. If you use the standard storage the data
itself is held in table SPERS_OBJ. A good example of a matrix type
attribute for roles is "RESOURCE" - this shows how easy it is to
create personalization a function module calling standard table
handling routines. You can also very rapidly create a personalization
key using a dictionary structure or table type. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Personalization data is
maintained on the Personalization tab of the User Master (transaction
SU01) or the Security Role (transaction PFCG). </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Users can only maintain
personalization keys if they have access to SU01 and the key has been
enabled for user masters (it can be enabled for roles only) and they
have sufficient authorization to maintain the data. There is no option
for changing Personaliation keys via the Portal. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Roles can of course be linked to
positions or jobs. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Yes attributes (infotype 1222)
assigned to positions or org units are another possible option. Be
aware that to maintain attributes correctly in this way you MUST use
one of the PPOMA* transactions - using PA30, PO13, or PO10 does not
give access to the "attribute scenario" which is critical to correct
maintenance of these attributes. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Key things to consider when
deciding which way to go:</font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">* How complex are the
attributes? - Matrices are easier to manage via personalization object
keys. Extended attributes are possible but involve greater coding
effort. </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">* What minimizes the maintenance
burden? If your delegations are in a discrete set of bands then this
is easier to manage via security roles/personalization object keys
rather than having to maintain attributes for every org
unit/position. If the delegations are more subjective, attributes may
be better.</font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">* Are the delegations for a user
based on the position they hold (.... use attributes) or their security
level (.... use personalization keys on roles) or are they assigned
personally to them (... use personalization keys on users)? </font></span></div>
<div dir="ltr" align="left"><span class="929480113-06062008"></span> </div>
<div dir="ltr" align="left"><span class="929480113-06062008"><font color="#0000ff" face="Arial" size="2">Hope that helps. </font></span></div>
<div> </div>
<!-- Converted from text/rtf format -->
<p><span lang="en-us"><font face="Arial" size="1">Regards,</font></span>
<br>
<span lang="en-us"><b><font color="#000080" face="Arial" size="1">Jocelyn
Dart</font></b></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">Senior
Consultant</font></span> <br>
<span lang="en-us"><b><font color="#808080" face="Arial" size="1">SAP
Australia Pty Ltd.</font></b></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">Level
1/168 Walker St.</font></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">North
Sydney </font></span><br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">NSW,
2060</font></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">Australia</font></span>
<br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">T
+61 412 390 267</font></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">M +
61 412 390 267</font></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1">E
<a class="moz-txt-link-abbreviated" href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a></font></span> <br>
<span lang="en-us"><font color="#808080" face="Arial" size="1"><a moz-do-not-send="true" href="http://www.sap.com/">http://www.sap.com</a></font></span>
</p>
<p><span lang="en-au"><font color="#ff0000" face="Times New Roman" size="1">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. </font></span></p>
<p><span lang="en-au"><font color="#ff0000" face="Times New Roman" size="1">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.</font></span></p>
<p><span lang="en-au"><font color="#ff0000" face="Times New Roman" size="1">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. </font></span></p>
<div> </div>
<br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
<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>] <b>On Behalf
Of </b>John A Haworth<br>
<b>Sent:</b> Friday, 06 June 2008 8:47 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Approval Limits for Travel Expenses<br>
</font><br>
</div>
<br>
<font face="sans-serif" size="2">Thanks Jocelyn,</font> <br>
<br>
<font face="sans-serif" size="2">One last question, promise. Is there
an advantage of 'Personalisation' over 'Attributes (PPOMA)' against an
organisational unit, my thoughts are that personalization seem to be
for use via iviews and the portal and could be seen by and potentially
changed by the user. Whereas attributes would be master data and only
changed by the relevant authorised person in Org Management and could
be against a Position or Job. I am trying to represent a delegated list
of authority with approval limits, so perhaps the Attributes approach
would be more suited?</font> <br>
<br>
<font face="sans-serif" size="2">Many Thanks</font> <br>
<br>
<font face="sans-serif" size="2">John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot,
Hampshire, GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. <br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of
e-mail for such purpose.<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
</font><br>
<br>
<br>
<table width="100%">
<tbody>
<tr valign="top">
<td width="40%"><font face="sans-serif" size="1"><b>"Dart,
Jocelyn" <a class="moz-txt-link-rfc2396E" href="mailto:jocelyn.dart@sap.com"><jocelyn.dart@sap.com></a></b> </font><br>
<font face="sans-serif" size="1">Sent by:
<a class="moz-txt-link-abbreviated" href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></font>
<p><font face="sans-serif" size="1">06/06/2008 06:23</font>
<table border="1">
<tbody>
<tr valign="top">
<td bgcolor="white">
<div align="center"><font face="sans-serif" size="1">Please
respond to<br>
"SAP Workflow Users' Group" <a class="moz-txt-link-rfc2396E" href="mailto:sap-wug@mit.edu"><sap-wug@mit.edu></a></font></div>
</td>
</tr>
</tbody>
</table>
<br>
</p>
</td>
<td width="59%">
<table width="100%">
<tbody>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td>
<td><font face="sans-serif" size="1">"SAP Workflow Users'
Group" <a class="moz-txt-link-rfc2396E" href="mailto:sap-wug@mit.edu"><sap-wug@mit.edu></a></font> </td>
</tr>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
</td>
<td> <br>
</td>
</tr>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td>
<td><font face="sans-serif" size="1">RE: Approval Limits
for Travel Expenses</font></td>
</tr>
</tbody>
</table>
<br>
<table>
<tbody>
<tr valign="top">
<td> <br>
</td>
<td><br>
</td>
</tr>
</tbody>
</table>
<br>
</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<font size="2"><tt>Hi John, <br>
Yes I've used this approach at some sites - especially where the limits
are matrixed - e.g. different limits per travel category. Works well. <br>
Regards, <br>
Jocelyn <br>
<br>
________________________________<br>
<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> on behalf of John A Haworth<br>
Sent: Thu 5/06/2008 7:34 PM<br>
To: SAP Workflow Users' Group<br>
Subject: RE: Approval Limits for Travel Expenses<br>
<br>
<br>
<br>
Thanks for that, and do you think that personalisation would be a
suitable place to hold the 'Approval Amount'? <br>
<br>
Again, many thanks for your advice. <br>
<br>
Kind Regards <br>
<br>
John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot,
Hampshire, GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. <br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of
e-mail for such purpose.<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
<br>
<br>
<br>
"Dart, Jocelyn" <a class="moz-txt-link-rfc2396E" href="mailto:jocelyn.dart@sap.com"><jocelyn.dart@sap.com></a> <br>
Sent by: <a class="moz-txt-link-abbreviated" href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> <br>
<br>
05/06/2008 06:17 <br>
Please respond to<br>
"SAP Workflow Users' Group" <a class="moz-txt-link-rfc2396E" href="mailto:sap-wug@mit.edu"><sap-wug@mit.edu></a><br>
<br>
<br>
To<br>
"SAP Workflow Users' Group" <a class="moz-txt-link-rfc2396E" href="mailto:sap-wug@mit.edu"><sap-wug@mit.edu></a> <br>
cc<br>
Subject<br>
RE: Approval Limits for Travel Expenses <br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi John, <br>
Yes Personalization is available in all SAP ABAP systems since R/3
4.6C. Only difference is you need to create your own personalization
key in transaction PERSREG and create the necessary coding to read it. <br>
There's a whole section on it in the Help library - look for
Personalization.<br>
Regards,<br>
Jocelyn <br>
<br>
________________________________<br>
<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> on behalf of John A Haworth<br>
Sent: Wed 4/06/2008 10:44 PM<br>
To: SAP Workflow Users' Group<br>
Subject: Approval Limits for Travel Expenses<br>
<br>
<br>
<br>
Hi <br>
<br>
I am looking in ECC6.0, at where would be best to hold Travel expenses
Approval limits. I remember that in SRM Org Management in the extended
attributes or personalisation there is an approval limit amount, but
dont think this is available in ECC6 Org Management. Has anyone had a
similar issue and any thoughts on where this amount would be best held?
<br>
<br>
Thanks <br>
<br>
Regards <br>
<br>
John<br>
<br>
CSC Computer Sciences Limited<br>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot,
Hampshire, GU11 1PZ, UK<br>
Registered in England No: 0963578<br>
<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. <br>
NOTE: Regardless of content, this e-mail shall not operate to bind CSC
to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of
e-mail for such purpose.<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</tt></font><br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
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>
</body>
</html>