SAP has invented a new database. Most of us know that by now. But what not all SAP customers know is that in order to move on to HANA then their custom coded ABAP programs must change, in some cases almost all of the custom code lines will need some change to survive the jump.
1st rule of robotics
When the Gekkobrain algorithms that make up our code fixing robot first evaluate a customer system it estimates the number of issues found. And that’s not just a rough estimate, but it’s right down to the special variety of a particular syntax that the developer has chosen to apply on a particular piece of code. It does this because it will need to estimate how the human programmer wanted to use the data that was retrieved from the database. Only when it’s absolutely safe to convert the code the robot reports its findings as positive and suggests a suitable fix. It doesn’t take chances.
It’s a trusted task to upgrade a customer’s system. And what’s more. If a robot manages that task, then it’s crucial that every step that robot takes to estimate its work and ultimately convert that code is under strict supervision.
And so, much like you would watch a robot getting better and better at playing chess while still observing the rules, we like to visit the thoughts of our robot as it churns through literally millions of lines of custom code to arrive at what it believes to be the best fix possible. When Assimov wrote The 3 Laws of Robotics little did he know that in order for a robot to be trusted, it probably first needs to be always helpful, but secondly we believe that it also needs be talkative :-)
At Haldor Topsøe they have just migrating their system to Business Suite on HANA. And after an introduction to the Gekkobrain tools they began by logging onto their legacy system, transferred the code to Gekkobrain’s code fixing robot and in a matter of hours the fixes needed to bring them onto HANA was ready for them. Choosing what program goes and what stays is often a matter of knowing which code is used. And with the usage reports provided by Gekkobrain that information is available at the time of fixing.
License to migrate
Consider this fact: Haldor Topsøe went to production on the basis of knowing exactly what was fixed and how it was fixed and why it was fixed.
What team of human developers can you get that information from without revisiting the changes they made or the documentation they did?
And how many developer keys would you need to buy from SAP before even getting off the ground on day one, before the excruciatingly many days of waiting for the developers to finish?
Its a wrap
We’re proud of our robot here at Gekkobrain, like any parent would be proud of their children at graduation time.
Our robot would like to thank Haldor Topsøe for using its algorithms on their custom code.
Do you need to get your custom code HANA ready as well? Get in touch and we will be happy to provide a demo.
The image below depicts the typical Gekkobrain code remediation process: