Académique Documents
Professionnel Documents
Culture Documents
Applies to:
Document is applicable to all systems on SAP HANA Platform.
Summary
This document provides an introductory and practical overview of HANA. It will provide a conceptual
comparison as well as practical illustration.
Author Bio
Benedict Yong is a Certified SAP BI Consultant, and practitioner of Business Intelligence (BI) and Enterprise
Asset Management (EAM).
Table of Contents
Introduction ................................................................................................................................................... 3
Definitions ..................................................................................................................................................... 4
What is HANA? ......................................................................................................................................... 4
What are the benefits of HANA? ................................................................................................................ 6
What is BW-on-HANA? .............................................................................................................................. 7
What are the benefits of BW-on-HANA? .................................................................................................... 8
HANA Modelling step-thru ............................................................................................................................. 9
HANA Modelling Concept .......................................................................................................................... 9
Attribute View .......................................................................................................................................... 10
Analysis View .......................................................................................................................................... 11
Calculation View ...................................................................................................................................... 14
HANA Modelling vs BW7 Modelling ......................................................................................................... 20
Bridging HANA into BW7............................................................................................................................. 21
TransientProvider using HANA Model ...................................................................................................... 22
VirtualProvider using HANA Model .......................................................................................................... 23
Bringing together HANA and BW7 Data ...................................................................................................... 26
Getting Data at its Source: HANA Live ........................................................................................................ 30
Conclusion .................................................................................................................................................. 31
Credits and Content Sources ...................................................................................................................... 32
Introduction
What is HANA? Despite all the buzz and media attentions given to HANA, it only brings more confusion as
the definition continues to expand day-by-day.
I liken HANA as a proverbial elephant that has many version of truths for those have not seen it firsthand.
This paper seeks to provide introductory and practical overview of HANA.
Apart from answering what is HANA, it also seeks to provide answers to the following questions:
Definitions
What is HANA?
The term HANA is an acronym for "High-Performance Analytic Appliance.
SAP defines HANA as a modern in-memory platform that is deployable as an on-premise appliance or in
the cloud. As an appliance, SAP HANA combines software components from SAP optimized on proven
hardware provided by SAPs hardware partners.
In short, HANA is SAP in-memory solution. Its a database. You can run BW on it or you can run ERP (or
other Business Suites) on it.
SAP HANA holds majority of its data in the memory for high performance. However, it still uses persistent
storage to provide a fallback in case of failure. SAP promises a compliance to the ACID (Atomicity,
Consistency, Isolation, Durability) expectation of traditional databases.
During normal database operation, data is automatically saved from memory to disk at regular intervals
called savepoints. If a failure occurs, for example a power failure, the database will restarted in the same
manner as any disk-based database, and it is returned to its last consistent state by replaying the redo log
since the last savepoint.
SAP recommends that the Log file volume to be 3x 5x of the Memory for HANA.
Within the HANA box, we can choose to load all tables into it or selective (because the HANA box will still
have a size limit). At startup, all row-based table are fully loaded, but column-based table are loaded ondemand (default setting).
SAP HANA is not only just an innovative technology, it is packaged with additional tools (such as HANA
Studio for modelling, HANA appliances for specific business requirements)
What is BW-on-HANA?
As mentioned earlier, HANA is a database that BW or ERP can choose to run on. It is a logical step to move
BW into HANA, due to its speed performance and scalable and agile modeling.
From personal experience, BEx reports can have an improvement of 500x 3000x.
Typical BW
HANA optimized infocubes have a different structure with traditional BW7 infocubes.
InfoCubes in BW are modeled using the BW-extended star schema with 2 fact tables (an E table with readoptimized partitioning, and an F table with write/delete-optimized partitioning), Dimension tables grouping
sets of characteristics, and shared Master Data tables. This schema is optimized for classic RDBMS
technology.
With HANA technology, the schema can be simplified to one fact table (HANA can perform read, write and
delete operations equally fast on this layout) joined directly to the Master Data tables.
HANA optimized infocubes eliminate unnecessary joins and tables bringing in better performance. No
modelling is needed.
However, to harness the power of on-the-fly in-memory advantage, we need to apply HANA modelling.
HANA modelling comprises of views, these views generate real-time SQL statements behind the scene.
The advantage is in its non-persistency nature: data is read and not staged, this data-modelling agility is
coupled with native HANA DB in-memory speed.
The information views from HANA Modelling draw parallel to BW7 concept of MasterData and InfoCube.
At the Attribute View level, we can combine several MasterData tables and appoint a primary key. At this
stage, we can do Master Data reporting.
At the Analysis View level, we can combine several Transaction Data tables as the foundation, and enrich it
with Attribute View. At this stage, we can already achieve analytical reporting.
If more complex scenario exist, such as merging two infocubes, we can create a Calculation View.
In pages to come, we will explain the HANA modelling process in greater details. It will helps to explain what
is HANA modelling, but it will not be suffice to explain how to do HANA modelling.
Attribute View
It is used for Master Data Modeling
Can be used to join two or more master data tables (eg MARA, MARC, MAKT, MBEW)
No measures, only attributes
HANA Studio allows a sample data preview for the first 200 rows:
10
Analysis View
It represents an OLAP View with a Star Schema including measures and attributes. Represents an OLAP
View with a Star Schema including measures and attributes.
Can be used to join two or more transaction data tables (eg VBRK, VBRK) as well as master data
tables and Attribute Views
Includes a Data Foundation based on a Fact Table with measures.
Can be used for OLAP Analysis, typically within one functional area
At the Data Foundation pane, we can insert the transaction tables and perform joining.
11
At the Logical Join pane, we can see the transaction tables are represented as Data Foundation. We can
perform joining with Attribute View.
At the Semantics pane, we can set the details of the final columns.
12
HANA Studio allows a sample data preview for the first 200 rows:
13
Calculation View
It is used for Advanced Modeling, for instance cross-cube analysis or flexible joining
Calculation Views are used to address complex business scenarios. They are created using attribute
views, analytic views and tables.
It can be created directly using the SQL (Script) editor, or using the standard Information View
Modelling
14
We start by pulling in the Projection Task into the Scenario Pane. After defining the Projection Task, we will
drag in the Union Task.
During the definition of Projection (Selection), we can choose what column to pick and filter off rows.
In our case, we need to filter State = New York.
15
In the Union Task, we can map the output fields from the incoming fields (from the Projection).
16
HANA Studio allows a sample data preview for the first 200 rows:
17
Next we are going to include the next leg for State = Texas and include it into the Union mapping.
HANA Studio allows a sample data preview for the first 200 rows:
18
Alternatively, a Calculated View can be created base on scripting (instead of modelling panels).
19
Revisiting the earlier Calculation View Tax Scenario, HANA Modelling makes development flow with greater
ease. Using BW7 Modelling for the same scenario, we need to have two more cubes to split the data into two
different Taxation States for individual processing and union them back again with a MultiProvider. Not to
mention, the Process Chain needed to cater for the additional modelling steps.
For discussion purposes, we can have a quick-fix by using a restricted key figure in BEx. But what if the
criteria gets more complicated, how would BW7 Data flow handle and how would HANA Modeler handle?
In HANA Modeler, we are allowed to create multiple Projections (SQL Select / Where) and in each isolated
Projections we can tweak the flow of that particular set of data. Eventually when we are ready, we can merge
those Projections with a Join/Union task. For those who are SQL purist, they can query their way into a
Calculation View. Such flexibility and scalability will be very difficult for any persistent InfoProvider to rival.
HANA Modeler
20
From our earlier HANA Modelling, we have created 3 type of Information Views. We can use these for
illustrating how HANA data can be access by BW (specifically BEx).
21
22
23
24
Individual fields from the information view has to be assigned with a BW infoobject.
25
Integrating HANA data with BW7 can be achieved with one of the 4 methods:
26
27
28
29
30
Conclusion
In the past, ERP is used as a competitive advantage for enterprise-wide effective consolidation. As ERP is
becomes a norm for large enterprise, as well as, medium; this advantage has been diluted. The new
advantage resides in the data that ERP has collected.
With the inclusion of HANA and Businessobjects, the BI landscape is not limited to only Traditional BW7
Modelling and BEx reporting. We are now presented with unprecedented versatility. For instance, we have
options between Webi broadcasting capabilities versus traditional EP, BW MultiProvider versus Webi merge
queries, BW workspace versus Webi ExcelProvider, and so on.
Our challenge now, is how to harness relevant and applicable information that has long been left out in our
ERP treasure trove.
The emergence of ERP on HANA and HANA Live beautifully brings Analytics back to SAP ERP --- not as a
peripheral extension but an intrinsic business process. We should come to the understanding that Analytics
is the business process of business processes --- all business processes have KPI and needs to be
measured.
31
2.
32