Higher, faster, further

All Abap applications and add-ons using Open SQL are database compatible, i.e. they run on different DB systems (MS-SQL, MaxDB, Oracle) and can therefore also be operated on Hana.

"Application server and DB server communicate via a database connection. All data required for the initiated command is loaded into the application server, where all computational operations and coding are then performed. This works the same way with traditional databases as it does with Hana"

but the disadvantage of this approach is obvious to Florian Lenz, Head of Departement Forecast at G.I.B.:

With large data volumes, there are long waiting times due to the data transfer between the database and the application server. But surely Hana was supposed to make everything faster?

"There can be performance gains without optimizations, but there doesn't have to be; after all, all essential computing operations continue to be done in the application server, and it remains the same"

explains Lenz.

When it comes to real-time analytics and more functionality, as much coding as possible needs to be done in Hana itself, he said.

But reprogram everything?

"The better the program uses the column-oriented database logic and the more statements are used from Hana and the more operations are performed on Hana, the faster the program"

says Lenz and adds:

"This comes at the expense of database compatibility."

For one of the programs from the G.I.B Dispo Cockpit family, he himself has chosen the middle way by providing all data transfer points with a switch.

"The program now recognizes whether it is based on a Hana or a conventional database. With a Hana, the program deviates from the 'normal' procedure and moves the coding to the Hana server."

This procedure, known as code push-down, holds enormous potential. Stefan Renk, head of SCM processes at lighting manufacturer Trilux, reported performance improvements of 90 percent in individual actions after just one week of live use of the G.I.B DCF on Hana add-on. Trilux is currently still working with a by-side solution; for Lenz, this is only an interim solution:

"The familiar ERP server with the existing database remains in operation. Only part of the data migrates to Hana and is kept up-to-date via the LT Replication Server."

Especially in the mobile application area, Hana opens up new dimensions. It is important to ensure that the result set is calculated as completely as possible in Hana, because mobile users expect results at the push of a button, even for mass data analyses. An appealing user interface is also part of this.

"It's a challenge to pick apart a complex application to create apps that make sense.

The identification of homogeneous user groups, the reduction of facts and processes to the essentials, and the courage to part with functions are fundamental processes in the design. These apps should be self-explanatory and lead to the goal in three to four steps. It is complicated to provide simplicity".

jokes Lenz.

Run simple

Simplification is also the keyword for S/4 Hana, the new era of the Business Suite. Unlike in the past, SAP no longer relies on database compatibility here:

"With S/4, the application and database are perfectly matched. Almost all coding should then be done in Hana, minimizing data transfer to the end device."

explains Lenz, adding that the interaction of Fiori, simplification and Hana opens up new performance dimensions. It should be noted that not only Abap knowledge is required on the developer side, but also additional skills in Javascript, SQL and SQL Script.

"With all the advantages, it must be noted: All S/4 Hana applications can only be operated with a Hana DB".

notes Lenz.