28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Dependent Views<br />

Analytic views can be defined on attribute views, and calculation views that are defined on other modeling views. If<br />

a user requests access to such a view that is dependent on another view, the behavior of the authorization check<br />

varies as follows:<br />

● Analytic view associated with attribute view(s)<br />

A user can access an analytic view with associated attribute view(s) if one of the following prerequisites is<br />

met:<br />

○ The user has been granted an analytic privilege on the analytic view itself.<br />

○ The user has been granted an analytic privilege on an underlying attribute view.<br />

Result filtering is performed by a logical OR combination of all analytic privileges found on the analytic view<br />

and on its underlying attribute views.<br />

An analytic privilege on an analytic view with dependent attributes therefore does not restrict data access to<br />

the view, but rather increases it because the privilege on the analytic view is combined with privileges defined<br />

on the associated attribute views using logical OR.<br />

● Calculation view based on other view(s)<br />

A user can access a calculation view based on other view(s) if both of the following prerequisites are met:<br />

○ The user has been granted an analytic privilege on the calculation view.<br />

○ The user has been granted an analytic privilege on all underlying views if they are attribute, analytic, or<br />

calculation views.<br />

Result filtering is performed for each individual view. The underlying attribute, analytic, calculation views are<br />

authorized and filtered using the analytic privileges relevant for these views. The result of the top-level<br />

calculation view is then filtered using the analytic privileges defined on the calculation view itself.<br />

An analytic privilege on a calculation view based on other view(s) therefore further restricts data access to the<br />

calculation view as the privilege is evaluated on top of the result filtered by the analytic privileges defined on<br />

the underlying views (corresponding to a logical AND combination).<br />

Creation and Management of Analytic Privileges<br />

Analytic privileges can be created, dropped, and changed in the <strong>SAP</strong> <strong>HANA</strong> modeler and using SQL statements.<br />

The <strong>SAP</strong> <strong>HANA</strong> modeler should be used in all cases except if you are creating analytic privileges that use<br />

dynamic procedure-based value filters.<br />

To create analytic privileges, the system privilege CREATE STRUCTURED PRIVILEGE is required. To drop analytic<br />

privileges, the system privilege STRUCTUREDPRIVILEGE ADMIN is required.<br />

In the <strong>SAP</strong> <strong>HANA</strong> modeler, repository objects are technically created by the technical user _SYS_REPO, which by<br />

default has the system privileges for both creating and dropping analytic privileges. To be able to create, activate,<br />

drop, and redeploy analytic privileges in the <strong>SAP</strong> <strong>HANA</strong> modeler therefore, a database user requires the package<br />

privileges REPO.EDIT_NATIVE_OBJECTS and REPO.ACTIVATE_NATIVE_OBJECTS for the relevant package.<br />

338<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Setting Up Roles and Authorizations

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!