THE YASH HANATIZATION APPROACH

Custom code hygiene for ECC to HANA Database compatibility

Are your codes sanitized enough to be HANA-ready?

Any one-size SAP doesn’t fit all businesses. Each comes with its own idiosyncrasies, likely supported by custom codes created internally with the company’s strategic needs in mind. It is a unique imprint of your organization, a digital DNA if you will.

What of the future?

The digital world is evolving at a breakneck speed, disrupting entire industries, flipping business models, presenting new opportunities with advanced technologies like automation, machine learning, big data and more. If you are using SAP ECC for instance, your journey to the SAP HANA database also brings such aspirations of a modern, digital-first business – for you, your workforce, and your customers.

This move to the new HANA  database also means, however, that your custom codes will need to be compatible with the new database, in terms of how efficiently the codes will perform, as well as how easily accessible they will be in the new environment. In the context of transition to the HANA database in particular, there are a few typical compatibility tests to be carried out before, during, and after the migration takes place.

But how do you make this journey from ‘data-to-code’ to ‘code-to-data’ in a seamless manner? How do you make sure you derive the maximum benefits from the new HANA database? YASH’s HANATIZATION solution, is a crucial step towards achieving this. But first, let us understand why we need it in the first place.

How to be HANA-ready?

YASH’s SAP ‘HANATIZATION’ journey helps ensure that all legacy or custom codes are adjustable to the new database. To orchestrate seamless functionalities across data, departments and teams, the codes also require optimization, for the ability to push custom codes down efficiently to HANA database. SAP in fact provides tools for Database Simplification to detect any custom code requiring adaptation after migration.

Let us understand what are the key phases in HANATIZATION, helping enterprises become HANA-ready.

The YASH ‘HANATIZATION’ journey

The process of HANATIZATION takes place in four key phases. The first phase – ‘preparatory’ – is custom code scoping and customized code analysis. It allows you to determine whether the ABAP custom code can be taken over or deleted entirely, minimizing the next phase’s efforts. The second phase – ‘realization’ – deals with custom code functional adaptation and custom code optimization after the technical system uprade/migration/conversion.

The third phase is ‘system checks’, wherein we check processes, (say, the performance of critical database inquiries) need to be optimized in the new system. SQL performance optimization using SQL Monitor is one of the tools for an overall analysis of the custom code.

Finally in the ‘handover’ phase, YASH team documents the confirmation of successful code modifications, and ensures a smooth transfer of knowledge for the client teams to be up-to-date on the system needs.

Future-ready with YASH and SAP

YASH’s pre-built HANATIZATION solution is a vital step for any organization looking to the future disruptions with SAP’s advantages in their armory. Seeking the right partnerships with trust is equally crucial, which is where you may need external support of IT consultants like YASH, who have specialized in creating custom-SAP roadmaps for 450+ businesses across sectors in partnership with SAP.

Read the complete HANATIZATION whitepaper here. If you want to know more about how we have helped them with our 16+ centers of excellence (CoEs), please check out our ‘HANA-ready’ success stories here.

• ECC to HANA Database
• HANATIZATION
• S/4HANA
• SAP