With SLT you can perform CDC by using Replication option, but it does not maintain history in your target.
Sap bods 4.1 software update#
It allows systems to bring only the latest changes on the data (after any insert, update or delete is triggered on the table) after the initial load. This is where the concept of CDC is used to determine or track the changed data and perform actions on the same. With any data warehouse implementation, maintaining history of the data is the key business requirement along with the need for data analysis, but at the same time we do not need to bring the entire source data into the target every day. With SDI being available as part of SAP HANA, it can have only HANA database (including cloud) as its target. Even though the most preferred scenario for SLT is loading into SAP HANA, it can still be used to load data into other RDBMS targets. SAP BODS can load data into various target systems including flat files. Big Data integration is now available with BODS and it can connect to HDFS.
Sap bods 4.1 software software#
SDI can also integrate well with Big Data software like Hadoop through HDFS system. SDI, with the help of SDA (smart data access adapters), can connect to a lot of traditional RDBMS and unstructured data sources like Twitter, Facebook etc. SAP BODS can connect to a variety of legacy systems (Like IBM, AS400) along with the traditional RDBMS as the source. It can also be used for a quite a few non-SAP systems like Oracle, DB2 etc. This does not mean that SLT can only be used for SAP source systems.
![Sap bods 4.1 software Sap bods 4.1 software](https://i.ytimg.com/vi/4zuzkr_NjxY/maxresdefault.jpg)
The best use case scenario for SLT has always been connecting from SAP ECC to HANA in a side car implementation. In other words, SLT is more suited for data replication than transformation. SLT, on the other hand, has very minimal transformation options that can be done only through ABAP. While the tool as such has a long way to go, it may acquire new transform options with each release. Nevertheless, SDI comes second with almost equal number of transform options available to integrate and cleanse data. When it comes to transforming, cleaning and integrating data, SAP BODS wins hands down as it offers a wide variety of data integration and data quality transform options. Note that real-time replication with SDI is not applicable for all data sources 2. On the other hand, SLT and SDI have the capability to do near-real-time data replication with SDI having an option to execute even in batch mode.
![Sap bods 4.1 software Sap bods 4.1 software](https://blogs.sap.com/wp-content/uploads/2019/12/Capture-41.png)
SAP BODS, a complete ETL tool, supports data replication in batch mode, but real-time replication is limited to web services. Data Replicationĭata replication is a basic feature that is expected from all data provisioning tools.
![Sap bods 4.1 software Sap bods 4.1 software](https://blogs.sap.com/wp-content/uploads/2013/12/9__cms_342631.png)
To start with, let us compare the SAP Data Services (BODS), SAP Landscape Transformation (SLT) and SAP HANA Smart Data Integration (SDI) from the following perspectives:Ī summary of the analysis is shown herewith, followed by more details below. In this blog series, we will be looking at various features and business scenarios and which of the data provisioning tools from SAP best fits in.
![Sap bods 4.1 software Sap bods 4.1 software](https://3.bp.blogspot.com/-7ETkjw3B2z4/U1UES3j4mRI/AAAAAAAAN7g/VJgOOxZy8mo/s1600/PHR1.jpg)