Professional Documents
Culture Documents
Table of Content
1 Business Context, Document Purpose and Scope 3
1.1 Document Purpose & Scope 3
2 General remarks 4
2.1 High level architecture 4
2.2 Pre-requisites 5
3 Configuration 6
4 Configuration checks 7
5 Replication scenarios 8
5.1 Replication scenario ERP à SLT à BW 8
5.2 Replication scenario ERP à SLT à CAR 10
5.3 Replication scenario CRM à SLT à CAR 11
5.4 Schema Mappings 12
6 CAR table partitioning 13
6.1 Partitioning: 14
6.2 Relocating Partitions 15
6.3 Archiving 16
6.4 Important notes and transactions 16
7 Tips & Tricks 17
7.1 List of replicated tables 17
7.2 Maintain DB connection in SLT 21
7.3 Reload data, but don't re-create table in HANA 21
7.4 Transformation rules during replication 22
1 Business Context, Document Purpose and Scope
1.1 Document Purpose & Scope
This document contains the required configuration to enable SLT replication from a source system to the HANA
target database.
This configuration is required in the context of replicating ECC and CRM tables to CAR HANA Database using
real-time replication mode on SLT.
2 General remarks
2.1 High level architecture
SLT is able to replicate data between multiple sources to multiple targets – SAP and non-SAP. The following
shows the typical connection between SLT and the source and target systems:
The following roles and authorizations have to be assigned to the different users to ensure a proper replication
scenario:
2.2 Pre-requisites
1. Create an RFC destination from SLT to the source SLT of the replication
2. Collect and define the following details about the target HANA database for the replication
a. Configuration name (corresponds to the name of the schema generate in HANA)
b. Number of Data Transfer jobs (based on number of tables to be replicated)
c. HANA Database Hostname (master node in case of scale-out)
d. Instance/system number
e. Password of HANA System user
3. Activate the following services form the transaction SICF
a. /sap/public/myssocntl
b. /sap/bc/webdynpro/sap/iuuc_replication_config
c. /sap/bc/webdynpro/sap/iuuc_helpcenter_document
d. /sap/bc/webdynpro/sap/iuuc_repl_mon_powl
e. /sap/bc/webdynpro/sap/iuuc_helpcenter
f. /sap/public/mysso/cntl
g. /sap/bc/webdynpro/sap/iuuc_repl_mon_schema_oif
h. /sap/public/bc/ur
i. /sap/public/bc/icons
j. /sap/public/bc/icons_rtl
k. /sap/public/bc/webicons
l. /sap/public/bc/pictograms
m. /sap/public/bc/webdynpro
3 Configuration
1. Go to transaction LTRC
2. Click on the button Create New Configuration
3. Click on the menu bar on Action à Create New Configuration
4. Fill all the required inputs as shown below
The selection of “Allow Multiple Usage” is quite important. It allows the usage of the same RFC
connection configuration for multiple replication into different targets, i.e. ERP data into BW and ERP
at the same time.
“Read from Single Client” would only take data from selected source client. As client info is replicated
anyhow in addition with all replicated data, the target application is taking care of using only client
specific data in the target scenario.
The rule of thumb for the number of transfer jobs is roughly 1 job per 10 tables to be replicated.
5. Save the configuration.
4 Configuration checks
The configuration can tested using the following checks.
1. From transaction LTR check if
2. From transaction LTRC access to the configuration just created (providing he correct Mass Transfer
ID) and check that initial technical tables are in replication mode.
3. Login to the target HANA Database and check the schema just created (same name as the
Configuration Name). In particular check if the tables DD02L, DD02T and DD08L have been created
and contains entries.
To speed up initial data load of tables, the number of calculation jobs can be increased until the initial load has
been done.
5 Replication scenarios
5.1 Replication scenario ERP à SLT à BW
As an example a screenshot has been attached to show the created configuration for ERP replication into BW
in the pre-production environment.
The following tables have been requested from Reporting stream to be replicated into BW with real time
replication setting: