<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:verdana, helvetica, sans-serif;font-size:10pt"><DIV></DIV>
<DIV>Dear Andy,</DIV>
<DIV> </DIV>
<DIV>This is quite a common problem and has an elegant solution. There's authorization object for save layout not user specific. Just don't give the users this authorization object and you'll be fine.</DIV>
<DIV> </DIV>
<DIV>I don't remember the authorization object name (I think its S_ALV_LAYO) - you can find it in t.code SU24 given transaction code SBWP.</DIV>
<DIV> </DIV>
<DIV>Good luck,<BR> </DIV>
<P><FONT face="verdana, helvetica, sans-serif" color=#00007f size=2><STRONG>Regards,<BR>Shai Eyal</STRONG></FONT></P>
<P><FONT face=Verdana color=#000080 size=2><STRONG>SAP Logistics senior consultant<BR>SAP Workflow specialist<BR>Mobile: 972-52-5816633</STRONG></FONT></P>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: verdana, helvetica, sans-serif"><BR><BR>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">Message: 5<BR>Date: Wed, 6 Feb 2008 09:54:49 -0700<BR>From: "Catherall, Andy M" <<A href="mailto:andy.m.catherall@csplc.com" ymailto="mailto:andy.m.catherall@csplc.com">andy.m.catherall@csplc.com</A>><BR>Subject: SBWP global layout problem<BR>To: "SAP Workflow Users' Group" <<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Message-ID:<BR> <<A href="mailto:BBDCCADC9807084FBE6A80D4F4505B5901682E83@acsemb05.americas.csplc.net" ymailto="mailto:BBDCCADC9807084FBE6A80D4F4505B5901682E83@acsemb05.americas.csplc.net">BBDCCADC9807084FBE6A80D4F4505B5901682E83@acsemb05.americas.csplc.net</A>><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Hi all<BR><BR>In these days of Portals & UWL, this query may be a blast from the past,<BR>but we've come across an interesting little problem.
In fact, I'm<BR>surprised we've not encountered this before, given the system has been<BR>live for years. Oh well, that's complacency for you...!<BR><BR>The other day, a user decided to update the layout of the business<BR>workplace, changing the columns etc. However, they were on the default<BR>global layout and hence when they saved it, they updated the appearance<BR>for nearly everbody.<BR><BR>Some people did not like this new design (especially as they had moved<BR>some dynamic columns into prime position, which appeared blank to most<BR>users) and so felt that they had a better approach. It's quite<BR>interesting to see quite what 'useful' information the users believe<BR>they really can't live with.<BR><BR>However, since then we've found ourselves in a losing battle. Everytime<BR>we try to correct the layout, another user decides they don't like<BR>what's happened, and modifies it again.<BR><BR>Of course, there are 'user specific' layouts, but
when a user modifies<BR>the default layout they are on and elects to save it, the 'User<BR>specific' flag is not set. They just update the global layout as that's<BR>the easiest. Worse, the file naming convention for 'User Specific'<BR>requires the user to clear the '/' and add a 'Z'. Not something they're<BR>going to do by accident.<BR><BR><BR>* Is there a way to permit users to update their user-specific layouts,<BR>whilst locking down the global ones? Are we missing some basic security<BR>settings?<BR><BR>* Has anyone else suffered from this? Or, how have you avoided it?<BR><BR>* Is there a technical solution, or will this just come down to user<BR>training in some way (eek!)? We have many hundreds of users, dotted<BR>around the world, so we can hardly just ring each of them and slap their<BR>wrists!<BR><BR>All suggestions gratefully received :-)<BR><BR>Cheers<BR>Andy Catherall <BR><BR>Please be environmentally friendly - please don't print this
email unless you really need to <BR><BR><BR>-----------------------------------------<BR><BR>This email (including any attachment) is confidential and may contain privileged information. If you are not the intended recipient or receive it in error, you may not use, distribute, disclose or copy any of the information contained within it and it may be unlawful to do so. If you are not the intended recipient please notify us immediately by returning this e-mail to us at <A href="mailto:mailerror@csplc.com" ymailto="mailto:mailerror@csplc.com">mailerror@csplc.com</A> and destroy all copies.<BR>Any views expressed by individuals within this e-mail do not necessarily reflect the views of Cadbury Schweppes Plc or any of its subsidiaries' or affiliates'. This email does not constitute a binding offer, acceptance, amendment, waiver or other agreement, unless such intention is clearly stated in the body of the email. Whilst we have taken reasonable steps to
ensure that this e-mail and attachments are free from viruses, recipients are advised to subject this mail to their own virus checking, in keeping with good computing practice. <BR>Please note that e-mail received by Cadbury Schweppes Plc or its subsidiaries or affiliates may be monitored in accordance with applicable law. <BR><BR>Cadbury Schweppes plc registered in England, Company Number 00052457<BR>whose Registered Office is at 25 Berkeley Square, London, W1J 6HB United Kingdom<BR>Telephone:+44 (0) 20 7409 1313 Fax:+44 (0) 20 7830 5200 <BR>-----------------------------------------<BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A href="mailto:SAP-WUG@mit.edu" ymailto="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR>End of SAP-WUG Digest,
Vol 39, Issue 11<BR>***************************************<BR></DIV><BR></DIV></div><br>Send instant messages to your online friends http://uk.messenger.yahoo.com </body></html>