How to Automate Generation of External SAP HANA Views to Save Time and Costs

  • by Joerg Boeke, Independent BW Senior Consultant and Solution Architect
  • October 2, 2017
Get a detailed guide (including SAP HANA ABAP code snippets) for speeding up your SAP HANA calculation views based on a DataStore object (DSO) by using external SAP HANA views based on classic DSOs. Instead of manually generating the external SAP HANA DSO views via the Administrator Workbench, the program helps you to select groups of DSOs to speed up implementation time.
Learning Objectives

Reading this article, you will learn how to:

  • Use external SAP HANA views in SAP BW/SAP HANA data modelling
  • Avoid mapping problems in SAP HANA studio or Eclipse Studio
  • Cut down implementation time by using a program to mass generate the external SAP HANA views instead of doing it manually one by one
Key Concept
One issue with SAP HANA is that unnecessary data is sometimes pulled from the database when using SAP HANA calculation views by using the old-fashioned ABAP approach of referencing the active data DataStore object (DSO) table such as /BIC/A… tables. In the SAP HANA environment, this should not be done to avoid problems with SAP HANA or SAP BW authorizations. SAP recommends using external SAP HANA views that can be activated on a standard DSO via the Administrator Workbench to avoid these problems. Individual activation on several hundred DSOs after migration to SAP HANA is time-consuming. You can implement an automation to the SAP HANA views to cut down time and project costs.

Running an SAP HANA database underneath your SAP BW system helps a lot in terms of performance. Most users migrated to the SAP HANA database to enjoy the speed for data loads as well as reporting performance. Many users, however, are not aware that besides performance, SAP HANA offers a lot more (for example, working with SAP HANA optimized models via calculation views).

Using that technology suppresses the need for keeping data in persistency layers instead of calculating new key figures and characteristics on the fly. Following this approach in my current project, we save millions of records by not adding more and more Advanced DataStore object (ADSO) layers. On the other hand, you can drop the need for increased SAP HANA licensing.

Within those new SAP HANA models, you can access existing InfoProviders (e.g., DataStore Objects [DSOs]) either by table name or via external SAP HANA views.

Joerg Boeke

Joerg Boeke is an SAP NetWeaver BW solution architect and senior consultant working with BIAnalyst GmbH & Co.KG, with 19 years experience in SAP NetWeaver BW, having worked on it since SAP BW 1.2A. He offers significant expertise in the SAP NetWeaver BW reporting area, including design, data integration, data visualization, performance optimization, and the cleanup of existing SAP NetWeaver BW systems. He is the author of SAP BW 7.x Reporting - Visualize your data.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.