Create Data Store in SAP HANA

Scenarios

1) Create Data store for MYSQL DB

Logon to DS Designer with local repository credentials

In Local object worasy go to Data store (Tab)

Right click and select new

Provide DST Name  DSI                        Data store

DST Type is database.

DB Type MSSQL 2005

DB Server name

DB Name

User id

Password

• Apply
• OK
• So will get stored procedures, physical tables and template table
• Double click on the physical table will get list of tables which are related to our source database

 

Note: - We need to import only required tables rather then all tables to increase the performance

• We can convert template tables to physical tables.

Interested in mastering SAP HANA Training? Enroll now for FREE demo on SAP HANA Training.

 

2) Create Data store for SAP R3 ERP system

SAP ERP is recognized in DS as SAP Application DST.

From SAP Application DS we call use metadata which is in the form of

1. Extractors in 4.0
2. Tables
3. Function module
4. Hierarchies
5. /docs

The above metadata can be extracted & loaded unto SAP

BW and any DB

 

 

Log on DS designer with local reposting credentials

In Local object Library go to data store (tab)

Right click add select row

Provide Data store name

•  Data store type as SAP applications
•  Application Server
• Username
• Password
• System no
• Working directory on SAP Server               D:/ usr / sap / trans
• Application path to the shared directory   D:/ Usr / sap / trans
• Data Transfer Method                                 Shared Directory
• Security profile                                               SAP – ALL
• NO of connections                                         3
• ABAP Execution option                               Generate & execute / execute Preloaded

NOTE:- Normally when you read the data from SAP R3 system it is recommended to use ABAP dataflow Over normal dataflow

If we want to store ABAP programmers in SAP systems we can select execute preloaded

Cerebrate & execute option the system generated ABAP code resides on DS and it will be reused for executions

Whereas if you select execute preloaded then the ABAP code will generated and reminds at SAP APPL servers

DS uses 4 different data transfer methods

1. a) Direct directory Using DS Using RFC can
2. b) Shared directory Using SAP Transports
3. c) FTP                         Using Remote Server
4. d) Custom TransferUsing Auto Execute Program

 

Note

When you don’t provide surety profile DS will take SAP-ALL

If we want to restrict we need to create seared profile and provide here

Ok

After creating DS we can create metadata

1. a) Extractors [Set of data source provided by B1 content / custom]
2. b) Functions [Set of functional mapping to ERP system is achieved by ABAP code this is reformed as function module which can be extracted & loaded dumped into any forget SAP BW/Data based]
3. c) Hierarchies [During preparation of source system you map functional data to the SAP ERP system with hierarchy

EX: - Cost centre, GL amounts, eh, custom data store

1. d) IDocs are preferred to load the data into target system when we used to transfer the data file it is Sinclair to on-directed staging area
2. e) Tables [SAP R3 DB tables]

For an Indepth knowledge on SAP HANA, click on below

• Performance Tuning in SAP HANA
• Security in SAP HANA
• Advanced Analysis with SAP HANA Tables and Views
• Analytical Privileges in SAP HANA
• SAP HANA Views