S_RS_COMP1 authorization objects

[Former Member]

Hi all,

I have a security requirement which wants the users to be able to see the query but not change the query. But the powerusers should be able to copy the query and play around with the definition.

I tried using the authorization object S_RS_COMP and S_RS_COMP1. it worked almost fine but for a just an issue. When a power user copies the existing query and making changes and save with a different name, it works fine .. but at his next log on if he wants to change the same query for which he was the owner, its not allowing to change , rather the user has to copy it again and make changes and save it with a new name... so for every change the user is forced to save it as a new query though for the S_RS_COMP1 object i gave full authorization for the owner.

So is there some setting i'm overlooking or is there anyother object/profile/template which would allow me to achieve this.

Thanks in advance.

Mav.

[tom_francis2]

LauQ is correct, I just want to add that the trick with S_RS_COMP1 is that you need authorization S_RS_COMP AND S_RS_COMP1 before you are allowed do make changes. This in contrary with all other authorization objects where you are authorized when one authorization object allows you.

kr,

Tom

[Former Member]

HI All,

Thanks alot for the input. I could achieve the scenario where i would allow a user to create his own queries by copying from the standard query and will be able to delete or to do what ever the user wants for the queries he is owner of .. but now when a user is trying to access queries made by somebody else, the system gives a msg "Bex transport request is not available or not suitable" where as the system should say something like " You dont have authorizations to change". I'm wondering what could have gone wrong.

Any help or insight would be appreciated.

Thanks,

Mav

[Former Member]

This looks like a transport issue. Goto RSA1--> Transport Connection. Hit on the Bex Icon on the middle of the screen and assign a Standard Bex Transport request.

Thanks.

[tom_francis2]

If you are in production you should not use the BEX request, but rather open the system for changes to queries. (It's next to the button described above).

Change the setting for queries to everything changeable (not only changeable original).

kr,

Tom

[GFV]

Try TCode RSSU53 (or SU53) just after the power user has tried to change one of the existing QUeries: you should obtain the missing authorization value related to the missing authorization object of the power user.

Did you give to the power user the Object S_RS_COMP with Type of Rep Component REP (Query) Activity 02 (Modify)?

S_RS_COMP1 is used to control the same objects, with a check on the user name ...

Hope it helps

GFV

[Former Member]

Hi,

Authorizations on user's queries are set up via S_RS_COMP1 with field RSZOWNER = $USER.

Regards.

LauQ