Best Approach from CDC on CDS Views - Data Intelligence

[cfpereira5]

Hi All,

We are starting a new Project that will connect CDS Views to third parties using Fata Intelligence.

We expect to have a CDC process to retrieve data as it changes to third parties ( S3 and in soms cases Datashpere ).

We know that we can stabilish CDC on CDS Viewa by Annotations, and we still have the option to use SLT to replicate the data ( inside DI ).

In this scenario, wich would be the best approach ? Use directly CDC on CDS Views and DI or use SLT to replicate the data from CDS Views ?

Regards,

Cristian

[jimgiffin]

The Data Intelligence central note (https://me.sap.com/notes/2890171) provides good guidance on this topic:

In SAP Data Intelligence, we recommend that you use the different approaches for replicating data in the order listed below. You should only use a subsequent option if you either need to customize the data transfer in a more detailed way, or if the target system is not yet supported by one of the previous approaches.

1. Replication Flows
2. Data Intelligence Graphs using Generation 2 Operators
3. Data Intelligence Graphs using Generation 1 Operators

Based on the different data sources, you may also have different options for replicating the data. The following recommendations apply:

1. If your source system is an SAP S/4HANA system offering the needed data by means of CDS views, directly connecting SAP Data Intelligence to this source system and using the respective CDS views is the best approach.
2. If the source system does not use CDS views, you may have the option to directly access the tables that store the data or there may be options to use objects provided by the ODP framework.

1. For ODP objects, directly connect SAP Data Intelligence to the source system that contains the add-on DMIS 2020, DMIS 2018, or DMIS 2011. In case you are connecting to an SAP S/4HANA system (we recommend using CDS Views instead of ODP when possible) the available functionality for accessing ODP may be limited depending on the S/4HANA version.
2. For tables, the recommended approach is to access the source by using a standalone SAP LT Replication Server system using SAP LT Replication Server for SAP S/4HANA 1.0 (addon DMIS 2020) or SAP LT Replication Server 3.0 (addon DMIS 2018).
   While technically possible, it is not recommended to use SAP LT Replication Server as part of an SAP S/4HANA system or with the version SAP LT Replication Server 2.0 (addon DMIS 2011).
   The reasons for this are as follows:
   - The SAP LT Replication Server version embedded in SAP S/4HANA cannot be upgraded independently of SAP S/4HANA. This means that if new functionality is needed, an upgrade of the whole SAP S/4HANA system is required. Due to different dependencies, it is also not possible to downport new functionality to older SAP S/4HANA versions.
   - SAP LT Replication Server 2.0 is not recommended as it still uses SAP NetWeaver 7.00 as the basis component. This version lacks important features of later ABAP versions for a stable connection and the full feature support for SAP Data Intelligence. SAP LT Replication Sever 2.0 is therefore no longer updated with new functionality like RMS or support for Generation 2 operators.

Adding my a few more thoughts:

The CDS option provides business object data which requires less remodeling in downstream lakes and also does not require the SLT server.

SLT provides tables which means you have to redo the business logic in your target system.

Based on your use case, either or both options might be relevant for your needs.