Provisioning is a process of creating, preparing, and enabling a network to provide data to its user. Data needs to be loaded to SAP HANA before data reaches to the user via a front-end tool.
ETL: Extract, Transform, Load
Extract: extracted from different source systems
Transform: Series of rules or functions is defined for data extracted from the source system, for loading data into the target system.
Load: Loads the data in the target system.
SAP HANA built in provisioning tools:
1) Flat File
2) Smart data streaming
3) Enterprise Informaiton Management (EIM)
4) Smart Data access( SDA)
5) Remote data
External Tools:
1) SLT
2) BO DS
3) SAP DXC
4) Sybase Replication Services
SLT
|
SLT ("SAP Landscape Transformation Replication Server") running on the SAP Net Weaver Platform. SLT is an ideal solution for Real-Time and Schedule time replication for SAP and non-SAP source system.
|
SAP DATA Services
|
SAP DATA Services is a platform for designing of ETL processes with a graphical user interface.
|
DXC
|
DXC stand for Direct Extractor Connect is a batch driven ETL tool.
|
Flat File Upload
|
This option used to Upload data (.csv, .xls, .xlsx) to SAP HANA.
|
SAP/non-SAP system:
SAP SLT Replication Server transforms all metadata table definitions from the ABAP source system to SAP HANA
SAP Source, SLT connection has the following features:
-When a table is replicated, SAP SLT Replication server create logging tables in the source system.
-Read Engine is created in the SAP Source System
-Connection between SAP SLT and SAP Source is established as RFC connection
-Connection between SAP SLT and non-SAP HANA is established as a DB connection
Data Provisioning through SLT require RFC/DB connection to SAP/NON-SAP Source system and a
Step 1) Login to SAP SLT server, and Call transaction "LTR" from SAP SLT replication server.
A Web-dynpro pop-up screen will appear for login to SAP SLT server.
- Enter Client / User id / password
- Click on logon tab
Step 2) In this step,
- Enter Configuration name and description.
- Select SAP System as the source system.
- Enter RFC connection for SAP System.
- Enter Username / Password / Host Name and Instance number.
- Enter Job options detail –
- No. of data Transfer Jobs.
- No. Of calculation jobs.
- Select Replication option as Real Time.
- Once all the settings are maintained click on 'OK' to create a new schema in SLT.
Import SAP Source Data to SAP HANA through SLT:
This Schema contains following objects-
- 1 Schema - SLTECC.
- 1 User – SLTECC.
- 1 Privileges
- 8 Tables –
- DD02L (SAP Tables Name )
- DD02T (SAP Table Texts)
- RS_LOG_FILES
- RS_MESSAGE
- RS_ORDER
- RS_ORDER_TEXT
- RS_SCHEMA_MAP
- RS_STATUS.
- 4 Role -
- SLTECC_DATA_PROV
- SLTECC_DATA_POWER_USER
- SLTECC_DATA_USER_ADMIN
- SLTECC_DATA_SELECT
- 2 Procedures
- RS_GRANT_ACCESS
- RS_REVOKE_ACCESS
Step 1) Load tables from SAP ECC to SAP HANA database:
1) Data provisioning from Quick View
2) Select SAP HANA System
3) Click on Finish Button
Step 2) SLT based Table Data Provisioning
Load (Full Load)
|
This is a one-time event, which starts an initial load of data from source system.
|
Replicate
(Full Load + Delta Load)
|
It start initial load (if not done earlier), and also consider delta change. Database trigger and related logging table will be created for each table.
|
Stop Replication
|
It stops the current replication process for a table. It removes database trigger and logging table completely.
|
Suspend
|
It pause a running replication process of a table. The database trigger will not be deleted from the source system, and recording of changes will continue. Related Information is stored in the related logging table in the source system.
|
Resume
|
Resume restarts the replication for a suspended table. After resume, the suspended replication process will resume.
|
Step-by-step is as below: "Load option" for initial load of the table data from source to SAP HANA Table
-SLT and target system details are selected
-click on load button, select table to load/replicate in SAP HANA
-Table is added to Data Load management Section with Action "load and Status "scheduled"
- Source and Target system details are selected according to SAP SLT configuration.
- Click on Load Button and select the table (LFBK) which we need to load/replicate in SAP Hana.
- Table (LFBK) will be added to Data Load Management Section with Action "Load" and Status "Scheduled."
Step 3) Check Data in the table (LFBK) by data Preview from Schema "SLTECC":
- Login in SAP HANA DB throgh SAP HANA Studio and select SAP HANA Studio and select SAP HANA System HDB (HANAUSER)
- Select Table (LFBK) under table node
- Right click on Table (LFBK) and click on Open Data Preview option
- Loaded Data through SLT process will be displayed in Data Preview Screen
STEP 1) Load tables from SAP ECC to SAP HANA DB: i) data provisioning from quick view ii) Select SAP HANA System
STEP 2) SLT Based Table Data Provisioning/ 5 options for Data Provisioning :
- Load(FULL LOAD): starts an initial load of data from source system.
- Replicate( FULL LOAD + DELTA LOAD):
- starts initial load
- considers delta change
- Database trigger and related logging table created for each table
- Stop Replication: (Stop current replication process)
- Removes db trigger
- Removes logging table completely
- Suspend: (Pause a running replication process of a table)
- DB trigger not deleted from the source system
- recording of changes will continue
- Related information is stored in the related logging table in the source system
- Resume: Restarts the replication for a suspended table
- process will resume after suspended replication
Step by step as below:
- Source and Target system details selected according to SAP SLT configuration
- Click on Load Button and select the table (LFBK) which we need to load/replicate in SAP HANA
- Added to Data Load Management Section with action "Load" and Status "Scheduled"
Src to Table:
1) Src and Target System details
2) Select table which we need to load/replicate in SAP HANA
3)Table will be added to Data Load Mgmt Section with Action "LOAD" and status "Scheduled"
4) Loaded Data through SLT process will be displayed
===========================================================
SLT:
A) Login-SLT Server(LTR) --NetWeaver
i) enter client number/ UN/ PW
B) i)configuration name/ description
ii) SAP system as SRC system,
iii) RFC connection for SAP SYSTEM,
iv) UN, PW, Host Name, Instance Number,
v) Job options (no. of data transfers, no. of calculation jobs),
vi)Replication option (RT/Scheduled(Interval, Time), vii) Connection to HANA System
After configuration SAP SLT server
A) DB connection for SAP HANA DB automatically created
B) Schema contains
- i) 1 schema-SLTECC,
- ii) 1 user SLT ECC
- iii) 1 privileges
- 8 tables (SAP tbl names, SAP tbl texts, RS_LOG_FILES, RS_MESSAGE, RS_ORDER, RS_Order_Text, RS_SCHEMA_MAP, RS_STATUS)
- iv) 4 Roles: SLTECC_DATA_PROV SLTECC_DATA_POWER_USER, SLTECC_DATA_USER_ADMIN, SLTECC_DATA_SELECT
- v) 2 Procedures: -RS_GRANT_ACCESS, -RS_REVOKE_ACCESS
STEP 2) SLT Based Table Data Provisioning/ 5 options for Data Provisioning :
- Load(FULL LOAD): starts an initial load of data from source system.
- Replicate( FULL LOAD + DELTA LOAD):
- starts initial load
- considers delta change
- Database trigger and related logging table created for each table
- Stop Replication: (Stop current replication process)
- Removes db trigger
- Removes logging table completely
- Suspend: (Pause a running replication process of a table)
- DB trigger not deleted from the source system
- recording of changes will continue
- Related information is stored in the related logging table in the source system
- Resume: Restarts the replication for a suspended table
- process will resume after suspended replication
Non-SAP source, the SLT connection has following features:
- -When a table is replicated, SAP SLT replication server create logging tables in the source system
- Read engine is created in the SAP SLT Replication
- The connection between SAP SLT and SAP Source/SAP HANA is establsihed as a DB connection
- The connection between SAP SLT and SAP src/SAP HANA is established as a DB connection
SLT can only do simplest transformations, for complex transformations we need other ETL tools such as SAP Data Services.
Step 3: Check data in the table by previewing data from Schema
A) Login to SAP HANA DB through Studio and select HDB(HANA USER)
B) Select table under table node
C)Right click on table and click on data preview
D)Load data through SLT process
*used to store Vendor Master (Bank Details
\
\
SAP DS (SAP Data services)
Qs:10 Which data provisioning method can you use to load data from SAP business content DataSources into SAP HANA? (Choose two)
A. SAP Landscape Transformation (SLT)
B. SAP Landscape Directory (SLD)
C. SAP Direct Extractor Connection (DXC)
D. SAP BusinessObjects Data Services
s:11 Your customer requires real-time replication. Where do you select the tables to be replicated to SAP HANA?
A. in transaction LTR in SAP Landscape Transformation (SLT)
B. in the Import dialog of the Quick Launch of SAP HANA studio
C. in transaction SAP ERP Tables and Indexes Monitor (DB02)
D. in the Data Provisioning dialog of SAP HANA studio
0. Data provisioning can be both initial load and replication : True
- Load(FULL LOAD): starts an initial load of data from source system.
- Replicate( FULL LOAD + DELTA LOAD):
- starts initial load
- considers delta change
- Database trigger and related logging table created for each table
- Stop Replication: (Stop current replication process)
- Removes db trigger
- Removes logging table completely
- Suspend: (Pause a running replication process of a table)
- DB trigger not deleted from the source system
- recording of changes will continue
- Related information is stored in the related logging table in the source system
- Resume: Restarts the replication for a suspended table
- process will resume after suspended replication
What happens(three things) happen when you replicate?
-Start initial Load, considers delta change, database trigger and related logging table created for each table
-Remove db trigger
-Removes logging table completely
What happens (three things) happen when you suspend?
-DB trigger not deleted from the source system
-Recording of changes will continue
-related information is sstored in the related logging table in the source system
What happens three things happen when you resume?
-Process will resume after suspended replicationWhat happens (one thing) happen when you load?
-starts an initial load of data from source system.
LFBK http://www.se80.co.uk/saptables/l/lfbk/lfbk.htm
No comments:
Post a Comment