Skip to Content

SDA vs EIM vs BODS vs SLT

Hi All,

Would like to know your opinions on different data provisioning options to HANA enterprise.

It would be great if you could answer these questions individually.

1. For real-time replication from SAP ECC systems, as of today would SDI have the ability to replace SLT?

2. SDI and SDQ which I assume comes under SAP EIM would require separate licensing whereas SLT license is already included within the enterprise HANA licensing. Is this true?

3. Can Smart data Access be used without SDI and SDQ? If I want to use it just as a data provisioning method without having any transformations to it. Similar to what SLT does.. just with virtual tables instead. In this case, would the customer need SDA just for the data provisioning?

4. Can SDI and SDQ (EIM) replace SLT/BODS today or in the near term future? I know it's part of the future roadmap but would you propose this as a solution instead of SLT for an ECC real-time replication need?

5. BODS vs SLT . My personal experience says SLT should be the preferred data provisioning solution at least for the SAP source systems when compared to BODS. Has anyone switched to BODS in such a need instead? If yes, why?

I would request replies assuming these solutions were to be given to a client for the near term future. I know future road maps promise a lot but not each component is mature yet to be proposed everywhere.

Waiting for answers and a healthy discussion.

Regards,

Shyam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Nov 11, 2016 at 04:42 AM

    Hi Shyam,

    1. SDI can do real time replication from ECC systems running on ASE, DB2, Oracle and SQL Server. Please have a look at the SDI PAM for details on supported versions.

    2. SDI is included with HANA Enterprise, SDQ is not.

    3. SDA is for virtualized access to data from external systems. It should not be used to transfer data into HANA.

    4. SDI and SDQ won't replace SLT or BODS. This is not on any roadmap and there are no plans for this.

    Which one to use depends on the requirements. For real time replication from ECC both SDI and SLT can be used. For SDI, please have a look at the SDI PAM to make sure the underlying database is supported.

    5. They shouldn't be compared because they don't serve the same purpose. BODS is an ETL tool. It can't detect changes in real time from a data source so it can't be used for real time replication. SLT is a real time replication tool but doesn't have the data transformation and data quality capabilities that BODS has.

    Best Regards,

    Richard

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 19, 2016 at 08:11 AM

    Hi Shyam

    1. For real-time replication from SAP ECC systems, as of today would SDI have the ability to replace SLT?

    Ans : SDI is not meant for replication. Its another ETL tool in built in SAP S/4 HANA box

    2. SDI and SDQ which I assume comes under SAP EIM would require separate licensing whereas SLT license is already included within the enterprise HANA licensing. Is this true?

    Ans: SDI is only free. SDQ is NOT free with Enterprise license

    3. Can Smart data Access be used without SDI and SDQ? If I want to use it just as a data provisioning method without having any transformations to it. Similar to what SLT does.. just with virtual tables instead. In this case, would the customer need SDA just for the data provisioning?

    Ans: I did not understand your question. But still SDI you can use like your SAP DS to some extend NOT full functionality still SAP is working to bring all the features from Data Service to SDI in the future. Don't compare SLT with SDI both are different purpose.

    4. Can SDI and SDQ (EIM) replace SLT/BODS today or in the near term future? I know it's part of the future roadmap but would you propose this as a solution instead of SLT for an ECC real-time replication need?

    Ans: This point i cannot answer only SAP can reply.

    5. BODS vs SLT . My personal experience says SLT should be the preferred data provisioning solution at least for the SAP source systems when compared to BODS. Has anyone switched to BODS in such a need instead? If yes, why?

    Ans: SAP DS ( Aka BODS) is a ETL tool for which can connect to any source like oracle, SQL server, Teradata, DB2 etc. and can do complex data transformation and load data via IDOC or BAPI or RFC FM. Where as SLT cannot do complex transformation easily, extraction cannot done for variety of source system and loading of data direct table update. Don't comparing both these tools. Both these tools are meant for different purposes.

    For any further queries contact the SAP directly for selection of tools and usage. Talk to your max attention team from SAP. They can help you much better than us.

    Thanks and Regards

    Vijay

    Add comment
    10|10000 characters needed characters exceeded