1. ETL based replication using BODS
2. Trigger based replication using SLT
3. Extractor based data acquisition using DXC
2) What is SLT?
SLT stands for SAP Landscape Transformation which is a trigger based replication. SLT replication server is the replication technology to pass data from source system to the target system. The source can be either SAP or non-SAP. Target system is SAP HANA system which contains HANA database.
3) Is it possible to load and replicate data from one source system to multiple target database schemas of HANA system?
Yes. It is possible for up to 4.
4) Is it possible to specify the type of data load and replication?
Yes either in real time, or scheduled by time or by interval.
5) What is Configuration in SLT?
The information to create the connection between the source system, SLT system, and the SAP HANA system is specified within the SLT system as a Configuration. You can define a new configuration in Configuration & Monitoring Dashboard (transaction LTR).
6) Is there any pre-requisite before creating the configuration and replication?
For the SAP source systems DMIS add-on is installed in
SLT replication server. User for RFC connection has the role IUUC_REPL_REMOTE
assigned but not DDIC.
For non-SAP source systems DMIS add-on is not required
and grant a database user sufficient authorization for data replication.
7) What is Configuration and Monitoring Dashboard?
It is an application that runs on SLT replication server to specify configuration information (such as source system, target system, and relevant connections) so that data can be replicated. It can also use it to monitor the replication status (transaction LTR).
Status Yellow: It may occur due to triggers which are
not yet created successfully.
Status Red: It may occur if master job is aborted (manually
in transaction SM37).
8) What is advanced replication settings?
A transaction that runs on SLT replication server to specify advanced replication settings like
Modifying target table structures,
Specifying performance optimization settings
Define transformation rules
9) What is Latency?
It is the length of time to replicate data (a table entry) from the source system to the target system.
10) What is logging table?
A table in the source system that records any changes to a table that is being replicated. This ensures that SLT replication server can replicate these changes to the target system.
11) What are Transformation rules?
A rule specified in the Advanced Replication settings transaction for source tables such that data is transformed during the replication process. Example you can specify rule to
Convert fields
Fill empty fields
Skip records
12) What happens when you set-up a new configuration?
The database connection is automatically created along
with GUID and Mass transfer id (MT_ID).
A schema GUID ensures that configurations with the same
schema name can be created.
The Mass transfer ID is used in the naming of SLT jobs
and the system can uniquely identify a schema.
13) What factors influence the change/increase the number of jobs?
Number of configurations managed by the SLT replication
server
Number of tables to be loaded/replicated for each configuration
Expected speed of initial load
Expected replication latency time. As a rule of
thumb, one BDG job should be used for each 10 tables in replication to
achieve acceptable latency times.
14) When to change the number of Data Transfer jobs?
If the speed of the initial load/replication latency time
is not satisfactory
If SLT replication server has more resources than initially
available, we can increase the number of data transfer and/or initial load
jobs
After the completion of the initial load, we may want
to reduce the number of initial load jobs
15) What are the jobs involved in replication process?
1. Master Job (IUUC_MONITOR_<MT_ID>)
2. Master Controlling Job (IUUC_REPLIC_CNTR_<MT_ID>)
3. Data Load Job (DTL_MT_DATA_LOAD_<MT_ID>_<2digits>)
4. Migration Object Definition Job (IUUC_DEF_MIG_OBJ_<2digits>)
5. Access Plan Calculation Job (ACC_PLAN_CALC_<MT_ID>_<2digits>)
