<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=158809&amp;fmt=gif">

GekkoBlog

Eliminate 90% of the Effort Needed to Fix Code for SAP HANA with Gekkobrain

GKB_safe_code_export.png

Getting the most out of SAP HANA doesn’t have to mean searching far and wide for a solution. In fact, the answer could be found by examining just 10% of your current codebase – but which 10%?

There are few things more wasteful within an organisation than squandered potential. Simply getting the best performance possible from every available resource can do wonders for productivity and it makes little difference whether it’s your employees or your IT infrastructure – it’s a lot more acceptable to try and give your tech a tune-up though.

Anybody familiar with SAP HANA will understand that it uses a very different approach to data storage, management and analysis than traditional databases. This necessitates a fresh take on ABAP-code, and, whether you’re simply cleaning up the code in your existing SAP HANA systems for better performance or going through this process prior to a full system migration, it can be a lengthy project. 

At Gekkobrain, we know this first-hand because we’ve been through it ourselves and faced the same challenges, which is why we developed our software to help drastically reduce the time it takes to optimize your ABAP code for SAP HANA.

Do You Need to Optimize 100% of your Code for SAP HANA?

The biggest thing that sets Gekkobrain apart from competing HANA-readiness software is its ability to make any HANA-readiness project shorter and easier to manage. 

Register now for our free webinar and learn how to clean up ABAP code for SAP  HANA

Instead of attempting to speed up the process of scanning your codebase and manually adapting code, Gekkobrain actually helps you strip away up to 90% of the HANA-incompatible custom ABAP-code in your systems.  

Yup, that’s right. There’s a good chance that only 10% of any potentially-problematic code in your systems will actually need to be fixed to get optimal performance from SAP HANA.

Unlike competitors who waste time scanning your entire systems and then encourage you to fix every, single, insignificant line of HANA-incompatible code, Gekkobrain saves you time and effort by highlighting the incompatible code that you can leave be – or in some cases delete.

How is it Possible?

We’re able to cut down the length and effort required for your HANA-readiness project by focusing efforts only on code that’s actually HANA-incompatible, used often in your systems and has an impact on your organisation.

It sounds obvious, but it takes the combination of three useful technologies:

  • Usage Procedure Logging (UPL)
  • SQL Monitoring (SQLM)
  • Our own secret algorithim

What Are the Benefits?

The obvious benefits to using Gekkobrain are that you could save a huge amount of time and effort  in turn saving you money too. 

That's because unlike our competitors, we don't waste time combing through your entire database or instruct you to fix every item of HANA-incomptible code. Instead we only focus on code that needs to be cleaned up.

As we mentioned earlier, it’s possible that up to 90% of your HANA-incompatible ABAP code won’t necessarily need to be adapted, leaving you with a HANA-readiness project that's much smaller and easier to manage,

Better Project-Management with Gekkobrain

Not only can Gekkobrain cut the length of your HANA-readiness project, it also sets itself apart from competitors with its analytic power and extensive project management functionality. As well as a breakdown of the HANA-incompatible code issues you need to fix, you also get a much more in-depth understanding of your upcoming HANA-readiness project.

When testing your codebase, Gekkobrain also provides an estimation of how much time will be required to fix individual issues and calculates the total length of time required until you’re HANA-ready. It helps you better organize your HANA-readiness project by assigning each issue one of the following priority levels:

  • Priority 1 Issues. Issues that must be fixed, or the system might not work after HANA upgrade.
  • Priority 2 Issues. Issues that are not mandatory but are highly recommended to be adapted to improve runtime performance
  • Priority 3 Issues. Issues that are not mandatory, but it is recommended to be adapted for performance reasons

Managing Tens of Thousands of Issues at Once with Gekkobrain

During our first HANA-readiness project we muddled forward with a gargantuan spreadsheet full of issues needing a fix and a list of employees. Although we searched for a better way of doing things, traditional project management tools just weren’t made for so many tasks.

So, we built our own project management functionality into Gekkobrain, including the addition of sprint planning.   

Optimal sprints are defined automatically by Gekkobrain based on a combination of effort, impact and complexity. This not only gives you a better overview of the work to be done, it also empowers you to focus the development and test activities around the individual sprints.

Gekkobrain also keeps track of your progress as your team is fixing code by running daily SAP Code Inspections and even notifies you when new instances of problematic code are written. These new issues are automatically added to your main list of issues, so you can immediately assign a team member to fix it.

And, at any point in your HANA-readiness journey, you can simply select the burndown chart on the very frontpage of the Gekkobrain app to see how far the project has progressed and when you can expect to be 100% HANA-ready.

New Call-to-action

Mogens Enevoldsen

Mogens Enevoldsen

I have worked with SAP since 1994, primarily within ABAP custom development and Integration. I have had several different roles eg. technical director, manager, technical project lead, specialist and developer.