...
A typical example of this CDS view type is the MSEG or MKPF view in S/4 HANA. These tables no longer exist as tables when it comes to availability in DDIC. SAP is covering the demand for backward compatibility by introducing so-called compatibility views. These are available in DDIC and share the structure of original ECC tables. However, in the definition of this view in SE11, you would notice, that the result is returned from the MATDOC table with certain filters applied. Important annotation here is @AbapCatalog.sqlViewName. When replicating CDS views of this type, the procedure is exactly the same as when replicating data from any other view that is available in DDIC. You can find the view in SE11 under the name of the @AbapCatalog.sqlViewName mentioned before. In this case, the fetcher type is the SAP table fetcher.
...
When consuming this query, you need to keep in mind remember the naming convention used within ABAP - the same as in SNP Glue. The resulting name consists of the concatenation of 2C and the name of the CDS view available within annotation @AbapCatalog.sqlViewName. Simply: 2C<@AbapCatalog.sqlViewName>
...
@Analytics.dataExtraction.enabled
Compatibility of ODP-enabled CDS can be verified by running a report RODPS_REPL_TEST in SE38, entering the CDS view name + respective data category, and executing a test data extract display.
The ODP Name equals the @AbapCatalog.sqlViewName and is suffixed by the data category classification @Analytics.dataCategory in the CDS view:
...