SAP LT Replication Server

Purpose

This purpose for this page is help with resolving SLT related queries.

How To Create A Configuration

Link on how to create a configuration.

DMIS Version

Which version of DMIS is being used on the Source & SLT system?
Here is a list of correction that has been released by SLT Development team.
It is recommended to install all correction on the Source & SLT system prior to raising incidents.

How To Improve LOAD

Improve Initial Load by Row ID

How to Load INDX tables into HANA using SLT (STXL & PCL2)

How to replicate VIEWS with SAP LT Replication Server

Performance Optimization Guide (2011 SP9)

How to load data from archives into HANA DB

How to replicate data from an INDX-like table to a target system using SLT (DMIS 2011 SP11)

How to reduce latency of table

Real Time Data Replication to BW Using SLT From SAP Source System (ODP Scenario)

Realtime Replication with SLT into Data Store Objects in SAP BW 7.4

Source tables have little activity or changes on them but their are frequent calls to the source system:

If SLT is using real-time replication then it is continuously checking the logging tables for new records. There are 2 ways the customer can reduce number of calls to the source:

Change from real-time replication to Interval. This setting can be found in the LTR settings, where customer can specify in minutes, hours, day, the frequency to check the logging tables. Perhaps once per minute is enough. Only issue with this is latency will increase, having up to a minute of latency in the time the record appears in Hana target.

Change the logging table check behavior. In LTRC-> Utilities-> Specify Option for Logging Tables, there are 2 options. The alternate option of “Only Process Logging Tables with Records” will avoid querying the logging tables when they are empty. This could be a good option as the customer’s configuration have very little activity as there is no need to continuously poll the empty logging tables