Qlik Replicate SAP ODP CDS View not processing Updates done in SAP

[Bill_Steinagle]

When replicating a CDS View the Updates are being processed as Inserts not Updates. In SAP the CDS views delta with UPSERT and SAP capture INSERT and UPDATE both as one operation which is treated as INSERT.

If you have a SAP login you can look up SAP Note 3300238 for more information as shown below:

SAP Note 3300238 - ABAP CDS CDC: ODQ_CHANGEMODE not showing proper status forcreation
Component: BW-WHM-DBA-ODA (SAP Business Warehouse > Data Warehouse Management > Data Basis >Operational Data Provider for ABAP CDS, HANA & BW), Version: 4, Released On: 19.01.2024

Resolution

This is working as expected. It is the designed behavior of the CDC logic. For both insert and update, ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1.

The CDC-delta logic is designed as UPSERT-logic. This means a DB-INSERT (or create) or a DB-UPDATE both get the ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1. It's not possible to distinguish in CDC-delta between Create and Update.

Environment

Qlik Replicate  
SAP S/4HANA
SAP BW/4HANA

[amanda2369weaver]

In Qlik Replicate, when dealing with SAP CDS views using ODP (Operational Data Provisioning) and encountering an issue where updates are being processed as inserts, there are a few key points to consider based on the information provided and the behavior described in SAP Note 3300238.

In SAP, the Change Data Capture (CDC) delta logic for CDS views treats both inserts and updates as a single operation (UPSERT). This means both operations are marked with ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1.

This behavior makes it challenging to distinguish between insert and update operations directly.

Example Task Configuration Snippet

---

@Bill_Steinagle wrote:

When replicating a CDS View the Updates are being processed as Inserts not Updates. In SAP the CDS views delta with UPSERT and SAP capture INSERT and UPDATE both as one operation which is treated as INSERT.

If you have a SAP login you can look up SAP Note 3300238 for more information as shown below:

SAP Note 3300238 - ABAP CDS CDC: ODQ_CHANGEMODE not showing proper status forcreation
Component: BW-WHM-DBA-ODA (SAP Business Warehouse > Data Warehouse Management > Data Basis >Operational Data Provider for ABAP CDS, HANA & BW), Version: 4, Released On: 19.01.2024

Resolution

This is working as expected. It is the designed behavior of the CDC logic. For both insert and update, ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1.

The CDC-delta logic is designed as UPSERT-logic. This means a DB-INSERT (or create) or a DB-UPDATE both get the ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1. It's not possible to distinguish in CDC-delta between Create and Update.

Environment

Qlik Replicate 
SAP S/4HANA
SAP BW/4HANA

---

Example Task Configuration Snippet

{
"source": {
"type": "SAP_ODP",
"settings": {
"cdcMode": "UPSERT",
"primaryKey": "YOUR_PRIMARY_KEY"
}
},
"target": {
"type": "YOUR_TARGET_TYPE",
"settings": {
"applyMode": "UPSERT"
}
},
"transformations": [
{
"name": "HandleUpserts",
"type": "UPSERT",
"conditions": {
"sourceField": "ODQ_CHANGEMODE",
"value": "U"
}
}
]
}