2737003 - SAP Landscape Transformation Replication Server (SLT): Non ABAP-based Targets

Symptom

You want to learn more about the use of SAP LT Replication Server (SLT) for non ABAP-based target systems.

Other Terms

LT Replication Server, SLT, replication, replicator, trigger, real-time, non ABAP, database connection, DMIS 2010, DMIS 2011, DMIS 2018

Reason and Prerequisites

You plan to use SAP LT Replication Server for the replication of data to non ABAP-based targets.

Important: Verify with your database vendor if your license entitles you to establish a permanent database connection with a 3rd party tool like SLT.

Solution

Supported Databases

Due to the use of OPEN SQL in the function modules generated by SLT which are used to write the data to the target system, the supported non ABAP-based targets are restricted to the databases officially supported by SAP NetWeaver. The supported DB versions are further dependent on the SAP NetWeaver release and the related DBSL version installed on the SAP LT Replication Server instance (see details in Product Availability Matrix https://service.sap.com/pam). Note: Due to the dependency on SAP NetWeaver for connectivity, only SAP HANA is supported as a direct database source of SLT when using SAP LT Replication Server for SAP S/4HANA (DMIS 2020).

The following databases can be connected as a non ABAP-based target to SLT 2.0 (DMIS 2011) / SLT 3.0 (DMIS 2018):

• SAP HANA
• SAP VORA (see SAP Note 2647941)
• SAP ASE (Sybase) 
• SAP MaxDB 
• Oracle 
• Microsoft SQL Server 
• IBM DB6 (DB2 LUW / DB2 UDB) 
• IBM DB4 (DB2 for iSeries) 
• IBM DB2 (DB2 for z/OS)

In order to replicate data via SLT to SAP HANA, it is possible to create a SLT configuration by only using an administration user. SLT will then automatically create a new user and schema in the target as well as DBCO entries in the SLT system. For more information refer to the guides on the SAP Help Portal (https://help.sap.com/sapslt).

In order to replicate data via SLT to any other listed target, it is necessary that user, schema, tablespace (where applicable) and a respective database connection (DBCO entry) exist. The user maintained in the database connection needs to have full read / write access to the target schema. Additionally, for some databases (like SAP HANA) PUBLIC SYNONYMS are used. Consequently the database user needs to have the respective authorization.

Note: Starting with DMIS 2011 SP16 / DMIS 2018 SP01 the approach of using an existing DBCO entry can also be used for an SAP HANA target. It is available as the target option "SAP HANA (Target DB Connection Not Managed by SLT)".

Important Considerations

The following restrictions exist:

• The maximum length of a target table name is 30 characters.

Data Type Mapping
When replicating data from a source system to a target system, the source system database data types must be mapped to the target system database data types. For information on how the ABAP Dictionary data types are mapped to different target system database types see SAP Note 2394986. You can also find this information in the help section of transaction LTRS in the SLT system.
Important: Due to the use of OPEN SQL in order to write data to the target database some data type combinations may not be supported by SLT as the data types cannot be mapped / data cannot be written correctly. Make sure to plan respective tests if you are not sure about the possibilities of SLT to write the data.

Not Supported Databases
In general, any database not listed in the list of supported databases is not supported by SLT. Especially Microsoft Azure is NOT supported (see SAP Note 2497147).

Information on IaaS environments
When the target of your SLT replication is hosted in an Infrastructure as a Service environment, it may be necessary to have the SLT system also run in the IaaS environment to ensure a stable connection to the target database. (see SAP Note 1380654 - SAP support in IaaS environments). Especially when using Microsoft SQL Server as a target, running the SLT in the same IaaS environment is critical to ensure a stable connection.