how to enable authorization relevance on a navigation attribute

Upload: kalyanaraman-parthasarathy

Post on 02-Apr-2018

225 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    1/12

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 1

    How to Enable Authorization onNavigational Attribute

    Applies to:

    SAP BI or product release (release 701, level 0004, SAP EHP 1 for SAP Net Weaver 7.0).

    For more information, visit the For more information, visit theEDW homepage.

    Summary

    This document will provide information regarding implementing Authorization relevance on NavigationalAttribute. Also it contains the information regarding analysis Authorization and role maintenance etc.

    Author: Ravikanth Indurthi

    Company: Intelligroup an NTT Data Company.Created on: 1 December 2010

    Author Bio

    Ravikanth.Indurthi has been working in various technologies in SAP BI. He is mainlyresponsible for implementing SAP BI/BO projects and has worked extensively on SAP BIModeling and SAP BO reporting.

    https://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bi
  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    2/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 2

    Table of Contents

    Introduction ......................................................................................................................................................... 3Objective ............................................................................................................................................................. 3Steps: How to Enable Authorization Relevant on a Navigation Attribute ........................................................... 4

    Enable Authorization Relevant at Infobject level .......................................................................................................... 4Enabling navigational attribute at Info provider level: ................................................................................................... 4Role Maintenance ........................................................................................................................................................ 5

    Assigning role to USER: .............................................................................................................................................. 6Creation of Authorization Variable: .............................................................................................................................. 6Check the Report with End Users ID: .......................................................................................................................... 7Check the Report with Developers ID: ........................................................................................................................ 9

    Related Content ................................................................................................................................................ 11Disclaimer and Liability Notice .......................................................................................................................... 12

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    3/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 3

    Introduction

    It is known that we can create Authorization variable on Infoobject and restrict the data for the users. But ifwe do not have the required infoobject in the data target and available as attribute then also we can restrictthe data using the attribute.

    In this document it will be demonstrated steps to create the authorization variable on navigational Attribute.

    Objective

    Initially we need to enable authorization relevance for Navigational attribute at Infoobject level.

    Here Customer is the Infoobject and Branch & Distribution channels are its navigational attributes.

    To restrict the data with respect to Brach and distribution channels, authorization relevance has to be createdand assign to the respective users assigned to that Branch/Distribution channels.

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    4/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 4

    Steps: How to Enable Authorization Relevant on a Navigation Attribute

    Enable Authorization Relevant at Infobject level

    Enable Auth orization Relevantcheck box in the relevant Infobject for the required Navigational Attribute.

    Enabling navigational attribute at Info provider level:

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    5/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 5

    Role Maintenance

    There will basically two Logins:

    1. Developer ID(ZADMINBI): Used to create authorizations and assign end users

    2. End User ID (TEST_2PROLE): Used to check the reports based on their respective branches /Distribution Channels.

    Create a role and maintain Authorization object Role Maintenance with Developer ID(ZADMINBI) and the T-Code is RSECAUTH (Analysis Authorization)

    After Enabling the Authorization relevance at infoobject level, those objects can be visible

    Authorization restricted:

    Select the Branch Navigation attribute and restrict the values B0001 & B002.

    Similarly the distribution channels are also restricted with values GT & MT.

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    6/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 6

    Assigning role to USER:

    Assign the same Authorization role to USER (TEST_2PROLE): (T-code RSECADMIN)

    Creation of Authorization Variable:

    Create the query with authorization relevant variable on the Branchnavigational Attribute

    Variable represents: Multiple single values, Optional and ready for input.

    Similarly create authorization variable on Distr ibut ion channelNavigational Attribute.

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    7/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 7

    Check the Report with End Users ID:

    Log in to User ID: TEST_2PROLE

    RSRT Transaction, give the Query name: (YTEST_AUTH_OBJ)

    Values forBranch and Distribution Channel in variable Selection Screen:

    Here only restricted values are seen in the variable input screen.

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    8/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 8

    In the report filters restriction is clearly visible.

    Report Output:

    Output can be visible only for the restricted Branches and Distribution channels

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    9/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 9

    Check the Report with Developers ID:

    All the Branchesare visible in the variable entry screen:

    All the Distr ibut ion Channelsare visible in the variable entry screen:

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    10/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 10

    Enter all the values in the variable screen:

    Report output with all Branchesand Distr ibut ion channels:

  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    11/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    2010 SAP AG 11

    Related Content

    Analysis Authorizations

    Management of Analysis Authorizations

    The New SAP NetWeaver BI Analysis Authorizations

    http://help.sap.com/saphelp_nw70/helpdata/en/66/019441b8972e7be10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw70/helpdata/en/55/46eb411a7f6324e10000000a1550b0/frameset.htmhttp://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/ded59342-0a01-0010-da92-f6b72d98f144http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/ded59342-0a01-0010-da92-f6b72d98f144http://help.sap.com/saphelp_nw70/helpdata/en/55/46eb411a7f6324e10000000a1550b0/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/en/66/019441b8972e7be10000000a1550b0/content.htm
  • 7/27/2019 How to Enable Authorization Relevance on a Navigation Attribute

    12/12

    How to Enable Authorization on Navigational Attribute

    SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

    Disclaimer and Liability Notice

    This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported 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 orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.