This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
SAP Business Intelligence (BW) 7.0.For more details, visit the EDW homepage.
Summary
This document will explain the steps to create Info object (characteristic value) level authorization for a reporting user in SAP BI 7.0
Author: Avinash Verma
Company: L&T Infotech
Created on: 09 February 2011
Author Bio
Avinash Verma is a SAP BI Consultant currently working in Larsen & Toubro Infotech Ltd. He has involved in implementation and development of various BI/BW projects.
Business Scenario .............................................................................................................................................. 3
Transactions used ........................................................................................................................................... 3
Info Object Maintenance for Authorization ......................................................................................................... 3
Management of Analysis Authorization ........................................................................................................... 4
Related Content ................................................................................................................................................ 17
Disclaimer and Liability Notice .......................................................................................................................... 18
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
SAP BI Authorization/security is an integral part of any BI implementation. Integrating all the data coming from various source systems and providing the data access based on the user‟s role is one of the important part of all the BI Projects.
Security of SAP R/3-ECC systems are based on the activities e.g. transaction level, particular activity level etc. while SAP BI Authorization/security is focused on what data user can access.
Authorization in BI is categorized by major 2 categories:
Administrative Users – The way we maintain security for administrative users is same as SAP R/3-ECC security but we have additional authorization objects in system which are defined only for BI objects.
Reporting Users – Analysis Authorization using transaction RSECADMIN, to maintain authorizations for reporting users.
Business Scenario
There are 5 company codes and we are going to restrict BI reporting user (USER1) to access data of only 2 company codes out of 5. And Company code is also not a part of user input selection parameter in report. In this eg.1000 and 2000 are the Company codes of the user USER1 for which we are going to give access. So whenever the user USER1 executes the report, he will only be able to see the data relevant to Company codes 1000 and 2000 in the report.
Transactions used
RSD1 - To maintain info object authorization relevant.
PFCG – To maintain roles.
RSECADMIN – To maintain analysis authorization and role assignment to user.
Info Object Maintenance for Authorization
Use RSD1 transaction to maintain infoobject. Mark the Infoobject Authorization Relevant and activate it. In this case Infoobject company code is used and authorization relevant field is checked.
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
These 3 special characteristics are mandatory while creating authorization object.
0TCAACTVT: This characteristic handles the general activity like create, change, display etc.
0TCAVALID: This characteristic handles the authorization for InfoProviders, by default it gives access to all the InfoProviders i.e. full access. We can restrict authorizations for particular InfoProviders using this characteristic.
0TCAVALID: This characteristic handles the validity of an authorization. Always valid (*) is set as the default for validity. You can restrict this validity. You can also specify a single value or an interval.
These special characteristics must be included in at least one authorization for a user; otherwise the user is not authorized to execute a query.
Step 3:
Add InfoObject to authorization structure and maintain value authorization for this infoObject as per requirement.
e.g. 0COMP_CODE (Company code) is inserted into authorization structure.
Note: Also include all Authorization Relevant Objects which are used in that infoProvider in addition to the above additional 3 objects otherwise you may get "No Authorization" error when you execute the query.
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Double click on the 0COMP_CODE to maintain value authorizations, as per Business scenario Company code 1000 and 2000 has been added to value authorization and „Save‟ this authorization. Here we are using operator „EQ‟ for single value authorization
You can authorize single values, intervals, simple patterns, variables, and hierarchy nodes.
Hierarchy Nodes authorization are maintained in the tab „Hierarchy Authorizations‟
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Note: 1.User with Authorization Object 0BI_ALL is having full access to data, and can overwrite any other Authorization Objects assignment to it. 2. Authorizations can be assigned to User either through Analysis authorization (Manual or Generated)or through Roles/
Profile (Role-Based).
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
But, in this Business scenario, Company code should not be a part of user input selection variable, it means output of query should directly display the data for company code on which User has access authorization.
Click on to edit authorization variable, in detail tab, uncheck the “Variable value can be entered by user” checkbox, save and execute query with the same user ID i.e. USER1, this time output of query will not prompt for user input variable, it will directly show the data for authorized company code (1000 and 2000).
BI 7.0 Reporting Authorization Based on Characteristic Value Level
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.