Skip to Content

Our production system is ECC 6.0 and we are not  planning to upgrade and migrate our system to HANA in a short period of time. On the other hand we want to use Hana live analitics and consume our real-time data with Lumira. For this requirement we decided to go with sidecar POC senario. With the DMIS addon capability we can make ABAP to ABAP replication for the specified tables. Our sidecar scenario requires standalone SLT and HANA license.


First of all we need to check our systems patch level and start for installing DMIS addon for SLT. On the ERP side we need to  install DMIS 2011_1_700 SP9 addon. In our case, SAP LT Replication Server is in the same system and we don’t need to check compatibility for support package level on both systems.

In the target system (Business Suite on Hana, ECC 6.07) also I have installed DMIS addon 2011_1_731 SP9. Main OSS note for DMIS addon is “2191214 – Installation/Upgrade SLT – DMIS 2011 SP9”. As an alternate you can use SAP Solution Manager system as an LT Replication server for non production usage. For productive usage SAP recommends dedicated SAP LT Replication server.


In the both side RFC connections were created and tested before creating configuration. For ABAP source system, we created a new user (do not use DDIC) and assigned the role IUUC_REPL_REMOTE  for RFC connection. With DMIS addon, two new roles have been created. In the replication system, roles SAP_IUUC_REPL_ADMIN and SAP_IUUC_REPL_DISPLAY are required to create, change or display configurations. Additionally i gave the roles related with NW Business Client which role names are including *NWBC*. You can follow the Application Operations Guide for SAP LT  at service.sap.com/instguides.


After preparation steps, we defined a connection between the source and target system. SAP defines this information as a configuration. In the replication server via transcation LTR we have created new config which name is ERP2HANA. In the configuration wizard, we specified source and target system and rfc names with the standard transfer settings. Now we were ready for the replication. In the transaction LTRC, gone through Data Provisioning button and selected the tables VBAK and VBAP then executed succesfully. You need to check the tables are exist in the both side exactly, because SLT couldnot create the target table structure.  Also if you have different client number between source and target; you need to specify transfer rules.  In my case, i am using Lumira and handling with the help of it without defining transfer rules.

/wp-content/uploads/2015/12/1_848110.png

In the LT Replication Server Cockpit (LTRC) i can check the transfer status for tables, view and analyze errors, change table write modes, reset load and replication in the expert mode. During replication you can get dublicate error short dump and use oss note 1972009 for solving and resetting status. Also MWBMON transaction can be used for monitoring mass data transfer.  /wp-content/uploads/2015/12/2_848126.png

/wp-content/uploads/2015/12/3_848127.png

/wp-content/uploads/2015/12/4_848128.png

After sucessfully transferring data to HANA, I have validated data by running a simple SQL sentence in HANA studio.

/wp-content/uploads/2015/12/5_848205.png

To report this post you need to login first.

2 Comments

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

Leave a Reply