<br><font size=2 face="sans-serif">Many Thanks Jocelyn. That looks as though
its exactly what I need.</font>
<br>
<br><font size=2 face="sans-serif">Kind Regards</font>
<br>
<br><font size=2 face="sans-serif">John</font>
<br>
<br><font size=2 face="sans-serif"><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%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Dart, Jocelyn"
<jocelyn.dart@sap.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">06/06/2008 14:16</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: Approval Limits for Travel Expenses</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=blue face="Arial">Hi John, </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">I think you must be looking at
the wrong doco. Personalization object keys have NOTHING to do with
Portal iviews. </font>
<br><font size=2 color=blue face="Arial">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>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Personalization data is maintained
on the Personalization tab of the User Master (transaction SU01)
or the Security Role (transaction PFCG). </font>
<br><font size=2 color=blue face="Arial">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>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Roles can of course be linked
to positions or jobs. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">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>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Key things to consider when deciding
which way to go:</font>
<br><font size=2 color=blue face="Arial">* How complex are the attributes?
- Matrices are easier to manage via personalization object keys. Extended
attributes are possible but involve greater coding effort. </font>
<br><font size=2 color=blue face="Arial">* 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>
<br><font size=2 color=blue face="Arial">* 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>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Hope that helps. </font>
<br><font size=3> </font>
<p><font size=1 face="Arial">Regards,</font><font size=3> </font><font size=1 color=#000080 face="Arial"><b><br>
Jocelyn Dart</b></font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Senior Consultant</font><font size=3> </font><font size=1 color=#808080 face="Arial"><b><br>
SAP Australia Pty Ltd.</b></font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Level 1/168 Walker St.</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
North Sydney <br>
NSW, 2060</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
Australia</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
T +61 412 390 267</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
M + 61 412 390 267</font><font size=3> </font><font size=1 color=#808080 face="Arial"><br>
E jocelyn.dart@sap.com</font><font size=3> </font><font size=1 color=blue face="Arial"><u><br>
</u></font><a href=http://www.sap.com/><font size=1 color=blue face="Arial"><u>http://www.sap.com</u></font></a><font size=3>
</font>
<p><font size=1 color=red face="Times New Roman">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>
<p><font size=1 color=red face="Times New Roman">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>
<p><font size=1 color=red face="Times New Roman">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>
<p><font size=3> </font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu]
<b>On Behalf Of </b>John A Haworth<b><br>
Sent:</b> Friday, 06 June 2008 8:47 PM<b><br>
To:</b> SAP Workflow Users' Group<b><br>
Subject:</b> RE: Approval Limits for Travel Expenses</font><font size=3><br>
</font>
<br><font size=2 face="sans-serif"><br>
Thanks Jocelyn,</font><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
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><font size=3> <br>
</font><font size=2 face="sans-serif"><br>
Many Thanks</font><font size=3> <br>
</font><font size=2 face="sans-serif"><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>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------</font><font size=3><br>
<br>
<br>
</font>
<table width=100%>
<tr valign=top>
<td width=46%><font size=1 face="sans-serif"><b>"Dart, Jocelyn"
<jocelyn.dart@sap.com></b> <br>
Sent by: sap-wug-bounces@mit.edu</font><font size=3> </font>
<p><font size=1 face="sans-serif">06/06/2008 06:23</font><font size=3>
</font>
<br>
<table border=4 width=100%>
<tr valign=top>
<td width=100% bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<p>
<td width=53%>
<br>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td width=86%><font size=1 face="sans-serif">"SAP Workflow Users'
Group" <sap-wug@mit.edu></font><font size=3> </font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: Approval Limits for Travel Expenses</font></table>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=49%>
<td width=50%></table>
<br></table>
<br><font size=3><br>
<br>
</font><font size=2><tt><br>
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</tt></font><font size=3><br>
</font><font size=2><tt>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</tt></font>
<br>