Skip to Content

This document presents step by step procedure for Trigger-Based Data Replication from ECC to HANA system using SAP Landscape Transformation (SLT) based on capturing database changes at a high level of abstraction in the source ERP system.

Initial Load and Simultaneous Delta Replication


The initial load of business data is initiated using the SAP HANA studio. The initial load message is sent from the SAP HANA system to the SLT system (based on SAP NetWeaver 7.02 with kernel 7.20 EXT), which in turn passes the initialization message to the ERP system. The ERP system begins by setting up database transaction log tables for each table to be replicated. After the transaction tables are completed, the SLT system begins a multi-threaded replication of data to the target system, which enables high speed data transfer.

           

The initial load of data can be executed while the source system is active. The system load that this process causes can be controlled by adjusting the number of worker threads performing the initial replication.

In parallel to the initial load, by means of database-specific triggers, the SLT system begins detecting any data changes that occur while the initial load process is running. These changes are logged to the transaction tables, and are propagated to the target SAP HANA system.

Continuous Delta Replication after Initial Load


After the initial load process has completed, the SLT system continues to monitor the transaction tables in the ERP system, and replicates data changes in the source system to the SAP HANA system in near real time.


/wp-content/uploads/2014/04/1_436653.jpg

Step by Step Procedure for Replication:

  1. Logon to SAP LT system and create a new configuration./wp-content/uploads/2014/04/2_436654.jpg

         /wp-content/uploads/2014/04/3_436682.jpg

         /wp-content/uploads/2014/04/4_436683.jpg

Enter a distinct configuration name (A schema of same name would be created in HANA system), Initial load mode as resource optimized, appropriate RFC Connection (ECC <–> LT), Data Transfer and calculation jobs. Replication would be Real time. Also mention the target HANA system credentials and click on Ok.

/wp-content/uploads/2014/04/5_436684.jpg/wp-content/uploads/2014/04/6_436685.jpg

.

  2. Logon to HANA Studio with the appropriate credentials . Here a schema of same name as configuration would be created.

      /wp-content/uploads/2014/04/7_436686.jpg

Click on Data Provisioning through Quick Launch.

/wp-content/uploads/2014/04/8_436687.jpg

This will take take us to SLT Based Table Data Provisioning.  Here we can see 3 tables are already being replicated without user replicating them. These tables basically provide HANA system with information of all the tables in source system.

/wp-content/uploads/2014/04/9_436702.jpg

Now for loading any table click on “Load” and select the table from the list of tables available in the source system and click finish.

Lets first take an example of  loading Material master table – MARA

/wp-content/uploads/2014/04/10_436689.jpg

The loading is scheduled and once completed status is set as executed.

/wp-content/uploads/2014/04/11_436690.jpg

/wp-content/uploads/2014/04/12_436691.jpg

With this, table “MARA” get loaded from Source ECC system to SAP HANA system.

/wp-content/uploads/2014/04/13_436692.jpg

/wp-content/uploads/2014/04/14_436693.jpg

For replication purpose lets take example of application table –VBAP (Sales Document line item data).

Click on “Replication” button and select VBAP table.

/wp-content/uploads/2014/04/15_436694.jpg

This will load the VBAP table and then set the status “In process” for replicating changes in the VBAP table in source system.

/wp-content/uploads/2014/04/16_436695.jpg

To show the replication process lets create one more record on the ECC side (with reference) which gets replicated to the HANA system as shown below:

/wp-content/uploads/2014/04/17_436696.jpg

/wp-content/uploads/2014/04/18_436697.jpg

/wp-content/uploads/2014/04/19_436698.jpg

Now a Sales Document with Document number (VBELN) – 13553 is created.

The same document would be replicated to HANA system in real time.

/wp-content/uploads/2014/04/20_436699.jpg

/wp-content/uploads/2014/04/21_436700.jpg

This completes our basic objective of replicating data from SAP ECC system to SAP HANA system in real time using SLT.

To report this post you need to login first.

8 Comments

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

  1. Sudha Rao

    Hi, thanks for the detailed blog on SLT.

    So i understand that even if the table is not loaded for the first time, and if user clicks on ” replicate” button in the studio, it will still trigger the first load and replicate later.

    One question is : is the size of the Log table defined / configurable anywhere?

    (0) 
    1. Ankit Mittal Post author

      Thanks Ranjit , Aruna and Sudha..

      @Sudha :We can set the maximum allowed value (maximum number of result record) using preferences but as far as size of log tables is concerned I think HANA Admin takes care of it …as an application developer we refer job logs to find successful/unsuccessful jobs and its cause. I will revert back to you once i find an appropriate answer to your question..

      (0) 
  2. Shahid Kassim

    Dear,

    First of all, thanks a lot of this step by step guide.

    I have a question to complete the sales order process described above.
    Assume we replicate the good issue table and post the good issue in the source system. Good issue document will be then replicated to Hana.
    Is there any way to automatically generate the financial posting in Hana based on its configuration based on the good issue document?

    Best regards

    (0) 
  3. Rajesh Sanikommu

    Hi,

    That’s detailed information, Thanks for providing that. I believe there should a table which holds all the table load details and its time stamp. Could you let me know if any one aware of this table.

    Thanks!!

    (0) 

Leave a Reply