What happens in SAP BW/4HANA when the "Trigger Delta Merge" process variant runs for a given data target in a Process Chain? Please choose the correct answer.

Question

Options

• AThe delta between the new data and the already loaded data is calculated in a DataStore object
• BOnly data from the delta queue is extracted and merged into the SAP BW/4HANA data target.
• CData is transferred from the delta store to the main store of a column-store table in SAP HANA.
• DThe before and after images of the delta queue are merged and sent to the SAP BW/4HANA

• A
  7% (1)
• B
  14% (2)
• C
  71% (10)
• D
  7% (1)

Explanation

"Trigger Delta Merge" refers to an SAP HANA internal storage operation: SAP HANA's column-store tables use a two-tier structure where incoming data lands in a write-optimized delta store first, and the delta merge process physically moves that data into the read-optimized main store - making C correct. Option A is wrong because delta calculation in a DataStore object (DSO) is a BW-layer concept about identifying changed records between load requests, which is entirely separate from HANA's storage engine. Option B is wrong because it conflates this with BW delta extraction (pulling changed data from a source system's delta queue), which is a different process chain step altogether. Option D is wrong because before/after image processing describes change-data-capture replication mechanics, not what happens inside HANA's storage layer during a merge.

Memory tip: The word "delta" appears in multiple SAP contexts - the key here is that Trigger Delta Merge lives at the HANA database level, not the BW extraction level. Think of it as a storage housekeeping job: data moves from the write-fast zone (delta store) to the read-fast zone (main store). If the answer is about column-store tables and HANA internals, you're on the right track.

No community discussion yet for this question.