...
For detailed information about how to implement these steps, see the guide from the the SAP Note 2652704 - Replicating Data Using SAP LT Replication Server SDKNote 2652704.
Deployment
The solution can be deployed in 2 modes:
...
ID - Mass transfer ID which is represented by the specific SAP LT configuration. If this value is empty all configuration which doesn’t have a specific setup will use this one
Storage - Storage ID which will be used for the SNP Glue™ table creation. It needs to exist on the system where the SNP Glue™ table will be generated
RFC to SNP Glue™- RFC destination from a system where SLT is operated to the system where transfer of the data should be executed. This value can be empty for the case of processing the data on the same system where the SLT is executed
RFC to SLT - RFC destination from a system where transfer of the data should be executed to the system where SLT is operated. This value can be empty for the case of processing the data on the same system where the SLT is executed
Prefix - prefix of the generated SNP Glue™ objects. The value must start with the 'Z' character, placeholder <MT> is supported which in case of use will be replaced by the Mass transfer ID value
Package - package for the SNP Glue™ objects to be generated. In case the system where SLT is operated is not the same as the system where data transfer should be executed the same package needs to exist on both systems
Watchdog - name of the Queue watchdog from the system where data transfer should be executed
Capture timestamp - checkbox for adding the additional column into the SNP Glue™ table with the value of timestamp when the data was received from the SAP LT functionality
Profile name - name of the Profile profile which should be used in the generation of the SNP Glue™ table
Escape / in tabname - checkbox for escaping the '/' by '_' character in generated SNP Glue™ table name
Enable Merge - checkbox for enabling Merge for SNP Glue™ Consumer and Key deduplication in SNP Glue™ Queue Fetcher.
...
In case the replication of the data from a source table get stuck and there are visible errors for the table (such as “Migration object .. has been deleted due to changes in table definition“ or “Replication job canceled by the user (job name/1LT/.. )“ ) it is necessary to manually suspend and resume replication for the table or to deactivate and activate the whole configuration to unstuck the replication.
Update of generated objects
In case of upgrading to a new SNP Glue™ SLT version, it might be needed to update already generated Glue objects to get new features/bug fixes or performance improvements. Go to SNP Glue™ cockpit (/DVD/GLUE) and in the menu pick Tools → SLT integration → Update Glue objects.
The screen contains a select option for the Mass transfer ID and a select option for the Source table.
The button Show objects can be used for a visual check of the objects that can be updated.
Executing the report will update generated Glue objects.
Deletion of generated objects
...