Skip to Content
Author's profile photo Mohammad Shafiullah

SAP LT REPLICATION-PART 1

SAP LANDSCAPE TRANSFORMATION REPLICATION:

/wp-content/uploads/2014/05/slt_463903.png

  • SAP LT is trigger based ,Real time replication method.
  • SAP LT replication server for SAP HANA leverage on proven SLO(System Landscape Optiomization) technology.SAP LT replication server is the ideal solution for all HANA customer who need real-time or schedule based replication sourcing from SAP and NON-SAP sources.
  • SLT replication server can be installed as stand alone server or can run on any SAP system with SAP NetWeaver 7.02 ABAP Stack(Kernel 7.02EXT) .
  • Add-on DMIS_2010_1_700 with SP5-7, NW 7.02; SAP Kernel 7.20EXT need to be installed for SLT replication to apply SPS04 for SAP HANA 1.0.
  • SLT replication system is connected with Source SAP ECC system by RFC(Remote Function call) connection and with target HANA system by DB Connection.In case of NON-SAP source system SLT connect with DB connection.
  • SAP source system contains Application tables,logging tables,triggers and read module.SLT server contains Control Module(Structure mapping & Transformation) and Writer module.In case of Non-SAP source system, Read Module resides in SLT System.
  • When replication start,logging table and trigger created in source system and data gets replicated to target system via SLT replication server and any changes in source system gets automatically replicated to target system.

SLT CONFIGURATION:


Configuration steps for SAP LT Replication Server

  • Define a schema for each source system
  • Define connection to source system
  • Define DB connection into SAP HANA
  • Define replication frequency (real-time; frequency for scheduled replication)
  • Define maximum number of background jobs for data replication

STEP 1: Open Configuration and Monitoring Dashboard by using transaction code “LTR”. Click on New button to start SLT configuration.

SLT1.png

STEP 2: Provide name of SLT configuration. Please note that a schema will be created with the same name in HANA after the completion of configuration settings.

SLT2.png

STEP 3: Specify source system details. If the source system in SAP (ECC) then select RFC Connection. Select DB Connection for Non-SAP Source system.

SLT3.png

STEP 4: Specify target system details. The target HANA system is connected through DB Connection. Provide HANA system connection parameters. Administrator user privilege required.

SLT4.png

When the popup to create a new configuration is closed by pressing the OK button, the following actions are performed automatically:

  • Configuration settings are saved on the LT Replication Server
  • New user and schema are created on the HANA system with the defined target schema name (not performed if an existing schema is reused).
  • Replication control tables (RS_* tables) are created in target schema.

          RS_LOG_FILES, RS_MESSAGES, RS_ORDER, RS_ORDER_EXT, RS_SCHEMA_MAP, RS_STATUS

  • User roles for the target schema are created:
    • <target_schema>_DATA_PROV -> Role to manage data provisioning
    • <target_schema>_POWER_USER -> Contains all SQL privileges of the target schema
    • <target_schema>_USER_ADMIN -> Role to execute authority
  • A procedure to grant (RS_GRANT_ACCESS) or revoke (RS_REVOKE_ACCESS) are created in the target schema
  • Replication of tables DD02L (stores the table list), DD02T (stores the table short descriptions) and DD08L (R/3 DD: relationship definitions) is started automatically. Once those tables are replicated, the HANA studio knows which tables are available in the source system.
  • SYS_REPL and table RS_REPLICATION_COMPONENTS are created (If they don’t exist already based on a previous configuration)
  • Replication is registered in table RS_REPLICATION_COMPONENTS

SLT4a.png

SAP LT REPLICATION OPTIONS:

SLT8a.png

Use LTRC transaction code to open LT replication Server Cockpit.We can use SLT options from SLT replication server as well as from  HANA data provisioning.Select table and replication option from LT Replication server to start/replicate/stop/suspend/resume replication.

SLT5.png

HANA data provisioning option can be seen in Quick launch view.

SLT7.png

Select table to start replication.

SLT8.png



Assigned Tags

      13 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      A nice quick reference !

      Author's profile photo Former Member
      Former Member

      Very Goof Reference!! Thank you

      Author's profile photo Former Member
      Former Member

      Can't wait for Part 2!  Great Reference!!

      Author's profile photo Ashutosh Chaturvedi
      Ashutosh Chaturvedi

      Mohammad Shafiullah,

      Nice blog.

      With Regards

      Ashutosh Chaturvedi

      Author's profile photo Former Member
      Former Member

      thank you

      Author's profile photo Narendra Reddy
      Narendra Reddy

      Thank you

      Author's profile photo Mridula Sharma
      Mridula Sharma

      @ Mohammad Shafiullah : Very nice article, short and precise. And with Screenhots, its easier to understand 🙂

      Author's profile photo Former Member
      Former Member

      Thank you

      Author's profile photo Former Member
      Former Member

      Good reference!!

      Author's profile photo Asad S Zafer
      Asad S Zafer

      Nice Document!

       

      Author's profile photo sridhar kolan
      sridhar kolan

      @ Former Member, thank you for the article. My question is in few parts and please provide response from your experience

      1. Assume that we are migrating from SAP ECC to S/4 HANA and we have multiple work streams MM/PP/SD/FI in use on ECC.

      1A. Do we have to identify and list each individual table in a SLT config, in such case we will have about 150 tables for each work stream to include master and transactional data. Some with huge volume in Millions and some with thousands.

      1B. If there are about 150 tables, do we have to add and complete initial load of the tables in a sequence to support the dependencies

      1C. For practical purposes, should we create separate configuration for each work streams or even break down within work streams, like with in MM (Material management, purchasing, inventory etc)

      1D. Will the tables names in SAP ECC and SAP S/4HANA be same, if so will there be any changes to the table properties

       

      2. Assume that we are migrating from non-SAP(SQL server) to S/4 HANA and we have multiple work streams in use on legacy.

      2A. How do we identify which table and fields in legacy goes to each table in SAP S/4 HANA. eg: in legacy material/purchasing are maintained in 1 table.

      2B. On a field level if we have to transform eg: legacy purchasing group A, B, C should be mapped to  SAP Purchasing group X. Coming from a non-SAP system to support the SAP config, will the "Line of code" or "include" the only options for transformation.(I understand SLT is not primarily used for transformation)

      2C. Since the table and field names in SQL server and SAP S/4HANA will not be same, do we have to provide mapping in SLT at field level. eg: Purchasing-materialno = MARA-MATNR.

      Author's profile photo Christoph Ostrop
      Christoph Ostrop

      question:

      is it possible to deactivate (and later again activate) the data-transfer/data-synchronisation (in LT-server) via a scheduled ABAP-report ??

      Author's profile photo Rama Shankar
      Rama Shankar

      Awesome Refresher - thanks.