SLT Fundamentals & Architecture

SLT can filter data during replication — what three granularities of exclusion does it support, and why does that change a design decision?

In the SLT T-shirt sizing template, roughly what expected throughput separates a Small landscape from a Large one?

What underlying data-capture mechanism does SLT use to detect changes in a source table, and why does that choice matter operationally?

During the SLT initial load, does the source system have to be taken offline or locked for the tables being loaded?

If the target SAP HANA system goes down temporarily during replication, what happens to the ongoing data changes in the source, and what is the risk?

In the SLT data-transfer flow, what triggers deletion of a delta record from the source logging table?

For an ABAP source system, where do the read modules that extract application-table data actually run?

How does the connection type between SLT and the source differ for an ABAP source versus a non-ABAP source?

Which add-on must be installed on an ABAP source system for it to connect to SLT, and on what stack must the SLT server itself be based?

SLT and SAP Replication Server are both real-time replication tools — which one should you choose for trigger-based replication into SAP HANA from mixed SAP/non-SAP sources?

You need near-real-time replication from SAP source systems using a standardized provisioning framework rather than table-level triggers — which SAP tool fits?

When SLT replicates into an SAP BW target, what intermediate mechanism does the data pass through inside SLT?

In an ABAP-to-ABAP SLT scenario, what must you ensure about the target table before starting the load/replication?

In an ABAP-to-ABAP replication, what connection type links SLT to the target system?

Which SLT deployment option does SAP recommend, and what problem does it specifically avoid?

If you deploy SLT embedded inside the source system to save on hardware, what is the operational cost you are accepting?

What is technically true about running ALL replications in a landscape from a single central SLT instance?

When replicating from multiple source systems into one SAP HANA database, how does SLT keep the data sets separate?

Which SLT report do you run to estimate sizing, and what prerequisite gates its availability on the source?

When you run the SLT sizing analysis, what must the Collect Statistics checkbox state be, and why?

In SLT sizing, how do the number of data-transfer jobs scale across the Small, Medium, and Large T-shirt bands?

Technically, what kind of software component is SLT within the SAP stack?

Which transaction installs the DMIS add-on for SLT, and don't confuse it with the runtime configuration transaction?

The book lists SLT for S/4HANA 1.0 as DMIS 2020, and SLT 3.0 as DMIS 2018 — what does mixing up these version pairs cost you?

What is the fundamental difference between SLT's initial load phase and its replication (delta) phase?

During the SLT data-transfer flow, at what point does the target SAP HANA engine perform its commit?