Query Protection

[Former Member]

Is there a way to protect a set of queries from being changed in production but allowing them to still be copied? Also users would have access to change other queries.

Thanks for any advise.

Richard

[Former Member]

Hi Richard,

did you read the chapter about Authorization in the online Documentation?

http://help.sap.com/saphelp_nw04/helpdata/en/80/1a68a7e07211d2acb80000e829fbfe/frameset.htm

and

http://help.sap.com/saphelp_nw04/helpdata/en/80/1a68b4e07211d2acb80000e829fbfe/frameset.htm

Just give them display (and execution) authority to those queries (just stick to some naming conventions for the queries). Copy should then still be possible.

Heike

[Former Member]

Hi Richard,

if you have a proper naming convention for the query you can easily achieve this. Users will then not be allowed to create or change queries in p system of a specific name but can copy them and create or change other queries.

Siggi

[Former Member]

Hi Siggi,

I agree with you..

All the queries in Production follow a naming convention starting with P_XXXXXXXX which cannot be changed .but can be saved by different name and then changed..

Could you pls describe the procedure to do it..

I believe its done in PFCG..defining specific roles..

Pls Clarify

Ashish..

[Former Member]

I did read the chapter but will re-read it.

The naming convention idea sound great.

[mstrein]

Hi Richard,

based on proper naming convention you can protect all BEx elements (Queryies, Views, RKF, CKF, VAR) using S_RS_COMP multiple times in a role. Especially Variables need proper Protection because they do not depend on the Cube but on the infoObject.

Take Care,

Michael

[Former Member]

Michael,

Thanks for the help.

[Former Member]

Hi Richard,

We have implemented a authorization check due to which the user can run queries but not change any queries in production..

They can make a copy of it and then can change it..

The basis team has been dealing with this..

I will surely try and find out and confirm this to you..

Ashish.

[Former Member]

Hi Richard,

You mean you want to protect only a set of queries and not all queries?

To my knowledge, I think its <b>ALL OR NOTHING</b> meaning, either you protect all or you protect nothing. Its because the <b>OBJECT CHANGEABILITY</b> can only be set across all objects. I have no idea if a single query can be protected from changes.

Best Regards,

Jkyle