SAP has partially redefined the ERP data model of the ERP with the introduction of S/4HANA. Certain Certain objects , such as CDS Compatibility Views, compatibility views have been introduced to ensure backwards compatibility of some core legacy processes, for example, such as transactions, reports and APIs. Some examples can be found You can find some examples in the SAP note 2595627.
Important: It is important to distinguish between CDS views and CDS compatibility views. This article focuses on CDS compatibility views only.
Let’s take a look at This chapter examines what compatibility views mean from the perspective of data replication and, in particular, replication by SNP Glue. We You will need to consider multiple aspects.
...
In many cases, compatibility views are unions and/or joins between the “old” old ECC tables (no longer accessible to the Netweaver NetWeaver layer) and “new” new S/4HANA tables which are actively used in the S/4HANA ERP. Is there any data in the compatibility view? Of course.
Is there any data in the original table? Maybe. Static? Mostly, Is it static? Mostly – usually leftovers from the S/4HANA upgrade.
2.
...
Are the views easy to handle? (complexity)
As with any good technical question, the answer is “sometimes.” Some CDS Compatibility Views compatibility views are quite easy to work with. For For example, the CDS Compatibility View compatibility view MSEG is just a selection from MATDOC with a few where WHERE conditions. It It only has a single layer, and replication is easily handled. In In SNP Glue, you can source the data from MSEG (as a view) and deploy the trigger on MATDOC to provide CDC.
Other CDS Compatibility Views compatibility views are extremely complex, consisting of many layers, and can include many underlying SAP tables. CDC CDC is quite difficult to implement in this scenario.
Examples:
...
3. How
...
can I find out?
To Proceed as follows to check if the underlying object you are trying to access is a compatibility view, go to SE16N and :
Start transaction SE16N.
In the Table field, enter the table name
...
.
Press Enter.
You will see the
...
Proxy Object field populated, which indicates a replacement object is used instead of a table directly.
...
Double-click
...
the proxy object
...
to navigate to transaction SE11.
...
Double-click the data definition to view the logic behind the compatibility view.
...
Example:
...
4. Progress or regression? (data modelling)
You have just implemented the newest and the latest innovations from SAP. It S/4HANA heavily simplifies the data model (besides other reasons, such as simplifying reporting and data modelling). Relying as well as reporting functions. Relying on old structures in your target platform means actively increasing your architectural debt.
Summary
In the majority of the most cases, there will be no data changes on are made to the original tables, and therefore no delta coming inis required. For some of these objects (see point 2 above), it is even impossible to define a reliable delta mechanism , which that would capture all changes and deliver the data in a an “at least once” fashion. Considering the differences between the data model models of ECC and S/4HANA, investment into the S/4HANA migration should also count with include adjustments in the reporting layer. Considering all points mentioned, in general
In summary, the SNP recommendation is generally to avoid data replication from CDS compatibility views , unless it is necessary. If it is necessary, SNP recommends only Full full loads for this purpose for smaller (tables, e.g. Master master data ) tables.