Skip to Content

Hello All,

In this blog, would like to give you the steps for the installation and configuration of SAP Landscape Transformation Replication Server (SAP LT Replication Server) in order to facilitate the trigger-based replication of data to SAP HANA. writing this blog based on experience of setting up the real time replication from the S4HANA Fashion Management system to SAP CAR (Customer Activity Repository) system

This blog is intended for system administrators performing initial install and configuration of SAP SLT server for SAP HANA and both source and target database are SAP HANA

2580573 – Can S/4 HANA be the source or target system of an SAP Landscape Transformation Replication Server? – SAP Landscape Transformation Replication Server

Introduction and Planning

  • SLT is the SAP first ETL tool that allows you to load and replicate data in real-time or schedule data from the source system and Non-Source System into SAP HANA Database.
  • SAP SLT server uses a trigger-based replication approach to pass data from source system to target system.
  • Components are used in the technical system landscape

−ABAP Source System

−Non-ABAP Source System

−SAP Landscape Transformation Replication Server

−SAP HANA System

  • SLT server can be installed on the separate system or on SAP ABAP System
  • Replication of non-ABAP source systems require SAP LT Replication Server to be installed on a separate system.
  • The SAP LT Replication Server system must be a Unicode system.
  • Installation Option for ABAP Source Systems
      Option A - SAP LT Replication Server is a Separate System

      Option B – SAP LT Replication Server is Installed in the Source System
  • Installation Options for Non-ABAP System

Installation Option for ABAP Source Systems

Option A – SAP LT Replication Server is a Separate System
  • The connection between SAP SLT and SAP Source is established as RFC connection.
  • The connection between SAP SLT and SAP HANA is established as a DB connection
  • When a table is replicated, SAP SLT Replication server create logging tables in the source system.
  • Read module is created in the SAP Source System

Option B – SAP LT Replication Server is Installed in the Source System
  • The SAP LT Replication Server installed in the ABAP source system. If the source system has the required SAP kernel and SAP NetWeaver versions to support the SAP LT Replication Server, the system architecture can be simplified to a 2-tier system

Installation Options for Non-ABAP System

  • The SAP LT Replication Server installed in a separate system. Compared to a setup with an ABAP system as a source system, only the read modules are created in the SAP LT Replication Server (for ABAP source systems the read modules are located in the source system only). The connection from the SAP LT Replication Server to the non-ABAP source system is established by means of a database connection
  • Ensure that the database of your non-ABAP source system fulfills all prerequisites for usage with the SAP LT Replication Server. Since a database connection from the SAP LT Replication Server to a non-ABAP system is required, an OS/DB restriction of SAP NetWeaver 7.02 or higher applies to the system running the SAP LT Replication Server

Comparison of Different Installation Options

the advantages and disadvantages of the different installation options are

Replication landscape in my case:

Steps:

  1. Install the SAP LT Replication Server

  2. Configure the source data system for RFC access from SAP LT Replication Server

  3. Start SLT configuration from LTR transaction

  4. Start replication from the source system to the target SAP HANA system

  5. Core post-installation steps for implementing SAP Customer Activity Repository

 

  1. SAP LT Replication Server System Installation

ABAP Source system:

SAP LT Replication Server is shipped in an add-on call DMIS_*. You must install the add-on in your ABAP source system, and in the SAP LT Replication Server system

source system is an SAP S/4HANA

Note: if the source system is an SAP S/4HANA On-Premise system (release 1610 or higher), then the add-on DMIS is not required.

in our case, we have used S4Hana 1709 as a source system, hence we have skipped the DMIS add on installation in source system

  1. Configure the source data system for RFC access from SAP LT Replication Server

Create an RFC ABAP connection from SLT system to Source data system

  1. Start SLT configuration from LTR transaction

Lunch the LTR tcode from the SLT system and proceed with the guided configuration, this will create the database connection to target hana database.

The configuration name we used here will be the “replication schema” in the hana database. which means all the replication tables from source system, can be found under this schema in the target database.

You can determine the logical port number by logging on to the tenant database, and running following SQL statement:

SELECT SUBSTRING(SQL_PORT,4,2) FROM "SYS"."M_SERVICES" WHERE SERVICE_NAME = 'indexserver'

Initial Load Mode:

You can define an Initial Load Mode if you want to use a different default reading type.

  • Initial Load Mode “Resource Optimized” is the default mode and uses reading type 3for all tables.
  • Initial Load Mode “Performance Optimized”can be used if reading type 4/5should be used for all tables. SLT will use reading type 4 for cluster tables and reading type 5 for the other tables.

Number of Data Transfer Jobs: This value specifies the number of data transfer jobs which will run in this SAP LT Replication Server configuration to replicate the tables of the RFC connection to the SAP HANA system.

No.of Initial load Job: A job that is used for the initial load process in the SAP LT Replication Server.

Number of Calculation Jobs: This value specifies the number of access plan calculation jobs which will be allocated by this configuration.

 

Once the configuration is created, we need to start the replication for the required tables. this can be done via transaction LTRC from SLT system.

in my case target system is SAP CAR system, hence we have to setup the replication for CARAB 2.0 – SLT Tables

You have downloaded the spreadsheet with the tables for your version of SAP Customer Activity Repository applications bundle:

  1. Navigate to SAP Help Portal at https://help.sap.com/viewer/p/CARAB and select the desired version at the top right.
  2. Download the CARAB 2.0 – SLT Tables archive from under Installation and Upgrade and extract the spreadsheet

Create and replicate the required tables using the SAP Landscape Transformation Replication Server. For reference, use a spreadsheet that lists the tables by source master data system (database schema).

4.Start replication from the source system to the target SAP HANA system

First you have to create table/DB view (list can be exported from xls directly) , then start load and start replication with same set of tables.

Please note, initial load (start load) would take more time to load data initially.

once replication is active we need to perform the post steps in case of SAP CAR as target system.

Transformation rule If source and target client numbers are different

If source and target system client are different,we need to create the rule assignment in LTRS transaction tcode

2330878 – How to create a template in SLT

  1. Post-installation steps for implementing SAP Customer Activity Repository as target system

 

Verify Correct Schema Mapping

The SAP HANA content of SAP Customer Activity Repository applications bundle is delivered with several authoring schemas (for different scenarios and different source master data systems). Verify that the authoring schemas are mapped to the correct physical schema of your customer system. If necessary, create new mappings.

 

 

Activate SAP HANA Content

In this procedure, you activate the SAP HANA content for your scenario(s) using a dedicated report.

The report activates the SAP HANA Transport for ABAP (HTA) objects that are required for your selected scenario(s). One HTA object will be activated for each SAP HANA content package.

Procedure

  • In CAR system, start transaction SE38.
  • Enter /CAR/ACTIVATE_HTAas the program and choose Execute.
  • Select all applicable source master data systems, business scenarios, and scenario options for which you wish to activate SAP HANA content.

 

 

Activate SAP HANA Script Server

In this procedure, you activate the script server for the SAP HANA database. This step is required, regardless of the scenario you are planning to implement.

ALTER DATABASE <Tenant database name>  ADD ‘scriptserver’

SLT Configuration and monitoring

LTR – SAP LT Replication Server transaction can be used for Configuration & Monitoring Dashboard

LTRC – SAP LT Replication Server Cockpit for Monitoring and work with Configurations

LTRS – SAP Landscape Transformation replication server

SLT Replication Logging and Replay To Retrieve Lost Data

  • SLT Logging:

Logging option available on SLT system and it used to log table specific replication or entire configuration which includes all tables

  • SLT Replay:

SLT Replay is the option to retrieve data with selections from logging data. Here selections depends on days which we selected for logging

  • Database Trigger:

The source system tracks database changes by using database triggers. It records information about changes in the logging tables.

Reference SAP notes:

1972009 – How to create an SLT Configuration Step-by-Step
2593656 – How to change the user for an SLT job
2645613 – Very high CPU utilization after patching SLT server to DMIS 14
2596411 – SLT / NZDT (DMIS2011 SP11-SP15; S/4HANA 1610 & 1709) – Note Analyzer
1908498 – How to set SLT jobs in SLT configuration
2329159 – Recommended number of data transfer jobs – SLT
2617586 – How to transfer LTRS settings between SLT systems

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply