SAP / SAP Mid Level (3 to 8 yrs) Interview questions
Explain the concept of code pushdown in CDS Views?
A CDS View's logic — joins, filters, calculated fields, aggregations — is compiled into an actual database view, meaning when an application queries it via Open SQL, that entire logic executes inside HANA's engine, not in the ABAP application layer. The application only receives the final, already-processed result set.
define view Z_SalesSummary as select from sales_transactions { region, sum( amount ) as TotalAmount } group by region " ABAP code just selects the already-aggregated result: SELECT * FROM z_salessummary INTO TABLE @DATA(lt_summary). " the SUM/GROUP BY logic ran inside HANA, not in this ABAP loop
This is the concrete mechanism behind the "push logic to the data" principle discussed elsewhere: rather than an ABAP program fetching raw rows and computing the sum itself in a loop, the CDS View's definition ensures that computation happens where the data lives, and only the small, final result crosses the boundary back to the application layer.
Where does a CDS View's join/aggregation logic actually execute?
What does the ABAP layer receive when querying a CDS View that performs aggregation?
More Related questions...
