Importing BW Objects

● You have implemented SAP Notes 1703061, 1759172, 1752384, 1733519, 1769374, and 1790333. ● You have upgraded your Modeler to SAP HANA 1.0 SP05 Revision 58.

● You have added BW schema in the SQL privileges for the Modeler user to import BW models. ● _SYS_REPO user has SELECT with GRANT privileges on the schema that contains the BW tables.

You use this feature to import SAP NetWeaver Business Warehouse (SAP NetWeaver BW) models that are SAP HANA-optimized InfoCubes, SAP HANA-optimized DataStore objects, Standard DataStore Objects, and Query

Snapshot InfoProviders to the SAP HANA modeling environment. These imported objects are exposed as SAP HANA information models and can be consumed for reporting using client tools such as, SAP BusinessObjects Explorer, SAP BusinessObjects BI 4.0 Suite (Web Intelligence via Universes, Dashboards, Crystal Reports), Microsoft Office and so on. The model properties are set based on the SAP NetWeaver BW models metadata.

Note

You can only import those Standard DataStore objects that have SID Generation set to During Activation. If you select a DataStore object, the resultant SAP HANA model is an analytic view with the same name as that of the DataStore object. If you select an InfoCube, two objects- analytic view and calculation view are created. In this 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. Conversion of BW analysis authorizations to analytic privileges

When you import the SAP NetWeaver BW InfoProviders, you can choose to import the relevant BW analysis authorizations. The analysis authorizations are imported as analytic privileges in the SAP HANA Modeler. These analysis authorizations could be associated with the InfoProviders or roles. You can import the analysis

authorizations in the following way:

● ○ You can choose to import only InfoProvider specific analysis authorizations. In this case, for all the authorization objects specific to the InfoProvider having 0CTAIPROV = <InfoProvider name>

corresponding analytic privileges are generated. The name of the analytic privilege is the same as that of the BW analysis authorization object.

○ You can choose to import analysis authorizations associated with the BW roles for the InfoProviders. In this case, all the analysis authorizations assigned to the selected roles are merged as one or more analytic privileges. The name of the generated analytic privilege is <InfoProvider

name>_BWROLE_<number>, such as, MyCube_BWROLE_1.

These analysis authorizations set on the InfoProviders are applicable at runtime for reporting. For example, consider that a user has the following authorizations in BW:

Table 8: AO1

0CUSTOMER 1000 - 2000

0PRODUCT ABC*

Table 9: AO2

0CTAIPROV CUBE1, CUBE2

0CUSTOMER 3000 - 4000

0CTAACTVT 03 (display)

● Now, if you choose to import only InfoProvider specific authorization, in the SAP HANA side, user would only be able to see 0CUSTOMER from 3000 to 4000.

● However, if you choose to import also role based authorizations, in the SAP HANA side, user would be able to see 0CUSTOMER from 1000 to 4000, and 0PRODUCT = ABC*.

● 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.

You can choose to place the generated models and analytic privileges in any of the user-defined packages in the import wizard and 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. Additionally, the calculated attributes created on the generated analytic views (in case of InfoCubes and DSOs) are also 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

● The following features are not supported on the generated SAP HANA models: ○ DSO without any key figure

○ Currency and unit of measure conversion

Note

Only currency mapping is supported and not the conversion. ○ Time dependent text and attributes

○ Non-cumulative key figures

○ Conversion routines in the BW system ○ Hierarchies

● The following features are not supported on generated analytic privileges: ○ Exclude operator

○ Aggregated value operator ‘:’ ○ Variables, User exits

○ Authorization on Key Figures ○ Authorization on hierarchy node

○ Exception aggregation such as, average, counter, first value, last value, no aggregation, standard deviation is not supported for generated measures.

● The query name for the Query Snapshot should not be the same as the BW InfoProvider name (this results in conflict on the SAP HANA side).

● Query Snapshot InfoProvider for BOE supports only key figures with aggregation types MIN, MAX, SUM, and COUNT.

1. Open the Modeler perspective.

2. In the main menu, choose File Import . 3. Expand the SAP HANA Content node.

4. Choose Import SAP NetWeaver BW Models, and choose Next.

5. To establish a connection with the SAP NetWeaver BW system (underlying BW Application Server), in the

Source System page, enter the SAP NetWeaver BW system credentials and choose Next.

Note

To add new connection details, select New Connection option from the Connection dropdown list. The connection details are saved and are available as dropdown options on subsequent logons.

6. Select the target system (an SAP NetWeaver BW on SAP HANA) to which you want to import the models, and choose Next.

7. Select the BW InfoProviders that you want to import and expose as SAP HANA information models.

Remember

In order to import the QuerySnapshot InfoProvider, make sure that the BW Query is unlocked in transaction RSDDB, and an index is created via the same transaction before it can be used as InfoProviders.

8. Select the target package where you want to place the generated models, and analytic privileges.

Note

Your package selection is saved during the subsequent import. Hence, the next time you visit the same wizard you get to view the package that was selected previous time. You can though change the package where you want to import objects.

9. If you want import the selected models along with the display attributes for IMO Cube and IMO DSO, select

Include display attributes.

10. If you want to replace previously imported models in the target system with a new version, select Overwrite existing models.

11. If you do not want to import the analysis authorizations associated with the selected InfoProviders, deselect

12. If you want to import the role based analysis authorizations as analytic privileges, select Generate Role based analytic privileges, and choose Next.

13. Select the roles to import the related analysis authorizations. 14. Choose Finish.

The generated information models and analytic privileges are placed in the package selected above. In order to view the data of generated models, you need to assign the associated analytic privileges that are generated as part of the model import to the user. If these privileges are not assigned, user is not authorized to view the data.