You want to load a customer table to SAP BW/4HANA in delta mode. The customer table is managed in SAP S/4HANA Cloud. Each record has a UTC time stamp. What is the recommended approach to implement…

Question

Options

• ACreate a customer DataSource (TC RSO2) that leverages the generic delta based on the time
• BCreate an ABAP CDS View that leverages a procedure to generate the delta based on the time
• CCreate an ABAP CDS View that is enabled for extraction and generates the delta based on the
• DCreate an ABAP CDS View that is enabled for extraction and model the Change Delta Capture

• A
  19% (4)
• B
  5% (1)
• C
  5% (1)
• D
  71% (15)

Explanation

Option D is correct because SAP S/4HANA Cloud supports ABAP CDS Views with the @Analytics.dataExtraction annotation family, and Change Data Capture (CDC) is the recommended delta mechanism - it tracks row-level changes directly at the database layer, making it reliable and independent of application-level timestamp maintenance. Option A is wrong because transaction RSO2 is an on-premise tool for creating generic DataSources; S/4HANA Cloud's restricted ABAP environment does not support this approach. Option B is wrong because calling a custom procedure to generate delta logic is not supported in S/4HANA Cloud's ABAP programming model, which restricts low-level procedural extensions. Option C is tempting but incorrect - although it uses a CDS View with extraction enabled, relying on a UTC timestamp for delta (time-stamp-based delta) is less reliable than CDC because missed or out-of-order timestamps can cause data loss, and SAP's recommended pattern for S/4HANA Cloud is explicitly CDC-based.

Memory tip: "In the Cloud, Change Delta Capture is king." Whenever the source is S/4HANA Cloud, think CDC over timestamps - timestamps belong to generic on-premise DataSources (RSO2), not to the modern CDS extraction model.

No community discussion yet for this question.