<br><font size=2 face="sans-serif">Thanks Jocelyn,</font>
<br>
<br><font size=2 face="sans-serif">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 size=2 face="sans-serif">Many Thanks</font>
<br>
<br><font size=2 face="sans-serif">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%>
<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 06:23</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><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>