Replication to Cloud Applications

Why can't SAP LT Replication Server write directly to a flat file or a cloud application, so that a second tool like SAP Data Services or SAP Data Intelligence Cloud is always required?

You need real-time delta into a hyperscaler target and must pick between the SLT + SAP Data Services hybrid and the SLT + SAP Data Intelligence Cloud hybrid. Which one do you choose when the target is a native cloud application (e.g. Azure Data Lake Gen2)?

When the SOURCE system goes down during replication (either cloud hybrid), what is the recommended action to prevent SLT filling up with errors, and what is the data impact?

While SLT itself is down, source triggers keep firing. What is the second-order consequence you must watch on the SOURCE system?

This is the key outage discriminator for the cloud chapter: when the CONSUMER tool goes down (Data Services vs Data Intelligence Cloud), does the data stay safe?

Mechanically, how does Data Services know where to resume after it comes back from an outage?

In the SLT + Data Services scenario, how does Data Services actually get the delta data out of SLT?

When creating the SLT configuration in LTRC, what target-system scenario do you pick for the SAP Data Services path versus the SAP Data Intelligence Cloud path?

In the SLT + Data Services scenario, what is the queue alias for and what constraint does it carry?

What minimum SAP Data Intelligence Cloud version is required to connect to an on-premise ABAP system via the cloud connector gateway?

For an SAP source, what must exist before you create the SLT configuration, and in which transaction is it maintained?

For the SLT + Data Intelligence Cloud path, what component bridges the on-premise SLT system to the cloud tool, and why is it mandatory?

When exposing an S/4HANA ABAP system to SAP Data Intelligence Cloud through the cloud connector, which function-module names must you whitelist?

In the cloud connector for Data Intelligence Cloud, if you create the RFC connection with the Load Balancing option, what must match on the connection-management side?

From SAP Data Intelligence Cloud 2308 onward, when you configure an SNC RFC connection directly in connection management, what must the Gateway field be set to?

In the SLT source system, which role must the replication user have, regardless of whether the target is Data Services or Data Intelligence Cloud?

Beyond the standard SLT roles, what additional authorization prerequisite is specific to the Data Intelligence Cloud path and has no equivalent in the Data Services path?

In the ODP (Data Services) scenario, can you start and stop individual table replication from within SLT using LTRC?

In the Data Intelligence Cloud path, where do you actually trigger the table load and replication once the replication flow is deployed?

In the Data Intelligence Cloud replication flow, what does choosing Load Type "Initial Only" versus "Initial and Delta" decide?

Which connection type do you use in SAP Data Intelligence Cloud connection management to reach Azure Data Lake Storage Gen2 as the target?

In SAP Data Intelligence Cloud connection management, what tells the ABAP (source) connection to route through the cloud connector rather than reach the system directly?

Where is SAP Data Intelligence Cloud provisioned before you can use it as an SLT replication target?

Both cloud hybrids depend on SLT's trigger-based CDC. What differs in HOW the two tools consume those captured changes from SLT?

The initial data transfer from source to SLT is real-time, but the transfer from SLT onward to the flat-file target via Data Services runs in what mode, and what recurring task does that impose?

On the second and later runs of the Data Services flat-file job, what does the job do to the existing target file by default?

When SAP Data Intelligence Cloud is unavailable, where does the not-yet-consumed data sit in SLT, and why can it become inconsistent?

In the Data Intelligence Cloud path, when the TARGET (Azure) is down, how does the failure surface and how do you recover once Azure is back?

During initial load, what does a table's sequence number changing from 30 to 40 in the Data Transfer Monitor tell you?

How can you verify, from the SOURCE system, that SLT actually created the change-capture triggers for a replicated table?

SLT is described as "just one of several" SAP replication options. Given a real-time trigger-based need into a cloud/hyperscaler target, what makes the SLT hybrid the fit over SAP HANA smart data integration or SAP Replication Server?