<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff size=2>Hi John, </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff 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 face=Arial
color=#0000ff 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><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff 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 face=Arial
color=#0000ff 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><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff size=2>Roles can of course be linked to positions or jobs.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff 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><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff 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 face=Arial
color=#0000ff 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 face=Arial
color=#0000ff 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 face=Arial
color=#0000ff 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><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=929480113-06062008><FONT face=Arial
color=#0000ff size=2>Hope that helps. </FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </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 face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 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 face="Times New Roman" color=#ff0000 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 face="Times New Roman" color=#ff0000 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 lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <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>
<DIV></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"
<jocelyn.dart@sap.com></B> </FONT><BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</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"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: Approval Limits for Travel
Expenses</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></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: sap-wug-bounces@mit.edu 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" <jocelyn.dart@sap.com> <BR>Sent by: sap-wug-bounces@mit.edu
<BR><BR>05/06/2008 06:17 <BR>Please respond to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu><BR><BR><BR>To<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu> <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: sap-wug-bounces@mit.edu 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>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></TT></FONT><BR></BODY></HTML>