BEX Query Authorizations

We are have authorization issues with Queries.   We have created  a generic Role that has some Standard Query's for our Company attached to this Role.

We give access to this role to our user community.  The problem we are having is that the users can Execute the queries and what they are suppose to do is only Save the Workbook to there favorites.   We are running across a problem because some of the users are saving the workbook as existing workbook.   So when they do this it wipes out the Query in that Role.    How can I stop users from overlaying the MASTER Query.   There has to be a way that you can protect a query so that it cannot be changed.    Because we have generic queries that are being used throughout our company, I need to be able to protect the query so that it can only be saved to users Favorites.
 

Go to role maintenance (PFCG) -> Authorization -> Change Authorization Data.

Open Basis - General Functions -> BC-SRV-KPR-BDS and restrict the user activities set like "Display, Print, Retrieve from Archive, Determine, Assign".

User with appropriate role could not be able to overwrite WORKBOOKS (!!!).

As for QUERIES, address to Business Information Warehouse -> BEx - Components and restrict Activities retaled to Queries - then users with appropriate role could not be able to overwrite GLOBAL DEFINITION of QUERY (!!!).

So, you can see, you need to restrict access to queries and workbooks separately.

SAP Books
SAP Business Warehouse, Functional, Basis Administration and ABAP Programming Reference Books

Main Index
SAP Basis, ABAP Programming and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.