You are on page 1of 3

1

ABAP Programming on SAP HANA

Day 2
Agenda:

1) Identify HANA specific settings in ABAP Dictionary

2) Describe the various code-to-data concepts

3) SAP HANA as Secondary Database – Access via Open SQL

Common Changes to SAP Table when SAP HANA is Primary Database –

1) De-Pooling and De-Clustering of tables

2) Deactivation of Secondary Indexes

New Features added to Data Dictionary

1) Storage Type for tables

2) De-Clustering and De-Pooling

3) Deactivation of Secondary Indexes

4) Full Text Index

What’s in for ABAP Developers?

Accelerate →

Extend ->

Innovate

Steps for Transition of ABAP code for HANA

1) Detect

2) Optimizing

3) Innovate

New Programming Paradigm

DAY 2 - ABAP ON HANA 1


SAPYARD.COM
2

ABAP Programming on SAP HANA

Bottom-Up Approach and Top Down Approach

Before AS ABAP 7.4 SP02

Native SQL Native SQL


SAP HANA Views – DB Layer Stored Procedures

After AS ABAP 7.4 SP02

External Views DB procedure proxies


SAP HANA Views – DB Layer Stored Procedures

7.4 SP05

CDS Views ABAP Managed DB Procedures


SAP HANA Views – DB Layer Stored Procedures

DAY 2 - ABAP ON HANA 2


SAPYARD.COM
3

ABAP Programming on SAP HANA

APPLCATION LAYER – SAP GUI

PRIMARY DB (Oracle) ----→ SECONDARY DB

SAP HANA as Secondary Database

T-Code → DBACOCKPIT

Some Restrictions for using Open SQL to access secondary DB –

1) Only tables and fields that are defined in the local ABAP Dictionary

2) No HANA specific objects i.e SAP HANA Views and Procedures

3) Only tables in the Schema assigned to the DB User in the Connection

1) Keep result sets small -→ Rows

2) Minimize amount of transferred data → Columns -->> More Important

3) Minimize number of database access -→ More important

4) Minimize search overhead → Less Important

5) Keep unnecessary load away from DB → Less important

DAY 2 - ABAP ON HANA 3


SAPYARD.COM

You might also like