I use this data in combination with a SQL Script calculation view in a third graphical calculation view to join both data. In my example, I use technical DSO content data to feed data and consume data in a graphical calculation view. In the following explanations and examples, I use data based on an external SAP HANA view. The actual set of SAP BW modelling tools can be found using SAP Note1944835 – SAP BW Modeling Tools – Delivery Schedule 1944835 – SAP BW Modeling Tools – Delivery Schedule. I am running Eclipse Neon 3 and the latest SAP BW and SAP HANA add-ons. (I do not cover authorizations such as direct reporting on calculation views without a Composite Provider).Īll the screenprints are based on Eclipse as the development studio for SAP HANA BW development.
You can also use calculation views directly in Analysis for Office reporting. You also join SAP BW table information (such as an SAP Data Dictionary table) into one combined calculation view you can use in combination with an SAP HANA Composite Provider for BEx or Analysis for Office reporting. That means you use existing SAP BW inbound data (DataStore object based, as in an SAP BW entry layer).
My example (Figure 1) is a simple mixed approach.Īn example of the mixed data approach using calculation views Now I guide you through the creation of SAP HANA data flows with the help of calculation views (graphical and SQL Script-based views), as well as some pitfalls you may run into. In the SAP HANA environment using SAP HANA studio or Eclipse, SAP BW operators can very easily switch from the old-fashioned models to the new calculation-view-based modeling concept or run a mixed scenario of both worlds.)Īn SAP HANA procedure is a database-stored procedure that gives you programming functionality with the help of SAP HANA SQL Script, similar to ABAP functions. SAP HANA calculation views and procedures for complex scenarios help to calculate data on the fly to cut down unload and reload phases to zero when it comes to business-related changes in data staging or extension/reduction in a data model. (In a modern SAP BW powered by SAP HANA environment, it is wise to switch to virtual data staging instead of old-school data staging via persistency layers. It also keeps your operation costs for SAP HANA at a minimal level because less data in an SAP HANA database means less expense for licensing. My approach can help you to be flexible when it comes to design changes because there is no unload or reload of data in staging layers when business logic changes. Why use old habits with SAP application layers, storing more and more data in persistency layers, when it’s possible to calculate new reporting data on the fly? Using SAP HANA-based staging to enhance data flows without the physical staging of incoming data in several layers (SAP staging layer architecture ) is something I am working on at a customer site. This is, of course, a keystone of an SAP HANA implementation within SAP BW, but not the only one.Īlso Read: SAP HANATEC 12 Certification Preparation Guideįrom my point of view, the tight integration of SAP HANA functionality using SAP HANA studio or Eclipse to design new ways of data warehouse management is at least as important as reporting performance. Some may just be replacing an existing database with the modern SAP HANA database to gain speed in query execution and warehouse management. More and more SAP system users are implementing SAP HANA as the foundation and database for existing SAP BW installations.