HANA – High Performance Analytic Appliance

What do you mean by High performance? – Below table contains 2 Trillion records. If you were to find
out top 5 customers based on amount, then MSSQL would take 8 hours whereas HANA would take only
6 Seconds.

Why? What are the reasons?

1> In memory database

Database – Collection of tables

Primary way to store the data is DISK (made up of Iron Plate) since it is cheaper. But in HANA, the
data is stored in memory (RAM – made up of transitors and capacitors).

- Data in RAM is closer to CPU than disk.

- Processing of RAM is faster (100-1000 times) in processing data.

2> Columnar DB
In table, data always gets stored in the form of files.

Store data in columns rather than rows.

Problem with row storage – for any search, system will start scanning all the data. Data in the
table is stored in a single file one after other.

Column storage –Based on the question we ask, it only goes to those columns. Each column is
stored in a separate file. Only relevant columns are scanned and irrelevant ones are skipped. In
this case, 4 files are created.

How these files are connected? – Means below, how system knows amount 200 is for customer
CO02? Via Row ID concept. Each data in each file is linked to a row ID. This builds the linkage.
 3> Massively Parallel Processing of data

In HANA, the complex table or program is broken into smaller subsets and each subset is processed by
different cores of a CPU (Central Processing Unit).

Above CPU has 4 cores – Quard core CPU. Each core can process 3.5 Billion scans per second per core
and 15-30 Million aggregations per second per core.

If the table has 30 billion records, if one core is involved, then it will take 10 seconds. If you have 10
cores, then it will take only 1 second.
Role – SAP HANA Application Consultant. What will we do in the project?

3 things :-

- Data Modelling – 60%

Defining the relationships among the tables. How they are inter-connected.

For multi dimensional analysis of the data.

- Data Provisioning – 20%

Movement of data from one place to another place.

- Data Reporting – 20%

Presentation of data to end user (BOBI – Business objects Business intelligence).

Comes under Analytics portfolio.

3rd Party reporting tools – Tableau, FIORI etc.

Side Car Scenario:-

SLT – SAP Landscape Transformation

Used for real time transfer of data. For e.g. If you post a sales order in ECC, within milli seconds (with
minimum latency), data will be available in HANA. To find the stock availability.

BODS – Business objects data services

It is known as an ETL tool. It is optimized for batch processing. For e.g. Salary calculations.

DXC – Direct extractor connection

It is used when you already have BW systems. If you don’t use BW, then this method can’t be used. Using
RFC communcation, data from ECC gets moved to BW. Whatever data you are sending to BW, the same
can be transferred to HANA using DXC. Why you want the data in HANA rather than in BW system –
because of performance.

SAP has more than 2lakh 25 thousand customers. Only 14K customer have BW.

SDA – Smart data access

When you want to connect to a non SAP system / non SAP databases(Oracle, DB2, Sybase, MSSQL,
Teradata).

Why should we move the data from source to target ? – already explained above.

Main Car Scenario :-

When you have HANA database directly under ECC.

Existing database is removed and replaced with SAP HANA.

Course Contents :-
Attribute view – For Master data modelling

Analytic view – For transaction data modelling -> Multi dimensional analysis

Calculation View – For both Master data and transactional data

Variables in HANA – Input boxes for end users to enter data

Meta data import to SAP HANA – To move information models etc from dev to quality to prod.
SQL Script – Write custom functions. HANA is all about Model to code which means – 90% of course is
only navigation (click here and then click there – navigation steps). When we model, system generates
the code. Rest 10% is coding where you write custom code to suit to business requirement.

CE functions – Calculation engine functions given by SAP. You can use these functions in the data models.

Procedures – To improve performance of processing data.

Hierarchies – Defining Parent – child relationship.

Data reporting tools – On BOBI, you have crystal reports, Lumira, Design studio, Analysis for office,
Analysis for OLAP, BO explorer. All these are different tools to visualize the data where each tool has its
own importance.
End to end installation of SAP HANA -> Install VMWARE. Inside vmware, install suzi linux. Inside suji linux
install SAP HANA database. How to configure & administor HANA database - Back up, Recovery, High
availability. Not recommended for developer but if you know then it is good.

Create Users / roles and how to secure database and its data.

Deals with Analytic previlages.

How BW and HANA can compliment each other. How both can levearge each other to provide a better
solution.

For 14K customers who invested so much in BW, SAP provided a way to use HANA as database. This is
known as BW powered by HANA.

We can import data models from BW etc.

S4 HANA – Simplified version of all SAP applications.

When HANA was introduced, only HANA database was introduced.

Then slowly SAP applications started to support on SAP HANA.

Just replacemnet of a database can give performance only.

Later SAP not only replaced database but we will also simplify how an SAP ABAP application layer can
work. To store/present data in a simplified way.

In terms of simplication, SAP removed aggregates, removed redundant tables, removed indexes.

Also, applications can be deployed in cloud.

Without ABAP application layer, we can do all the developments in HANA.

HANA can process structured and semi structured data.

Demerites - HANA can’t process unstructured data – Analysis of pattern of photos and videos. Big data
like HADOOP can process these requests. In HANA, you can save this data but can’t process them.

System access for 6 months –

ECC IDES 6.0 EHP 7

BODS 4.2 SP 6

BOBI 4.1

S4 HANA 1511 edition

HANA SP 11

SLT 2.0

BODS 4.2

Email – NAGARJUNA.K@GMAIL.COM / 7799911129

SAP Certifications :-

Associate level – No experience

Professional Level – SAP Pre-requisite - at least 3 years of hands on experience (send resume to SAP and
then SAP will evaluate it).

Write in Teched also - end of the year – Bangalore.

Topics :-

HA 100 Introduction to SAP HANA

HA 300 Implementation and Modelling

HA 350 (Optional) Data Provisioning

HA 900 Business Suite Powered by HANA

BW 362 BW powered by HANA

S4H01 S4 HANA

Mandatory – HA100, HA300, HA900, Hands on Lab (Assignments given by SAP)

HA 400 - ABAP

S4 life cycle :-

Traditionally, first came HANA, followed by Suite on HANA, followed by the simple finance add-on on ERP
6.07 or 6.08 and finally S4/HANA.

1> HANA Hana database

2> SoH Business suite powered by HANA / Suite on Hana

Take a product of SAP business suite running on “any DB” (E.g. ECC Ehp7) or above, and migrate
the “Any DB” to an SAP HANA database, you will get an “powered by SAP HANA system”.
Upgrade all the systems of the suite in the same way, and you will get a Business suite powered
by SAP HANA.

Version 1506 – 15 is year and 06 month => ADDON to existing ECC system – Simple Finance.
Later named as S4 HANA FINANCE Simple Finance

1511 Nov 2015. Full fledged version of HANA – Logistics + Finance.

Very very important :-

https://blogs.sap.com/2017/09/05/hana-s4-hana-suite-on-hana-soh-simple-finance-s4-hana-finance-
lets-have-the-right-wording/

What is the best approach :-

Existing BW customer – can go for side car or Main car design

New customer – should go for HANA not BW.