SAP Note

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

Sources
Component: CA-LT-SLT (Cross-Application Components > Landscape Transformation > SAP Landscape
Transformation Replication Server (SLT)), Version: 41, Released On: 19.06.2024

Symptom
You want to learn more about the use of SAP LT Replication Server (SLT) for non ABAP-based
source 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 from non ABAP-based
sources.
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 read
the data from the source system, the supported non ABAP-based sources 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) or as part of SAP S/4HANA.
The following databases can be connected as a non ABAP-based source to SLT 2.0 (DMIS 2011) /
SLT 3.0 (DMIS 2018). Please consider possible restrictions as described in the following
related SAP Notes:

Database SAP Note

SAP HANA 2376535

SAP ASE (Sybase) 2377357

SAP MaxDB 1778969

Oracle 1771460

Microsoft SQL Server 1778971

IBM DB6 (DB2 LUW / DB2 UDB) 1778880

IBM DB4 (DB2 for iSeries) 1877524

IBM DB2 (DB2 for z/OS) 1778975

Important: When replicating data from non ABAP-based sources, there is no guarantee for the
data type mapping / data conversion from SLT. You have to make sure that the respective data
type mapping applied by SLT fits to your needs and data is correctly converted (for example,
if a conversion happens to due different data types). This is especially important when
connecting to non-unicode source. Furthermore, it is not recommended to use SLT for
decommissioning of legacy / third party systems (for example, JD Edwards) as this requires
extensive data type mapping and data conversion via rules (if possible at all).
Important Considerations
The fundamental concept of the trigger-based replication for non ABAP-based source systems
is the same as for ABAP-based source systems. The main differences are that the connection
is a database connection (not an RFC connection) and that the generated function modules
used to read data reside in the SAP LT Replication Server system.

The following restrictions exist:

In case the source table name is longer than 30 characters, the table can still be
loaded / replicated (up to 128 characters long table name) but there is an internal
mapping in SLT which will reduce the table name to 30 characters. Consequently, also the
target table name is limited to 30 characters.
It is not possible to load / replicate tables that have field names that include spaces.
It is not possible to load / replicate tables that have key fields with more than 30
characters. For all other fields, a view needs to be used to map the field names that
exceed 30 characters to shorter field names (max. 30 characters).
It is not possible to load / replicate tables which have mixed or lower case field
names. If you anyways want to use such a table, you need to create a view in the source
which maps all field names to uppercase only and use this view for load / replication.
Additionally the target table needs to have uppercase only field names (if SLT creates
the target table, it will automatically be created with uppercase only field names).
Attention: In case a key field has a mixed or lower case name replication is not
possible at all, even if a view is used to map the column names.
It is not possible to load / replicate tables with user defined (nested) data types -
only elementary data types are supported.
It is not possible to load / replicate tables with DB-specific settings that are not
supported by SAP / ABAP NetWeaver Stack (for example, STREAMS for ORACLE).
It is not possible to replicate tables not having a primary key or unique index.
It is not possible to replicate tables that have a primary key that consists of more
than 16 fields.
It is not possible to replicate tables that have key fields in the middle / end of the
table structure (all key fields need to be at the beginning).
In case there is a default value for a field in the source table, this setting will not
be copied to the target when the target table is created / altered by SLT.
The replication of NULL values is possible starting with DMIS2011 SP15 / DMIS2018 SP00
if the target is an SAP HANA database and certain other restrictions are met - see SAP
Note 2684480.
In lower releases NULL values will be initialized, as ABAP does not know NULL values
(for example, NULL in an integer field will lead to 0 in the target).
Trailing spaces are getting truncated by the ABAP layer, therefore SLT is not able to
differentiate “TEST” from “TEST “. This limitation will lead to:
Inconsistencies if a key-field is affected with the result that no records are
processed any further.
Inconsistencies between the source and target for any non key-field (without any
error indication in SLT).
It is not possible to copy a view definition from a non ABAP-based source to the target
using the Data Provisioning option in LTRC.
Additional aspects to consider:
Starting with SAP LT Replication Server 2.0 (DMIS_2011 SP06), 1 to N replication is
supported for non-ABAP source systems if the following three prerequisites are met:
 For each target system, a different database connection from the source system to
the SLT server is used.
The non-ABAP source database supports the creation of several trigger sets for the
same table (contrary to the ABAP-based sources system 1:n replication, where only
one set of triggers (insert, update, delete) for all replications is created).
As there may be a performance impact associated with creating several trigger sets
for each database table, ensure that the applications running on the source database
are still running with acceptable performance or adapt the source system sizing to
the new setup.
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 data types are mapped to the ABAP Dictionary, 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 query the source database, some data type
combinations may not be supported by SLT as the data types cannot be mapped / data cannot be
read. Make sure to plan respective tests if you are not sure about the possibilities of SLT
to access 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 source 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 database. (see SAP Note 1380654 - SAP support in IaaS
environments). Especially when using Microsoft SQL Server as a source, running the SLT in
the same IaaS environment is critical to ensure a stable connection.

This document refers to

SAP Note/KBA Component Title

2051828 HAN-DP-LTR SLT (2011 SP06) - NON SAP - Correction 09

2042805 HAN-DP-LTR SLT (2011 SP07) - NON SAP - Correction 01

2042801 HAN-DP-LTR SLT (2011 SP06) - NON SAP - Correction 08

2039199 HAN-DP-LTR SLT (2011 SP06) - NON SAP - Correction 07

2031652 HAN-DP-LTR SLT (2011 SP06 / 2010 SP10) - NON SAP - Correction 05

2016511 HAN-DP-LTR Installation/Upgrade SLT - DMIS 2011 SP7

2015417 HAN-DP-LTR SLT (2011 SP06 / 2010 SP10) - NON SAP - Correction 04

2011549 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 14

2011228 HAN-DP-LTR SLT (2011 SP06 / 2010 SP10) - NON SAP - Correction 03

2006029 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 13

2005474 HAN-DP-LTR SLT (2011 SP06 / 2010 SP10) - NON SAP - Correction 02

1990763 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 12

1983148 HAN-DP-LTR SLT (2011 SP06 / 2010 SP10) - NON SAP - Correction 01

1969792 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 11

1969025 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 10

1955228 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 09

1946062 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 08

1943565 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 07

1937950 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 06

1936583 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 05

1929612 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 04

1923685 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 03

1921769 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 02

1903462 HAN-DP-LTR SLT (2011 SP05) - NON SAP - Correction 01

1824710 HAN-DP-LTR Installation/Upgrade SLT - DMIS 2011 SP4 / 2010 SP9

1778975 HAN-DP-LTR SAP LT Replication Server: Using DB2 as non-SAP source

1778971 HAN-DP-LTR SAP LT Replication Server: Using MS SQL as non-SAP source

1778969 HAN-DP-LTR SAP LT Replication Server: Using MaxDB as non-SAP source

1778880 HAN-DP-LTR SAP LT Replication Server: Using DB6 as non-SAP source

1771460 HAN-DP-LTR SAP LT Replication Server: Using ORACLE as non-SAP source

1759156 HAN-DP-LTR Installation/Upgrade SLT - DMIS 2011 SP3 / 2010 SP8

1709225 HAN-DP-LTR Installation/Upgrade SLT - DMIS 2010 SP7 / 2011 SP2

1605140 CA-LT-SLT SAP Landscape Transformation Replication Server (SLT)

This document is referenced by

SAP Component Title
Note/KBA

3464600 Error when reading from ABAP Dictionary for table /1CADMC/XXXXX (RFC destination NONE) -
SLT

3458950 CA-LT-SLT DMIS compatibility with DB's - SAP SLT

2855008 CA-LT-SLT CREATE VIEW permission denied in database - SLT

2693536 HAN-DP- Top level sender structure /1CADMC/L**** does not have key fields - SAP Landscape Transformation
LTR Replication Server

2610189 CA-LT-SLT How to check for key fields on non-SAP source systems - SLT

1877524 CA-LT-SLT IBM i: SAP LT Replication Server: Use of IBM Db2 for i (DB4) as non-SAP source

2376535 CA-LT-SLT SAP LT Replication Server: Using SAP HANA DB as non-ABAP source system database

1605140 CA-LT-SLT SAP Landscape Transformation Replication Server (SLT)

1759156 HAN-DP- Installation/Upgrade SLT - DMIS 2011 SP3 / 2010 SP8

LTR

1824710 HAN-DP- Installation/Upgrade SLT - DMIS 2011 SP4 / 2010 SP9

LTR

1709225 HAN-DP- Installation/Upgrade SLT - DMIS 2010 SP7 / 2011 SP2

LTR

1771460 HAN-DP- SAP LT Replication Server: Using ORACLE as non-SAP source

LTR

1778880 HAN-DP- SAP LT Replication Server: Using DB6 as non-SAP source

LTR

1778975 HAN-DP- SAP LT Replication Server: Using DB2 as non-SAP source

LTR

1778969 HAN-DP- SAP LT Replication Server: Using MaxDB as non-SAP source

LTR

1778971 HAN-DP- SAP LT Replication Server: Using MS SQL as non-SAP source

LTR