Describing the Architecture for Replication into an ABAP System

Objective

After completing this lesson, you will be able to describe replication to ABAP-based SAP systems.

Data Replication into ABAP-Based Systems

Replication between ABAP systems is available from SAP Landscape Transformation Replication Server DMIS2011 SP6 onwards. A standard SLT license is required to use this function.

Starting from DMIS 2011 SP12, for ABAP-based SAP source systems running on SAP HANA, you can specify settings related to data- aging. You can avoid replicating changes to data-aging fields to the target system as prerequisites SP12 is required also on the source system.

A diagram of ABAP-to-ABAP replication architecture shows data flow from SAP Business Suite to SAP LT Replication Server and then to another SAP Business Suite via RFC connections.

See the following SAP Notes:

  • 2415064 - Release Information SLT - DMIS 2011 SP12
  • 2570052 - Release Information SLT - DMIS 2011 SP14
  • 2198671 - SLT (2011 SP06 - SP09) - Data-aging in the case of SAP HANA DB source systems is not considered - source system correction
  • 2968667 - SLT Source & Central System (DMIS 2011, DMIS 2018, S/4HANA OP 1909 and 2020): Failed to created triggers for HANA DB source - invalid data aging column
The image illustrates the architecture for Non-ABAP to ABAP data replication, involving source systems, SAP LT Replication Server, and SAP Business Suite with application tables.

In the case of a non-ABAP source system, instead of connecting it via the RFC destination, the connection is established using a database connection between SLT and the source system. Otherwise, there is no difference to ABAP-to-ABAP replication.

Note

For more information, see SAP Note 1768805 for limitations on non-SAP source systems.
Diagram showing ABAP Source system connected to SLT Replication Server, which is then connected to ABAP system. Both connections are labeled RFC Connection with user SAP_IUC_REPL_REMOTE.

The role for the RFC user in the ABAP source system can also be used to allow the RFC user to connect to the ABAP target system.

For information on authorization requirements using SAP HANA DB as a non-ABAP source system database, see SAP Note 2376535.

Diagram showing three different SLT deployment options: separate instance, on source, and on target, with SAP systems

All ABAP source and target systems require the installation of DMIS 2011 or DMIS 2018. Remember to keep the support packages of the DMIS AddOn in sync.

However, SAP supports a support package level in the ABAP source and target systems that is up to three stacks lower than the central instance that manages the replication.

For example, if the central instance is on DMIS 2018 SP03, the target and source system AddOn requires at least DMIS 2018 SP00.

If you want to run SAP LT Replication Server on an SAP S/4HANA system, the installation of the DMIS AddOn is not required in the SAP S/4HANA system. This is because SAP LT Replication Server is part of SAP S/4HANA. In this case, you only need to consider the installation aspects for the source system (if it is a SAP NetWeaver-based system).

Note

The following are restrictions for ABAP-based target systems:

  • No replication logging

  • No target table creation

Replication logging was designed for native database replication scenarios. Therefore, it does not support scenarios that are connected via an RFC connection on the receiver side, such as Central Finance and BW scenarios such as ODP.

In addition, replication logging is not released for complex objects, such as predefined objects or central finance.

In the ABAP target system, the target tables must already exist and must not be deleted by SLT. This can lead to duplicate errors if repeated initial load or replication attempts occur.

If the source and target clients are different, a transformation rule for the client-field might be required so that the data is visible in the target system.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn