Sap hana documentation @ TL Technologies

SAP HANA 1.0
By Mr. Vijay K Naidu

We Teach…..You Lead
D.No : 7‐1‐619/A/38, Behind Huda, Gayathri Nagar,
Ameerpet, Hyderabad ‐ 500038
Contact: M: 8885304545 L: 40066296

2
T L TECHNOLOGIES @ 8885304545

About TL:

We are Specialist’s in SAP Class Room Trainings
& Online Trainings.

This Document covers Introduction to SAP
HANA that includes Architecture & Data
Provisioning with few Certification stuff. In the
next Release we are publishing SAP HANA
includes HANA STUDIO , Security BI4.0 on
HANA DB With Realtime Scenario’s & Interview
questionnaires.

3

SAP HANA 1.0 @ T L Technologies
Version 1.0 Doc
By Mr.Vijay K Naidu

Agenda
1. Introduction to SAP HANA.
I. What is SAP HANA?
II. Why its required?
III. What HANA DB Contains?
IV. Sap HANA Data Flow.
2. SAP HANA DB Architecture
3. SAP HANA Architecture Overview
I. Load Controller
II. Replication Agent
III. Data Services
IV. In‐Memory Studio
V. BI 4.0
VI. Session Management
VII. Request Processing & Execution Control.
VIII. Persistence Layer Importance
IX. Why does HANA DB Need a Persistence Layer?

4
X. Backup & Recovery.
XI. Importance of Columnar Storage
XII. Importance of Transaction Manager/Authorization manager &
Meta Data Manager.

4. SAP HANA SYSTEM LANDSCAPE
5. HANA SIZING
DATA PROVISIONING
I. IMPORT
II. What is SAP LT Replication.
SLT ‐ Sizing Considerations.
Key Benefits.
SLT Architecture (with SAP & Non‐SAP)
LTR Transaction Importance
Different Operations of SLT.
Importance of SLT.
SLT Sizing.
Navigation of SLT taking LOAD & Replication as example.

III. SAP BO DS4.0 and SAP HANA DB.
. Process Flow In Data Services.

. ODP & its importance.

IV. Direct Extractor Connection:
what is DXC?
USE OF DXC.

5
INTRODUCTION ‐ SAP HANA :
SAP HANA….In‐memory Database.
Sap Hana = High performance analytical appliances.
Developers: SAP AG (GERMANY)
It sits on Suse Linux Operating Systems
Why it is required?
In‐Memory Computing is a technology that analyses massive volume of structured or unstructured
data in local main memory so that the results of complex analyses and transactions are available at
your finger‐ tips – and business decisions can be executed without delay.

Sap hana is a combination of Hardware & S/w Appliances (CE Engine).
Hardware is provided by Vendors IBM, FUJITSU, CISCO,and HP& DELL……

What HANA DB Contains?
HANA DB contains:

6

Multi‐Core CPU’S ‐>To process the data in& out of DB.
Rows & Columns Relational Engine in HANA Architecture( initially data is loaded will be loaded both
row wise & column wise but HANA Supports Columnar storage, so whatever the data loaded in Row will
be act like a meta data.
Compression: This DB has got a good Compression technique, with SP3 compression ratio is 5X and with
Current Service Pack compression ratio 20X.
Whatever the data which is compressed will be partitioned based on available RAM’S inside the DB.
Aggregation table: ‐NA‐Here there is no concept of Aggregation .
It enables the Real Time Replications – i.e it is something like Delta mechanism in BW.
What is Delta: it’s a type of replication of data to HANA DB, we can upload new data or changed records
after Historical Data loads.
In HANA Data resides on Main Memory.

7

SAP HANA DATA FLOW:

In The above Data flow there are two replication processes is shown

1. SAP LT Replication – Trigger based
2. Data Services 4.0/4.1 is supported ETL Based.

8

SAP HANA DB Architecture:

Then most important component of HANA DB are Index Server.
Then index server contains the actual data stores and the engines for processing data.
Index server uses preprocessor Server to analyze Text data & extracting information on which Text data
resides.
Name Server has the information about Topology of a SAP HANA as it is used to identify where the
components are running & on which data is located.
. Statistical Server collects all the information related to performance, status & resource consumption
from all the components belonging to SAP HANA DB.
Statistical Server also provides the history of measurement of data in the system for further analysis.
. XS Engine is optional it is used map Persistence model with Consumption model via HTTP.

9

The above screenshot depicts SAP HANA Architecture:
1. Session management:  Session mngt used to capture how many Perceptive opened in the HANA
STUDIO’s & captures version management.
2. Request Processing & Execution Control
SQL PARSER/SQL SCRIPT – All the SQL procedures will be handled by these two.
MDX – Script Logic/ Macro’s & formula’s in excel will be handled.
Calculation Engine or Planning Engine:  All ABAP or Planning related to BPC/APO/ IP will be
handled.

3. Persistence Layer: Backup & Recovery of data will be handled here.

Whatever the data taken backup we will specify as SAVEPOINT.

10
So we can take the back of data which we have saved.
Navigation: go to HANA STUDIO Select Server click on Back‐up
A new window will open give the destination information where do you want to take the
backup.
Usually path would be Application server.

All the backup of data will be moved to Page management & log information i.e before image and after
image will be moved to Logger.

After certain span of time Data which was taken backup will be moved to Data Volume & from Logger
log details will be moved to Log Volume.

In Memory Data regularly Saved to Disk:

11

Data:
SQL data and undo Log information
Additional HANA information, such as modeling data

LOG:
Information about data changes(Redo Log)
Directly saved to Persistence storage when transaction is committed.
Cyclical overwrite (only after Backup).
SAVEPOINT:
Saved data backup is called SAVEPOINT
Changed data & Undo Log is written from memory to Persistence Layer.
What is Undo Log:
Data Pages & before images are the Undo Logs and these are written to data volumes.
What is Redo Log:

12
After Images are Redo & these are written to Log volumes.
When data/Log entries are written to Disk?
Redo Log entries are written to Log volumes at latest when a transaction ends, Changed data itself
written at latest when a savepoint is performed.

13
BACKUP & RECOVERY:

14

Importance of Columnar Storage:

Transaction manager: He monitors how the data is loading to HANA DataBase (Column wise), if at all any job
has failed he shoots a mail to Developer with necessary screenshots.
Authorization Manager: if at all any authorization is given to any view it will be tracked.
Meta Data manager: System generated files will be monitored.

15
7. Reporting:

EXCEL Based : this excel report is used with Live Cache and display any hierarchies defined in the View’s
level.
IDT: Information design tools(UTD in early version),
Business Layer – Universe Layer
Different BI4.0 reporting tools
1. Web intelligence
2. Crystal reports
3. Dashboard
4. Bo Explorer
5. Visual Intelligence.

8. In‐memory Studio:

HANA STUDIO : Place where development work needs to be done.
Administration: SAP HANA ADMINISTRATOR Activity performed here.

9. ERP

Load Controller:SAP LT Replication: used to extract SAP ECC Application table to HANA DB.
Replication Agent :used to extract data from Sybase DB to HANA DB.
Dataservice:Used to extract SAP ECC(TABLE/DATASOURCE)/SAP BW & NON‐SAP DATA to HANA DB.

Note: Calculation in BW which is present @ Application Layer is present in
DB layer in HANA DB.

16

The above figure depicts the SAP HANA Landscape, where HANA DB is connected with various
Replication tools & BI4.0 reporting tools.

HANA SIZING:
Based on size of data in an organization, SAP has come up with different Configuration:

17

18

Data Provisioning

Sap HANA Has come up with various Data Provisioning Scenario’s:

1.Import:
Using Import function, we can import flat file data into HANA DB.
Supported file formats are : .csv & .xls
This option has come up with SP4.
If required file is not available in the HANA DB,then you need to create a structure based on file
format
Always mapping should be 1:1.

19
When new data is loaded it will append to existing data, but it will not overwrite or add.

Navigation:  Goto HANA STUDIO
IMPORT ‐ Upload data from FLAT‐FILE
Select the source file to be uploaded and target Schema where the file to be loaded.

SAP LT Replication:
What is SLT?
SAP Landscape Transformation.
Use: This Trigger based replication method used to extract SAP ECC Application Table to HANA DB.
SIZING Considerations:
‐ SLT System must have atleast following configurations:
‐ File‐system: 100GB.
‐ RAM: 16 – 32 GB
‐ CPU: 2‐4 Cores
‐ Number of recommended bg jobs available:10.

20

When can we configure LT SERVER:
If your system is <EHP5 & = SAP NETWEAVER 7 Kernel then you can install your SAP LT Server inside your
SAP SOURCE SYSTEM.
If your system configuration is not matching the above requirement then it is suggested to go with
Separate standalone Server.
SAP LT Server Architecture:
Below Shown figure is In‐Build Scenario:
<EHP5 & = SAP NETWEAVER 7 Kernel:

21

In this Scenario, we have SLT Server installed inside the SAP Source system.

If at all System Configuration is less than required then we need to approach below scenario:

Note: Here we have SLT as an Standalone server, connectivity between SLT & SAP SOURCE SYSTEM is
RFC & Connectivity between SLT & HANA System will be DB Connection.

22
SAP LT Replication also used to extract data from NON‐SAP Data.

Connectivity between Non‐sap & SLT is DB Connection, SLT & HANA SYSTEM is also a DB Connection.

Different Options:
Read Module: It is used to Read/extract the data from Application table & Logging Table.
Structure mapping & Transformation: it is something like mapping.
Write module: What‐ever the data extracted from Appl. Table & Logging table will be initially stored
here from here using the DB connection data will be moved to HANA DB.
Logging Table: It stores the newly or changed data records.

LTR – Transaction:
It is the transaction used to monitor all the jobs like Replication/Load/Trigger…

23

24

25

26
Different Operations of SLT:

LOAD: it is similar to FULL Load.
Replication: it is just like Init load in BW or when you trigger Replication it extracts all historical data
from source and enables DB trigger.
Stop Replication: To delete the Replication.
Suspend: to pause the replication
Resume: to continue replication.

Important Stuff:

27

The table is IUUC_TAB_ALLOWED in the SAP SOURCE SYSTEM restricts the set of tables that are
allowed to be defined for Load/replication from the HANA STUDIO.
Packages need to be installed as part of SLT are:

Below Screenshot depicts the Configuration of SLT.

28

29
SIZING:

30

31

32
Navigation of SLT:

Login to HANA Studio:
Select Data Provisioning Under Data

Select LOAD Command:

33

34

select table PA0002 to load:

35

SELECT THE TABLE & and click on ADD & say finish

36

Select Finish to start the Load Job.
Similarly:
Replication:

37

Selected the VBEP to replicate:

38

39

and say Finish.
Below screenshot shows the Scheduled jobs:

40

SAP BO DS4.0 and SAP HANA DB.

41

Data Services is the Engine to load data into ICE(In‐memory Calculation Engine).

42

43

Direct Extractor Connection:
Is the extraction tool used to extract SAP ECC Datasource to HANA DB.
It is the one of the Data Provisioning tool which has come up with SAP HANA.
DXC is used to Extract Business Content Data sources to SAP HANA DB.
Create HTTP connectivity of DXC to SAP HANA System.
Note: Need to create User for DXC at SAP HANA & Schema for DXC also.

44

Source for DXC is BI content Datasources.
Target is In‐memory DSO.
Below shown figure depicts how the data flow to In‐Memory DSO using DXC.

45

Here:
In the above scenario, when your make a entry in the Sales Order it reflects in the respective Application
tables in SAP source system & then using the  Update mode data moves to the Data source from there
to the HANA System where our data target is In‐Memory DSO. Initially data comes to Activation queue
from there upon activation data moves to Active Table,  here 3rd
table is Status table(Change‐Log).
Naming Convention of Active table: /BIC/A<Datasource_name>00
i.e here in our example we are taking Sales order Item Datasource, so we can define as
/BIC/A2LIS_11_VAITM00.
Similarly Activation queue: /bic/a2lis_11_vaitm40.
Note:
Two infopackages need to be created,
a. Init
b. Delta – as it supports Delta.

46
De‐merits of DXC.

1. It doesn’t support NON‐ CUMMULATIVE KEYFIGURE.
So for handling inventory it is suggest that to go with BW System instead HANA.
Below are the list of Datasources where HANA Does not support:
0CFM_INIT_POSITIONS
0CML_INIT_BUDAT
0CML_INIT_DDISPO
0CML_INIT_DFAELL
0RE_1
0RE_3
0SCM_LIM_1
2LIS_02_SRV
2LIS_03_BX
2LIS_03_S197
2LIS_03_S198
2LIS_40_S278
2LIS_03_BF
0BV_BEV1_EM_CUSTSTO_BW_GET_TD
0RE_2
0RE_3
0RF_REASLOC_ATTR
0SCM_LIM_1
0SCM_LIM_2

____________________________End of Version 1_____________________

Sap hana documentation @ TL Technologies

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (9)

Similar to Sap hana documentation @ TL Technologies

Similar to Sap hana documentation @ TL Technologies (20)

Recently uploaded

Recently uploaded (20)

Sap hana documentation @ TL Technologies