Symptom
You have defined CDS View as following and want to load it to Datasphere via Replication Flow:
@Analytics.dataExtraction.delta.byElement.name:'updated_timestamp'
@Analytics.dataExtraction.delta.byElement.maxDelayInSeconds : xxxx
@Analytics.dataExtraction.delta.byElement.detectDeletedRecords: true
@Analytics: {
dataCategory: #FACT,
dataExtraction: {
enabled: true,
delta.changeDataCapture:
Environment
- SAP Datasphere
- Replication Flow Runtime
Reproducing the Issue
- Configure the replication flow from S/4HANA to Datasphere using the specified CDS Views.
- Attempt to execute the initial load and delta replication process.
- Observe the error messages in the application log related to subscription interface and reconstruction metadata.
Cause
- The CDS View inconsistency caused by the use of two delta mechanisms: Generic Timestamp/Date-based logic and Change Data Capture (CDC) logic within the same CDS View.
Resolution
There are two delta mechanisms for CDS based delta extraction: Generic Timestamp/Date based Delta and Change Data Capture (CDC) Delta.
You can use either generic delta or CDC delta to extract delta data but you cannot use both of them in one CDS View.
Please refer to blog:
CDS based data extraction - Part II Delta Handling
The solution is to modify the CDS View and keep only one method for delta load.
See Also
Keywords
replication flow, datasphere, s/4hana, CDS views, delta replication, initial load, inconsistency, generic timestamp, change data capture, CDC, note analyzer, SAP datasphere, ABAP integration, replication flow issue, Delta logic. , KBA , DS-DI-RF , Replication Flow Runtime , Problem
SAP Knowledge Base Article - Public