Which features prevent the SAP HANA-optimization of transformations in the SAP HANA database? (2)

Question

Options

• ATransfer routine on the characteristic level
• BABAP expert routine in the transformation
• CABAP end routine in the transformation
• DLookup master data in the transformation

• A
  10% (5)
• B
  83% (40)
• D
  6% (3)

Explanation

B (ABAP expert routine) and C (ABAP end routine) are correct because both contain custom ABAP code that must execute on the ABAP application server - they cannot be translated into SQL or pushed down to the SAP HANA database engine. SAP HANA optimization works by executing transformation logic directly inside the database; any step requiring the ABAP stack breaks that execution path and forces processing to leave the database layer.

A (Transfer routine on the characteristic level) is wrong because characteristic-level transfer routines are handled in a way that remains compatible with HANA optimization - they operate at a different scope and don't force ABAP stack execution in the same disruptive way.

D (Lookup master data) is wrong because master data resides within the SAP HANA database, so the lookup can be resolved natively as a database join, keeping everything inside HANA without breaking the optimization.

Memory tip: Think "ABAP = off to the App Server." Anything labeled "ABAP _____ routine" (expert, end, start) forces processing out of the HANA database and onto the ABAP stack - that's your blocker. If the operation stays native to the database (joins, lookups, characteristic rules), HANA optimization survives.

No community discussion yet for this question.