With SAP HANA, your ABAP developers need to rethink the way they code and move much more of the processing logic from the application layer to the database. This will allow them to take advantage of SAP HANA's new features such as CDS views, AMDP and native HANA SQL.
This does not mean that everything is processed by the database, but it opens up a new world of possibilities, e.g. database functions can be used in most cases so that the database can do the processing.
There are two main approaches to development for SAP HANA:
As of Release 7.5, code pushdown with ABAP is enabled for SAP HANA. This approach allows you to create new database views directly in ABAP. This object can then be used in SAP HANA, meaning your views and procedures are created for you in HANA as soon as they are called. This also improves lifecycle management and maintenance.
This approach is mostly considered with pre ABAP 7.4 releases. With this approach, we use new ABAP artifacts to consume HANA views and procedures. Although this is a viable solution, it comes with drawbacks as developers have to work in both worlds and requires much more effort to keep objects in sync.
SAP HANA offers many benefits, but the biggest and most tangible benefit is the significant performance increase.
Making your existing code from legacy systems compatible for SAP HANA often requires making changes to existing programs.
SAP offers a number of tools, including the Performance Worklist Tool, that can help you determine which programs need to be optimized and should be changed first. This is critical to achieving the desired performance improvement.
With the code-to-data paradigm, SAP HANA provides new and improved tools to drive your processing logic toward the database.
Here are some of those tools:
- SAP has removed many of the SQL limitations of its previous systems and offers a host of new features
- CDS views (Core Data Services) provide a much better and easier way to encapsulate your query logic in a user-friendly way and provides many features
- AMDP (ABAP-Managed Database Procedures) allow you to write your queries in a database-specific language, such as Native SQL or SQL script, and can be implemented in the body of an AMDP procedure, providing optimized database access