1. By www.Garudatrainings.com Ph No:+1-508-841-6144
www.Garudatrainings.com
2. What are the different types of replication techniques? ETL
based replication using BODS Trigger based replication using SLT
Extractor based data acquisition using DXC
www.Garudatrainings.com
3. 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.
www.Garudatrainings.com
4. 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. www.Garudatrainings.com
5. Is it possible to specify the type of data load and
replication? Yes either in real time, or scheduled by time or by
interval. www.Garudatrainings.com
6. 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). www.Garudatrainings.com
7. 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.
www.Garudatrainings.com
8. 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).
www.Garudatrainings.com
9. 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
www.Garudatrainings.com
10. What is Latency? It is the length of time to replicate data
(a table entry) from the source system to the target system.
www.Garudatrainings.com
11. 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. www.Garudatrainings.com
12. 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 www.Garudatrainings.com
13. 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. www.Garudatrainings.com
14. 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.
www.Garudatrainings.com
15. 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
www.Garudatrainings.com
16. What are the jobs involved in replication process? 1.
Master Job (IUUC_MONITOR_) 2. Master Controlling Job
(IUUC_REPLIC_CNTR_) 3. Data Load Job (DTL_MT_DATA_LOAD__)
4.Migration Object Definition Job (IUUC_DEF_MIG_OBJ_) 5.Access Plan
Calculation Job (ACC_PLAN_CALC__) www.Garudatrainings.com
17. What is the relation between the number of data transfer
jobs in the configuration settings and the available BGD work
processes? Each job occupies 1 BGD work processes in SLT
replication server. For each configuration, the parameter Data
Transfer Jobs restricts the maximum number of data load job for
each mass transfer ID (MT_ID). A mass transfer ID requires at least
4 background jobs to be available: One master job One master
controller job At least one data load job One additional job either
for migration/access plan calculation/to change configuration
settings in Configuration and Monitoring Dashboard
www.Garudatrainings.com
18. When to go for table partitioning? If the table size in
HANA database exceeds 2 billion records, split the table by using
portioning features by using Advanced replication settings
(transaction IUUC_REPL_CONT, tab page IUUC_REPL_TABSTG).
www.Garudatrainings.com
19. Are there any special considerations if the source system
is non-SAP system? The concept of trigger-based replication is
actually meant for SAP source systems. The main differences are:
There will be a database connection between non-SAP source and SLT
system instead of RFC. Source must have primary key Tables DD02L,
DD02T which contains metadata are just initially loaded but not
replicated. The read modules reside on SLT system. Tables with
database specific formats may need transformation rules before they
are replicated. Only SAP supported databases (with respective DBSL
for SAP Net Weaver 7.02) are supported as non-SAP source systems.
www.Garudatrainings.com
20. What are the potential issues in the creation of
configuration? Missing add-on DMIS_2010 in source system Missing
the proper role of SAP_IUUC_REPL_REMOTE for RFC user (
SAP_IUUC_USER for SLT system ) Logon credentials are not correct
www.Garudatrainings.com
21. How can you ensure that data is consistent in source system
and HANA system? Since any changes in the source system is tracked
in dedicated logging tables, the replication status for each
changed data record is transparent. A entry of logging table is
deleted after a successful commit statement from HANA database and
this procedure ensures the data consistency between source system
and HANA system. www.Garudatrainings.com
22. Does SLT for SAP HANA support data compression like SAP
HANA database? Yes, this is automatically covered by the RFC
connection used for data replication from the SAP source system.
www.Garudatrainings.com
23. Contact Us: For more Details Please Log On To
www.Garudatrainings.com You Can also Find Us On:
www.Garudatrainings.com