Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Layouts - restrict authorisation to save user-specific only

Former Member
0 Kudos

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

1 ACCEPTED SOLUTION

Former Member
0 Kudos

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.

9 REPLIES 9

Former Member
0 Kudos

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.

Former Member
0 Kudos

Thanks a lot!

Former Member
0 Kudos

FYI - auth object S_ALV_LAYO does the trick. Thanks.

Cheers Stefan

0 Kudos

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

0 Kudos

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

0 Kudos

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

0 Kudos

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

0 Kudos

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

Former Member
0 Kudos

Message closed