Explain HANA Data Provisioning: SLT, SDI & Smart Data Access in SAP

44 / 65

HANA DBintermediate

HANA Data Provisioning: SLT, SDI & Smart Data Access

Real-time and batch data replication techniques for feeding HANA from source SAP and non-SAP systems.

Data provisioning questions come up whenever an interview touches BW/4HANA, side-by-side HANA data marts, or any scenario where HANA needs data from elsewhere, and interviewers use it to check whether a candidate can pick the right replication technology for a given latency/complexity trade-off rather than reaching for one tool regardless of fit.

SLT is like a live news wire service continuously feeding fresh updates from an SAP source into HANA's newsroom as they happen; SDI is a general wire service that can pull stories from many different outside sources, not just SAP; Smart Data Access is picking up the phone and asking a remote correspondent for the story on demand each time you need it, rather than keeping any copy of it in your own newsroom at all.

Key Concepts

SAP Landscape Transformation Replication Server (SLT) is the standard trigger-based real-time replication technology for SAP ABAP source systems - it reads changes from the source system's database via triggers placed on the source tables (configured and monitored through transaction LTRC), captures inserts/updates/deletes with low latency, and replicates them into HANA target tables, commonly used to feed BW/4HANA or a side-by-side HANA reporting system directly from an ECC or S/4HANA source without waiting for a batch extraction window. SLT's trigger-based approach means it operates at the database level on the source and works well for ABAP-based sources where SAP has built specific integration, and it supports both initial full-load and ongoing delta replication in the same configured connection.

LTRC

SAP Data Services / Smart Data Integration (SDI) covers broader ETL and non-SAP source connectivity - SDI specifically provides HANA-native adapters (including a CDC - Change Data Capture - capability for compatible source databases) that let HANA pull data from a wide variety of non-SAP relational databases, flat files, and other sources directly, often used when the source isn't an SAP ABAP system SLT can target. Smart Data Access (SDA) takes a different, non-replicating approach entirely - it creates virtual tables in HANA that federate live queries out to a remote source system at query time rather than copying data into HANA at all, useful when a small amount of infrequently-queried remote data doesn't justify the complexity of a full replication setup, though at the cost of query performance being bounded by the remote system's own responsiveness.

A senior-level answer frames the choice explicitly: SLT for real-time replication from ABAP/SAP sources with low latency requirements, SDI for broader ETL/non-SAP connectivity and batch or CDC-based ingestion, and SDA when avoiding data duplication matters more than query speed and the data is queried rarely enough that federated live access is acceptable - and notes these techniques are frequently combined within one landscape (e.g., SLT feeding the bulk of BW/4HANA's real-time data while SDA federates one rarely-used external reference table without a full replication pipeline).