IT Operations Management (ITOM)

Multi-Tenant reports using SHR Groups

Multi-Tenant reports using SHR Groups


SHR supports grouping dimensions and CIs. SHR Reports are parameterized by groups. This allows SHR users to filter reports based on groups.   RtSM Views and OM NodeGroups form default groups available to SHR users. In addition to RtSM Views and OM NodeGroups, SHR supports creation of Custom Groups based on dimension/CI attributes.


SHR Groups in conjunction with BusinessObjects(BObj) Restrictions provide a means to achieve report level multi-tenancy. SHR administrators may define users (or user groups) in BObj and associate these users to specific SHR Groups. Once this association is created, users are restricted to their SHR Groups. 


There are a couple of points to be noted:

  1. SHR Reports support both Optional and Mandatory prompts. While Restrictions work on both, users may skip Optional prompts and gain visibility to all groups. To avoid this, ensure prompts are made Mandatory
  2. Please make a copy of the BO Universe before changing it!


Please refer SHR Online Guide for creating a Custom Group. The rest of this write-up describes associating a BObj User to a SHR Group. This is an one time activity that should be carried out for each BObj User or BObj User Group.


BObj Restrictions apply to a BObj Universe. Create a new Restriction as shown in the figure below:



The new Restriction created can then be assigned to an existing BObj User (or a BObj User Group).

The following step demonstrates associating a BObj Restriction NG1_Restriction with BObj User NG1_User:



Now that a Restriction-User association has been created, the next step is to add a condition to the restriction. This condition defines the nature of restriction that will be imposed on the associated user.


Edit the restriction to add a SQL WHERE Clause:



SHR stores all group definitions in a table named K_Group.

The next step is to define a list of SHR groups against the created Restriction.


The following condition restricts user NG1_User from viewing or accessing any group other than 'SM_PA'.



On completion of the above steps, the user NG1_User is now restricted to selecting SM_PA Group only on all SHR Reports and has no visibility to any other group that may be available to other users. This applies to all reports that include Business View(s)/Group(s) in their prompts.



The above technique is applicable for all conformed dimensions/CIs available in SHR.


BObj Restrictions may be used within a non-MSP/single-tenant installation as well.

  • operations bridge
0 Kudos
About the Author