SAP SLT Replication :

SAP SLT Replication : SAP Landscape Transformation Replication Server (SLT)

In this Blog we will explain the SAP SLT Replication and alert Configuration.
SAP SLT Replication use to move data in different sap systems within same network.

SAP SLT Replication Integration Monitoring Setup

Technical Prerequisites:

Below Components is required on SAP system for SLT.

1. Below components is required on managed system-SLT system.
DMIS Version: 2011* SP1 or higher version
2. Additional below components is required in SLT system.
ST-PI 2008_1 700 SP6 or higher
ST-A/PI 01P or higher

Integration Monitoring Setup:

We need to add the Integration & Exception Monitoring then select the monitoring catalogs as per the configuration.

• Execute the transaction – FRUN for Integration & Exception Monitoring and click the Integration & Exception Monitoring.
• Configuration panel —Technical systems then click the pen icon.
• Check the user system SID and select. If system not exists then Click add button and add the system.
• Once added the system, we can see the all monitoring categories is available on the system.
• Based on the scope select monitoring categories

LTRO : Monitoring transaction for SLT

Configure Filter:

• Execute the LTRO
• Select the view Monitoring
• Click Plus option for add the new filter
• Select the category for filter and mention the filter name.
• Select the target client and SAP System.

Available options for filter:

1. Source system Replication
2. Target system replication
3. SLT configuration name
4. Status of the Replication : Error or success

Alerts Configuration for SLT:

Based on the alert Configuration, we will receive the alert for SLT status.

1. Goto Alerting view
2. Click option + and enter the alert information
3. Select the monitoring category
4. Select the metric name details
5. Enter the name of the alert fot SLT
6. Click check box for activate the alert and based on threshold value alert will be generate.

Below Metric is available for Alert SLT:

1. SLT Replication with Error
2. Load Jobs Config Not Run
3. Load Jobs Status
4. Load Jobs Terminated
5. Source Status
6. Target Status
7. Others Metrics.

Other information for SLT:

data transfer from ECC/APO system to BW system.

• Login to the SAP system –LT system.
• Run transaction LTRC . This transaction will open the SAP LT replication server Cockpit.
• Select the Mass Transfer ID
• Go to the tab: Administration Data
• As per requirement select the active or deactive option for under Configuration status.

If SLT is using real-time replication data then it is continuously checking the logging tables for new records.
There are the ways for customer can reduce the number of the calls to the source system.

1. Need to Change the real-time replication to Interval.
If required change the LTR Settings, where the customer can specify the time in minutes, hours, day, the frequency to check the logging tables on sap system.
Perhaps once per minute is enough. Only issue with this is latency will be increase, having up to a minute of latency in the time the record appears in Hana target.

Change the logging table check behavior. In LTRC-> Utilities-> Specify Option for Logging Tables,
The another option is available for Process Logging Tables with Records will avoid querying the logging tables when they are empty and this is best option for logging tables.

How to check the Error Logs in SLT:

• Log into SLT system
• Execute the transaction LTRC
• Enter the your MT_ID and Execute
• Click the Application Log Tab then filter the ID and table name for error overview
• Check both system logs for the Source & SLT system
• Check the SM21 logs
• Check ST22 logs for analysis
• Check the WP logs in SM50

Validate Record Counts on Source R/3 System or Hana db level:
SAP SYSTEM:

• Log into SAP SYSTEM
• Execute the Transaction SE16
• Put in table name and execute
• Click on Number of Entries details.

HANA System

• Log into HANA Studio
• go to the Table in HANA
• Right click on table and click Open Definition
• Click on the Runtime Information
• In the General section then check the Number of Entries
Compare the both system no of the logs