Replication to SAP BW / BW-4HANA

For loading data into SAP BW/4HANA with SLT, which replication scenario applies and which is ruled out?

In the PSA-based SLT-to-BW scenario, which table types can and cannot be replicated?

Why should you avoid the persistent staging area SLT-to-BW scenario for any new development?

Data is piling up in the ODP system for a BW subscriber whose target is unavailable — how do you end it via ODQMON?

When the target SAP BW system is down in an ODP scenario, what happens to the in-flight data?

In the ODP scenario, once SLT writes delta to the ODP framework, who owns getting it into BW — and what's the risk?

In the three-setup-options list, does the label 'SAP BW' include SAP BW/4HANA?

In ODP RecordMode logic, what does ODQ_CHANGEMODE = D with ODQ_ENTITYCNTR = -1 map to versus D with 0?

In ODP RecordMode logic, how are ODQ_CHANGEMODE = C/1 and U/-1 interpreted?

When creating the receiving aDSO for SLT deltas, which option should you enable and why?

After the first delta arrives via a manually executed DTP, why is this not yet true real-time sourcing?

Which BW/4HANA feature turns the SLT ODP pipeline into hands-off real-time loading, and how is it controlled?

In the LTRC configuration wizard, how do you designate an ODP/BW target instead of a database or RFC target?

What minimum source-system NetWeaver release does the SLT-to-BW ODP scenario require, and what about older sources?

What core problem does the ODP framework's 'extract once, deploy many' concept solve for BW sourcing?

How do you cross-check that the initial load into the aDSO is complete and correct?

Roughly what fraction of standard SAP BW DataSources can deliver delta data natively, and how does SLT change that?

In the ODP architecture, what is the difference between a provider and a subscriber, and where does SLT sit?

What are the format and uniqueness constraints on the SLT queue alias used as the ODP context?

When SLT loads to BW via ODP, where is transferred data persisted, and by which system?

Setup option 1 for SLT-to-BW: what is the injection mode and the minimum release?

Setup option 2 for SLT-to-BW: what makes it different and what release does it need?

Setup option 3 for SLT-to-BW: what is its distinguishing mechanism and supported releases?

With SAP BW/4HANA specifically, which of the three SLT setup options are supported?

What is the default retention period for data held in an operational delta queue, and why does it matter?

When is SLT-to-BW the wrong choice compared to standard SAP extractors?

What links the SLT configuration to the SAP BW subscriber in an ODP replication setup?

Can you run SLT-to-BW replication without an initial load, and add the initial load later?

Fundamentally, what distinguishes the three SLT-to-BW setup options from one another?

In the SLT system, which role lets a user create or modify an LTRC configuration versus only view it?

Which role is granted on the SAP BW side (not SLT) to run the data provisioning process?

Which role enables the SAP BW system to subscribe to the ODP framework, and where is it assigned?

Which role must the RFC user carry on the connection from the source system into the SLT system?

When the source or target sits in the same system as SLT, what shortcut replaces a normal RFC destination?

For the ODP-SLT Queue logical system in BW, which two authorization profiles must the callback-connection user hold?

Why might the ODP target option not appear under 'Other' on some SLT systems, and what do you do?

In Specify Transfer Settings, when do you pick Resource Optimized over Performance Optimized for the initial load?

In how many configurations can one source system be reused, and which option enables it?

The BAdI activation step for ODP usage in SLT — for which configurations is it required?

In an SLT-to-BW ODP setup, which system leads the replication and where are the tables actually selected?

Where do you create the logical system for an ODP source in modern SAP BW, and what is deprecated?

After creating the ODP source system in BW but before setting the ODP context, where does it appear in the tree?

Which four BW objects must you create to receive SLT-replicated data via ODP?

What does choosing 'Proposal from Operational Data Provider' do when creating the BW DataSource?

In the BW DataSource Extraction tab, what is prefilled and why does that confirm the ODP wiring?

What Delta Process is autoselected for an SLT ODP DataSource, and what capability does it imply?

Two extra fields appear on an SLT ODP DataSource that aren't in the source table — which, and what do they carry?

Why is an intermediate aDSO layer needed for SLT ODP data rather than loading straight to an InfoCube?

Which NetWeaver release first ships the ODP framework as a standard component?

What does the No. of Calculation Jobs setting do differently across SLT reading types?

How does the ODP scenario move data into SAP BW differently from the older PSA scenario?