SAP HANA Developer Guide - Get a Free Blog

case, the name of calculation view and analytic view is same as that of the InfoCube and the name of the analytic
view is suffixed with _INTERNAL. The analytic view generated in the case of an InfoCube is used internally for the
generation of the respective calculation view and is not available for client consumption. If you select a
QuerySnapshot InfoProvider, the resultant SAP HANA model is an analytic view.
When you choose to import the SAP NetWeaver BW InfoProviders, the analysis authorizations set on the
InfoProviders are also imported as analytic privileges in the SAP HANA Modeler. The name of the analytic privilege
is the same as that of the BW Analysis Authorization object. These analysis authorizations set on the
InfoProviders are applicable at runtime for reporting.
Note: In the case of Query Snapshot, all the BW Analysis Authorization objects which are applicable on the
underlying InfoProvider of the query, will also be applicable on the Query Snapshot. These BW analysis
authorization objects will be imported as analytic privileges when importing the query snapshot.
The generated models and analytic privileges are placed in the sap.bw package. You can choose to enhance the
generated models. However, with the subsequent import of the same objects, the changes are overridden. Also,
changes made to the models on BW side are not automatically reflected in the generated models. This may lead
to inconsistent generated models based on the changes made to the physical tables. To avoid this, you need to re-
import the models.
Caution:
● The calculated key figures (CKFs) and restricted key figures (RKFs) defined on the SAP BW models
are not created for the generated SAP HANA models. In this case, you can create an RKF as restricted
measure in the generated analytic view. For CKF you can create calculated measures in the generated
calculation view or analytic view. These CKFs and RKFs are retained during subsequent import. If a
change is made to the characteristics or key figures based on which these restricted measures and
calculated measures are created, this may lead to inconsistency in the generated models. In this case,
you need to manually adjust these restricted measures and calculated measures.
● The restricted measures and calculated measures that you define for the analytic view that
correspond to a query snapshot, is overwritten with the subsequent import.
● The BW analysis authorization objects are not always mapped 1:1 with the generated analytic
privileges on the SAP HANA Modeler side. If the BW Analysis Authorization object does not include
0TCAIPROV, the authorization is not moved to SAP HANA. Also, restrictions created in the BW
analysis authorization are skipped if they do not match with the restrictions supported by the SAP
HANA Modeler. In such cases, the data available for reporting for a SAP HANA Modeler user differs
from the SAP NetWeaver BW user with the assigned restrictions.
For reporting purposes, data which is visible for a user is:
● For a DSO generated analytic view, all the data in the active table is available for reporting.
● For an InfoCube generated calculation view, only successfully loaded requests are available for reporting
(these are the green requests in manage InfoCube section).
Restriction:
SAP HANA Developer Guide
Setting Up the Analytic Model
P U B L I C
© 2012 SAP AG. All rights reserved. 155