Monitoring

You need a holistic, cross-configuration view of every replication across the whole SLT landscape, not the tools for one specific configuration. Which transaction do you open?

Before you activate SLT email notifications, one piece of infrastructure must already be working or no mail will ever go out. What must you verify first, and where?

SLT health checks are split into two families. Into which family does the trigger check fall, and why does that distinction matter operationally?

You want to run an SLT health check right now rather than wait for the scheduled background job, then read the outcome. What two LTRC buttons do you use, in order?

Which SAP Solution Manager application do you use to detect actual data inconsistencies between the SLT source and target — and what does it do that SLT's own latency/logging checks cannot?

The Cross-Database Comparison inconsistency-resolution report refuses to fix one of your tables. What table status is required, and why is that a hard prerequisite?

When resolving an inconsistency, if a record exists in the SLT source table but is missing from the target, which operations does the report allow on the target — and which does it explicitly forbid?

The Cross-Database Comparison runtime option "Update Logging Table without Performing Checks" is faster than the default "Do Not Update Logging Table if Record Key Exists." What must you guarantee before choosing the fast option?

You open the notification expert function via Transaction IUUC_REPL_EN and it asks you for something that you never had to supply when you reached the same function from the SLT Cockpit. What is it, and why the difference?

The SLT notification screen shows the message "Notifications are not active for mass transfer ID <MTID>". A colleague says the configuration itself has stopped replicating. Is that the right reading?

In the SLT notification checks, which specific check tells you that changes are reaching the target too slowly — as opposed to the check that tells you data is piling up unsent in the source?

The SLT Table Status Check does something beyond just reporting a table's status. What additional source-system fact does it verify?

For the SLT Connection Check, what is the default response-time threshold, and when would leaving it at default cause false connection-error alerts?

You set a latency error threshold at the configuration level, but one particularly hot table keeps firing errors even though its own latency is fine for its volume. Where do you override it, and which threshold wins?

On the SLT Email Recipients tab, why isn't it enough to just add someone's address — what decision do you make per recipient?

In SLT Job Settings, the default handling for long-running jobs is "Cancel Jobs After 24 Hours (and additional delay time)." What is the default additional delay time, and when would you deliberately switch to "Do Not Cancel Jobs"?