Replication to Cloud Applications

Data leaves SLT via ODQ/ODQMON in the Data Services scenario, but in the SAP Data Intelligence Cloud scenario, where does the cloud writer pull the data from inside SLT?

What minimum SAP Data Services release lets it consume SLT's real-time changes through the ODP framework?

To subscribe SAP Data Services to SLT's changes, what must you enter in the Data Services datastore besides pointing it at the SLT system?

When you create the SLT configuration for a cloud replication that goes through SAP Data Intelligence Cloud, which target system scenario do you choose?

When you build a replication flow in DI Cloud, what do you select as the Source Container, and where does that value come from?

When configuring the cloud-connector connection for DI Cloud replication, what authentication method is used and which field must be left blank?

A replication-flow table offers a Load Type of Initial and Delta or Initial Only. What does choosing Initial Only cost you?

By default, each subsequent Data Services job run to a flat-file target treats the existing file how, and what breaks if you assumed it appends?

SLT captures source changes in real time, so what actually determines how fresh the data is in the cloud/flat-file target in the Data Services scenario?

Beyond just being able to reach a target SLT can't write to, what does routing through SAP Data Services add that pure SLT replication cannot do?

For delta files in a DI Cloud replication flow, choosing a compression type is a trade-off — what are you actually balancing?

What are the four main configuration steps to replicate from an SAP source to a cloud application (e.g. Azure ADLS Gen2) using SLT and DI Cloud?

The book lists only SAP_IUUC_REPL_REMOTE for the source RFC user in cloud replication. What extra role does an SAP S/4HANA on-premise source (release 2020+) actually require?

What must you expose in the cloud connector, and how, so SAP Data Intelligence Cloud can reach an on-premise ABAP source system?

For loading data to a cloud application via DI Cloud, which authorization roles are needed in the source system versus in SLT, and what else must be reachable?

In DI Cloud Connection Management, which connection type do you use to reach an Azure Data Lake Storage Gen2 target?

When replicating to a flat file or a cloud application, why can't you just point SAP LT Replication Server directly at the target the way you would for a HANA or BW target?