Preparations for the Hana trip

Experience shows: In the context of ERP, Hana tends to help in special scenarios that can be accelerated by in-memory technology. This includes both classic applications such as profit and loss and market segment accounting or logistics information systems as well as long-running processes such as payroll accounting in HR or material requirements planning.

Some of the modules and processes for Hana currently need to be optimized. SAP is beginning a complete overhaul of other applications. The first in a series of so-called S-Innovations is SAP Simple Finance. Further Hana-based solutions are planned.

This is different in the business warehouse sector. A simple 1:1 migration from a classic database to Hana can significantly improve performance. Of course, this does not automatically convert a poor data model into a good, efficient one.

A migration can be a first, simple step towards achieving "quick wins" in terms of performance and system operation. However, it should always be combined with accompanying projects - from housekeeping, data management (nearline storage or smart data access) and code optimization to system monitoring or alerting. Simply migrating to Hana is a good first step, but it is a long way from realizing the available potential.

There is no doubt that Hana is a big hit, but it is "only" a database. If the data modeling is not optimal, this can also reduce the performance of Hana. In some cases, the platform even works more slowly than the previous "classic" database.

The reason for this is that SAP systems used to place a lot of workload on the application servers, which is why the programs are designed for this. If the SAP systems now run completely on Hana in order to exploit the speed of the in-memory technology, it is advisable to adapt the data modeling and, if necessary, the Abap code.

Simple operation as a database

Hana is actually easy to operate in practice as a data warehouse, for example as a replacement for a conventional database. Neither a large number of special engines nor Hana Studio are required.

All SAP customers can benefit from the advantages, particularly with regard to speed and the associated flexibility in reporting, especially in the BW environment.

The myth of an "expensive migration to Hana" is unfounded. In practice, however, SAP user companies usually combine migration projects with other, long overdue projects.

The classics are system consolidations, harmonizations, upgrades, archiving/NLS, Unicode conversions, outsourcing or process changes. Due to such integrated projects, migrations to Hana are mistakenly perceived as lengthy, expensive and difficult to manage.

On demand or on premise?

SAP user companies can use Hana both on demand and on premise. Even in the on-premise version, companies can operate the technology at a reasonable cost.

They benefit from the fact that they can control Hana better and gain valuable experience. For other companies, the on-demand alternative is more suitable. You should check the contract, including the agreed service level agreements.

Introducing Hana and carrying out a migration definitely requires a little more than simply migrating the operating system or database.

With in-memory technology, the data model and system operation must be adapted to make the system fit for the future.

Do not migrate all data

Hardware and software costs are the biggest challenge for companies when it comes to implementation. In addition, the amount of data is constantly growing, while its value is decreasing at the same time.

The key here is the elective system migration to Hana. This not only enables an uncomplicated introduction, but also a reduction in system size, improved loading performance and a reduction in operating costs.

Instead of simply copying the entire system, an empty system is created based on the data model of the productive system - but without transaction data or master data.

Data is migrated to the new Hana system according to predefined selection criteria such as time or organizational criteria. The business-critical data remains accessible at all times and in real time.

At the same time, the total cost of ownership (TCO) can be reduced, as only relevant data is migrated and the entire SAP landscape is simplified.

Effective Hana sizing

There are various options for hardware sizing of the Hana appliance in the "non-Hana" environment:

• Hana Sizing with QuickSizer Tool - a web-based tool that can be executed via the SAP Service Marketplace
  Hana Sizing with DB-specific Scripts - Download via SAP Note 1637145 - SAP BW on Hana: Sizing SAP In-Memory Database
• Hana Sizing with an Abap Report - Download via SAP Note 1793345 - Sizing for SAP Suite on Hana
• DataVard BW Fitness Test
  - Proof of concept for the migration
  project on Hana

Abap report is the standard

Most SAP user companies use the Abap report. It checks all objects (tables, sizes) in the "non-Hana" environment. Based on the results, the Abap report suggests a dedicated sizing.

This includes memory for row store, column store, row store, CPU, disks, etc. The output for the Abap report looks like this, for example:

The Abap report does not use ADK technology (Archive Development Kit). At one company, for example, this resulted in 6 TB of data being lost in archived files.

In this case, Hana was set too small right from the start. In addition, the Abap report did not refer to the "Deep Compression" database (apart from DB2 compression).

Conclusion

Hana is not a panacea, but the in-memory technology is an extremely fast database. It offers great advantages in both the ERP and business warehouse areas.

Companies are well advised to take advantage of these benefits. However, they should definitely think in advance about what they want to use Hana for. From this, they can derive the data management that is absolutely necessary.

The big question is: What data needs to be stored in the main memory in real time? For this reason, data management and information lifecycle management are becoming increasingly important.

There is no doubt that Hana is the future. But most SAP user companies still need to prepare for it efficiently. Because even when migrating to Hana, preparation is crucial.