Real-Time Data Replication with SLT – TechEd && d-code 2014 Overview

Real-Time Data Replication with SLT – TechEd && d-code 2014 Overview

The recent TechEd && d-code in Berlin featured several sessions about the SAP LT Replication server. In this blog I will introduce SLT to you and give a summary of the new SLT features that were presented at the convention.

SAP LT Replication server

The replication server is positioned for scheduled or real-time (trigger-based) data replication from ABAP and non-ABAP sources (SAP NetWeaver supported databases only). SLT is recommended for real-time data replication business scenarios. As we have seen in a demonstration, data can be available in the target system in less than 1 minute. Therefor it will be the ideal solution for real-time data replication. Target systems can be SAP HANA, SAP Business Suite, SAP BW and SAP Data Services. The SLT Replication Server is embedded in your landscape and will not disrupt your existing operations.

Operational Data Provisioning (ODP) Infrastructure

The replication server uses the Operational Provisioning Framework. It is possible to connect several data providers, each with its own delta queue mechanism (ODQ). The delta queue mechanism is loaded with data from the source and there will be a database trigger for each new, changed or deleted record. You can even define how long data will be kept in the delta queue. More than one subscriber can use a defined delta queue at the same time.

ODP Framework

Architectural Concepts

Replication is possible from ABAP and non-ABAP source systems into ODP. The connection from ABAP source systems is setup by a RFC connection. Connections to non-ABAP sources are made via a DB connection and is only available for SAP NetWeaver supported databases.

SLT and ODP

As you can see in the picture above, it is possible to transfer the data out of the ODQ directly into a DSO or InfoCube. The PSA layer has become optional. Therefor the loading time to SAP BW can be reduced.

Use case for ABAP to ABAP replication are:

  • Transfer data between two ECC systems
  • Replacement of a batch-oriented option to move data between systems
  • Fill additional ABAP system beside ECC with real-time data
The replication between ABAP systems is general available with SAP LT Replication Server DMIS2011 SP6. The standard SLT license is required to be able to use this function.
The replication between ABAP systems is general available with SAP LT Replication Server DMIS2011 SP6. The standard SLT license is required to be able to use this function.

Use cases for ABAP to non-ABAP replication are:

  • Fill additional non-ABAP systems with real-time data
  • To feed in-house developed solutions, legacy or 3rd party non-ABAP products to analyze their business data
  • SLT to feed analytical systems with data in real-time and minimize the transfer volume by transferring only delta data
The replication between from ABAP to non-ABAP systems is not general available with SAP LT Replication Server DMIS2011 SP07. The technical foundation is feasible to achieve such a replication, but it is not unrestricted enabled. Wrong data types could harm the systems, SAP recommend to evaluate in a small project feasibility of your use case and will activate and enable you for the non-ABAP target replication. The standard SLT license is required to be able to use this function.
The replication between from ABAP to non-ABAP systems is not general available with SAP LT Replication Server DMIS2011 SP07. The technical foundation is feasible to achieve such a replication, but it is not unrestricted enabled. Wrong data types could harm the systems, SAP recommend to evaluate in a small project feasibility of your use case and will activate and enable you for the non-ABAP target replication. The standard SLT license is required to be able to use this function.

DB Supportability Matrix for Replication to SAP HANA

As you can see in the table below, a lot of non-ABAP databases are supported.

DB Supportability Matrix for Replication to SAP HANA

‘SLT’ Replication Concept: Multi System Support

Within the replication concept it isn’t possible to support several scenarios with source and target systems (1:1, 1:N and/or N:1 Replication).

SLT Replication Concept Multi System Support

‘SLT’: Data and Structure Transformation Capabilities

While the data is replicated from the source system to the target system, there are several transformation capabilities:

  1. Reduce number of records by filter (e.g. only specific years, customers or vendors should be used in HANA).
  2. Data conversion (e.g. make certain fields anonymous for HR reporting, fill initial fields, convert units or currency and recalculate amounts and values using coded rules).
  3. Adjustment of target table structures (e.g. remove fields that are not required in the HANA system, add additional fields, merge the same table from different source systems).

Via the transaction IUUC_REPL_CONTENT there are more transformation capabilities available. For more information about this topic, see SAP NOTE 1733714 which includes the guide “Advanced Replication Settings”.

Product road map overview – key themes and capabilities

As you can see in the roadmap overview below, SAP is planning to create an open interface to feed analytical non-ABAP target systems from ABAP source systems. A lot of customers will appreciate this.

Product road map overview SLT

The Replication Server is for most customers relatively new and not being used at the moment (only 2874 customer landscapes according to SAP). Personally, I think this tool will be very interesting in the near future.The recent TechEd && d-code in Berlin featured several sessions about the SAP LT Replication server. In this blog I will introduce SLT to you and give a summary of the new SLT features that were presented at the convention.

SAP LT Replication server

The replication server is positioned for scheduled or real-time (trigger-based) data replication from ABAP and non-ABAP sources (SAP NetWeaver supported databases only). SLT is recommended for real-time data replication business scenarios. As we have seen in a demonstration, data can be available in the target system in less than 1 minute. Therefor it will be the ideal solution for real-time data replication. Target systems can be SAP HANA, SAP Business Suite, SAP BW and SAP Data Services. The SLT Replication Server is embedded in your landscape and will not disrupt your existing operations.

Operational Data Provisioning (ODP) Infrastructure

The replication server uses the Operational Provisioning Framework. It is possible to connect several data providers, each with its own delta queue mechanism (ODQ). The delta queue mechanism is loaded with data from the source and there will be a database trigger for each new, changed or deleted record. You can even define how long data will be kept in the delta queue. More than one subscriber can use a defined delta queue at the same time.

ODP Framework

Architectural Concepts

Replication is possible from ABAP and non-ABAP source systems into ODP. The connection from ABAP source systems is setup by a RFC connection. Connections to non-ABAP sources are made via a DB connection and is only available for SAP NetWeaver supported databases.

SLT and ODP

As you can see in the picture above, it is possible to transfer the data out of the ODQ directly into a DSO or InfoCube. The PSA layer has become optional. Therefor the loading time to SAP BW can be reduced.

Use case for ABAP to ABAP replication are:

  • Transfer data between two ECC systems
  • Replacement of a batch-oriented option to move data between systems
  • Fill additional ABAP system beside ECC with real-time data
The replication between ABAP systems is general available with SAP LT Replication Server DMIS2011 SP6. The standard SLT license is required to be able to use this function.

The replication between ABAP systems is general available with SAP LT Replication Server DMIS2011 SP6. The standard SLT license is required to be able to use this function.

Use cases for ABAP to non-ABAP replication are:

  • Fill additional non-ABAP systems with real-time data
  • To feed in-house developed solutions, legacy or 3rd party non-ABAP products to analyze their business data
  • SLT to feed analytical systems with data in real-time and minimize the transfer volume by transferring only delta data
The replication between from ABAP to non-ABAP systems is not general available with SAP LT Replication Server DMIS2011 SP07. The technical foundation is feasible to achieve such a replication, but it is not unrestricted enabled. Wrong data types could harm the systems, SAP recommend to evaluate in a small project feasibility of your use case and will activate and enable you for the non-ABAP target replication. The standard SLT license is required to be able to use this function.

The replication between from ABAP to non-ABAP systems is not general available with SAP LT Replication Server DMIS2011 SP07. The technical foundation is feasible to achieve such a replication, but it is not unrestricted enabled. Wrong data types could harm the systems, SAP recommend to evaluate in a small project feasibility of your use case and will activate and enable you for the non-ABAP target replication. The standard SLT license is required to be able to use this function.

DB Supportability Matrix for Replication to SAP HANA

As you can see in the table below, a lot of non-ABAP databases are supported.

DB Supportability Matrix for Replication to SAP HANA

‘SLT’ Replication Concept: Multi System Support

Within the replication concept it isn’t possible to support several scenarios with source and target systems (1:1, 1:N and/or N:1 Replication).

SLT Replication Concept Multi System Support

‘SLT’: Data and Structure Transformation Capabilities

While the data is replicated from the source system to the target system, there are several transformation capabilities:

  1. Reduce number of records by filter (e.g. only specific years, customers or vendors should be used in HANA).
  2. Data conversion (e.g. make certain fields anonymous for HR reporting, fill initial fields, convert units or currency and recalculate amounts and values using coded rules).
  3. Adjustment of target table structures (e.g. remove fields that are not required in the HANA system, add additional fields, merge the same table from different source systems).

Via the transaction IUUC_REPL_CONTENT there are more transformation capabilities available. For more information about this topic, see SAP NOTE 1733714 which includes the guide “Advanced Replication Settings”.

Product road map overview – key themes and capabilities

As you can see in the roadmap overview below, SAP is planning to create an open interface to feed analytical non-ABAP target systems from ABAP source systems. A lot of customers will appreciate this.

Product road map overview SLT

The Replication Server is for most customers relatively new and not being used at the moment (only 2874 customer landscapes according to SAP). Personally, I think this tool will be very interesting in the near future.

Sander van Dillen