Replication Scenarios, Sizing & Deployment

For a non-ABAP (third-party database) source, where do the read modules that extract data from the application tables run, and how does the source connect to SLT?

In an ABAP-to-ABAP replication configuration, what must be true about the target table before you start the load or replication?

What is architecturally distinctive about how SLT stages data when the target is an SAP BW system?

The ABAP/non-ABAP to SAP S/4HANA replication scenario in SLT is centered on which specific business capability?

You have downloaded the DMIS software from SAP. Which transaction installs the DMIS add-on onto the NetWeaver stack?

Can a single central SLT server realistically serve an entire landscape, and what real-world scale backs that up?

When SAP HANA is the target, SLT offers four replication layout options. What actually decides which one you choose?

For a table of master data that rarely changes, should you use Start Load or Start Replication in SLT, and why?

When a row is deleted in the source, what does SLT's delete trigger write to the logging table, and from which row image?

You need SLT to feed data toward cloud object stores like Amazon S3, Azure, or Google Cloud Platform. Which target scenario is that, and what was it formerly called?

Which SLT report gives you table-level sizing figures for a replication project, and how do you obtain it if the DMIS add-on is not yet on the source?

In SLT's template (T-shirt) sizing, what do the Small / Medium / Large tiers imply for number of source systems, number of tables, and expected throughput?

How many data transfer jobs does SLT's template sizing allocate on the SLT server for the Small, Medium, and Large tiers?

Why is installing SLT as part of the SAP source system generally discouraged even though it is technically valid?

Which SLT deployment option is the most recommended, and what two independence benefits drive that recommendation?

What is the specific risk of deploying SLT as part of the target SAP instance?