(Glue-2111) SLT Integration

Owned by SNP
Nov 22, 2021
5 min read

Datavard Glue provides an option to integrate SAP LT with its data extraction framework. This enables you to leverage the existing SLT implementation and provide the ever-growing Glue support for multiple targets,

The solution enables you to:

  • Support batch and real-time data integration

  • Write to multiple targets, leveraging queues

  • Control load and performance

  • Deploy Datavard Glue on separate box from SLT

  • Handle new sources/targets in an automated way

The integration leverages SAP LT SDK to write to custom ABAP-based targets via BADI implementation. The end-to-end process is seamless and automated.

This page describes the configuration required and additional information about troubleshooting and clean-up activities.

For detailed information about how to implement these steps, see the guide from the SAP Note 2652704  - Replicating Data Using SAP LT Replication Server SDK.

Deployment

The solution can be deployed in 2 modes:

  • Standard deployment

  • Separate box deployment

Standard deployment

SLT and Datavard Glue run on the same SAP system.

Separate box deployment

In this deployment SLT and Datavard Glue run on separate SAP systems.

The prerequisites for this scenario are the following:

  • Datavard Glue and Datavard Glue SLT connector are imported to both SAP LT and the Glue Box

  • RFC communication is enabled in both directions between SLT and Datavard Glue

  • Package DMIS_2011_1_731 or above is present in the Datavard Glue box

Configuration Information

Before the replication run

For the replication to start the valid SAP LT configuration needs to exist and the Glue SLT setup needs to be preset.

SAP LT configuration

Go to transaction LTRC and click the button New to create a new configuration. The system displays a dialog box where you can specify the settings for the new configuration. Note the following important settings when creating the configuration:

  • In the step Specify Target System, enter the connection data to the target system. Choose RFC Connection as the connection type. In the field Scenario for RFC Communication, select the value Write Data to Target Using BAdI from the dropdown list. The RFC connection is automatically set to NONE.

  • In the step Specify Transfer Settings, use the input help (F4 help) for the field Application to find the application ZDVD_GLUE. The application is automatically added into the SAP LT customizing when Glue transport is imported into the system.

Preset of Glue SLT setup

Via Glue cockpit (/DVD/GLUE) access in the menu Tools → SLT integration → Setup maintenance. This will direct you to the SM30 for the table /DVD/GL_SLT_SETT. Glue SLT setup needs to be filled before starting any replication in SAP LT.

The Maintain button will enable you to create/edit a setup that will be used for the generation of the Glue objects. The fields of the table are:

  • 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 Glue table creation. It needs to exist on the system where the Glue table will be generated

  • RFC to 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 Glue objects. It is necessary that the value starts 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 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 Glue table with the value of timestamp when the data was received from the SAP LT functionality

  • Profile name - name of the Profile which should be used in the generation of the Glue table

  • Escape / in tabname - checkbox for escaping the '/' by '_' character in generated Glue table name

After the replication run

SAP LT replication will generate Glue objects and prepare the data to be transferred to the target storage. In case the created replication for a specific source is no longer required by the user, generated Glue objects with Glue SLT metadata can be deleted. Also, all actions within the Glue SLT integration create application logs.

Transfer data to target storage

To complete the data transfer the extraction via generated Extraction Process needs to be executed. For that, the Queue watchdog can be used (if it was set in the Glue SLT setup) or the user can manually execute the extraction.

Deletion of generated objects

Via Glue cockpit (/DVD/GLUE) access in the menu Tools → SLT integration → Deletion report. This will submit a report for the deletion of the generated Glue objects for the specific combination of Mass transfer ID and source name.

The screen contains select-option for the Mass transfer ID which is mandatory and select-option for the Source table.

The button Show objects can be used for a visual check of the objects before the execution of deletion based on the filled selection.

After pressing the execute button the confirmation pop-up will be displayed.

Glue SLT application logs

To access application logs go to transaction SLG1 and fill screen input Subobject with '/DVD/GL_SLT'.