01-11-2007 4:56 AM
Dear all,
we would like to restrict all end-users to only be able to save user-specific layouts across FB* transactions and others. In other words they should not be able to save global layouts visible to other users. I have read about the I_SAVE = U parameter but that would have to be set for every report individually as far as I understand. We are after an authorisations object that restrict the user to generally save user-specific layouts only. Many thanks! Cheers Stefan
01-15-2007 4:03 PM
Hi Stefan,
I am not aware of any authorization object to control layout changes as required by you. The best way would be to use the I_SAVE parameter withing the program.
An alternative can be to ask the user to protect their individual variant, so that apart from them no other user can change them. If you want to make these variants globally accessible again, use report RSVARENT.
Also see note 80526.
Regards,
Sanju.
01-15-2007 4:03 PM
Hi Stefan,
I am not aware of any authorization object to control layout changes as required by you. The best way would be to use the I_SAVE parameter withing the program.
An alternative can be to ask the user to protect their individual variant, so that apart from them no other user can change them. If you want to make these variants globally accessible again, use report RSVARENT.
Also see note 80526.
Regards,
Sanju.
01-16-2007 2:43 AM
01-16-2007 11:56 PM
07-03-2007 10:00 PM
Hi Stefan, It's been a while ... wondering if you still remember how exactly you solved this problem. Can you brief on the same.I'd want the users restricted to the global defaults. Thanks
12-06-2007 12:34 PM
Hi stefan
Can u Help us tell how u solved your problem
how S_ALV_LAYO authorization Object does the Trick
Reply urgently please or give your cell no so that we can contact you
12-07-2007 9:33 PM
Hello Manish,
If Stefan posted his cell number directly, it would be removed again (sorry, that rule makes sense).
If you look at Stefan's Business-Card, you will also be able to see that Stefan has (most likely) been inactive since June 2007.
Assuming that non-Stefan people can also answer... ... have you already restricted the variants and the global unlock? Are you sure that all used variants are locked? To my knowledge that is stronger than S_ALV_LAYO (though I might be wrong).
Kind regards,
Julius
12-19-2007 5:01 PM
Hello Julius,
Can you please elaborate on methods to lock down global variants? I'm trying to evaluate options for our system. And between the auth object S_ALV_LAYO and a higher level of control, I'd prefer a system setting/control over security. Specially if we're talking about locking all GLOBAL layouts.
Thanks,
Kaushal
12-20-2007 4:55 PM
Hello Kaushal,
Stefan is correct about restriction of S_ALV_LAYO being used to protect types of layouts (see SAP notes 409190 and 601803 - I_SAVE = 'A' changes to 'U').
For program variants (different to layouts, but might specifc the layout in the variant - which is what misled me) the note already mentioned above (80526) explains how to prevent the unlocking of variants which are protected (therefore protected for the person who locked it).
I havent ever tried this... but I beleive that variants of the type "system" need to be changed in client '000' and / or are subject to the client settings (SCC4).
Cheers,
Julius
01-16-2007 11:57 PM