Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

Summary of the SLT email notification function. I take no credit for the documentation as it is straight from SAP, I just provided the screen-shots 🙂

There are also additional functions for monitoring logging table build up in the source system as well as latency statistics which are very useful in tracking down a process which could be the root cause for latency fluctuations i.e. COPA transaction KE27. I will try and document the usage of these statistics against HANA logs, but in another blog.

SLT Email Notification setup:


Any issue in the replication process can be very critical for the HANA side by side approach. Therefore it's important that the SLT admin will get aware of any issue as soon as possible. To avoid a permanent monitoring of the SLT System, notification functionality is provided.

The functionality is implemented in the following way. There will be one background job running in a defined interval which checks all SLT configurations where notifications are activated.


The Notification settings can be reached from the LT Replicator Cockpit (Transaction LTRC), or via transaction IUUC_REPL_EN.


SAPconnect must be properly configured for correct email output -> Verify transaction SCOT.


Tab 'General Settings'

You must activate the Notification on each configuration (mass transfer ID) you want to be checked periodically by system.  You do this by checking the field 'active , and saving.  The Notification Job is automatically launched/adjusted/stopped upon the save.

You can change the frequency (in seconds) that the checks should be executed,  as well the interval you want to be notified via email (in minutes).

It is also possible to activate and deactivate every check individually, for each configuration.


Tab 'Latency Thresholds'

Here you can define individual threshold (in seconds) for error and warning, for each table. These settings are optional. Tables not defined here will assume system defaults. The warning and error values could be combined with the settings in the COPA accelerator safety buffer value i.e. 600 second safety buffer in COPA, with 300 seconds as a warning from SLT and 600 seconds as an error. The error value could be set lower i.e. at 500 in order to give a buffer during which an action could be taken.

Tab 'e-Mail Receivers'

In this tab, the email addresses of the notification receivers are defined.  Each configuration can have multiple receivers.

For each receiver, it can be selected the type of messages to be included in the notification (Info, Warnings, Errors).


On the bottom of the screen, you can check the Notification Job status, as well the last execution timestamp & last notification timestamp.


In case of any issues, an email will be send to all registered users. The error notification should run the following checks :

- Check if Master Job is running

- Check connection to source and target system

- Check if all data load jobs are running

- Check if load and replication works and jobs are not waiting for any resource (e.g.  Table lock, connection to HANA)

- Check if job status is valid

- Check trigger status

- Check size of the logging tables

- Check latency figures (critical latency time could be defined for the entire configuration and on table level)

- Check flags in table IUUC_TABLES

- Check flags in table DMC_MT_TABLES

- Check flags in table DMC_ACS_PLAN_HDR

- Check flags in table IUUC_RS_STATUS

- Runtime object issues

- Application Errors

Labels in this area