SNP Glue SLT facilitates the replication of data between two SAP systems, providing a solution when SAP SLT is unable to replicate tables due to structural differences in tables between S/4 and non-S/4 systems.
You’ll find the required configuration details for this scenario below.
Via SNP Glue™ cockpit (/DVD/GLUE) access in the menu Tools > SLT integration > Setup maintenance.
Storage ID can be empty. In this scenario, the data is stored in the SAP primary database, therefore the connection of the external storage is not used.
Glue scheduler - do not use parallelization. This feature is not available for SAP to SAP replication.
Capture timestamp - must be enabled.
Enable merge - this parameter defines whether the SNP Glue should process delete operations on the target SAP table. If not specified, the deletion operations are ignored.
New parameter Glue SLT SAP consumer must be enabled. If checked, SNP Glue logic will create an SAP table consumer (instead of a standard Glue table consumer) which is required for this use case.
The additional parameters should be configured in the same manner as a typical SLT replication scenario.