As we have mentioned earlier, we’re very interested in finding out, what AI can do for our clients: How can we leverage AI to extend the Robotic Process Automation (RPA) elements of our tools? How can AI improve the portion of automatic ABAP code fixes, we offer? How can we use AI to add more
Upgrading to SAP HANA in itself is a relatively straightforward process, because SAP has already prepared all its own code for HANA. I won’t go into details about why you should upgrade, because the benefits are covered elsewhere. All I can say is that you definitely would want to upgrade. HANA’s take on big data opens up entirely new ways to run your business.
Ever wondered, what we mean about Actionable Advice in Gekkobrain DevOps for SAP®? Well, here’s a fresh example from one of our customers. If Gekkobrain DevOps finds any issues, then the SAP Technical Lead receives an email, which highlights the most pressing issues.
Over the past few months we have been in dialogue with quite a number of our partners’ customers, and in those conversations, one thing has become very clear: Very few realize that cleaning up custom code is not something that should wait until you decide to upgrade. You should start now.
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.
ABAP code has been used by programmers working with SAP products since the 1980s, so why is it starting to cause problems for organizations who want to migrate to and get optimal performance from SAP HANA almost 40 years later?
One thing we’ve noticed in almost every SAP project we’ve worked on, is the sheer volume of unnecessary or under-performing ABAP code haunting clients’ SAP systems. To help exorcise that code, we built the Gekkobrain Code Optimizer.
Normally, DevOps tools aim to deliver better performing code through lots of tweaks to code already in production, based on frequent feedback using real-world data. Our new DevOps for SAP tool achieves similar results without constantly rewriting your ABAP code – accurately forecasting code’s performance data, as you write it.
This is a question, we often get from new and prospective customers. We normally answer in number of issues, which ranges from anywhere from 10,000 to 100,000 for a normal customer.
Cleaning your ABAP codebase can be daunting, so it’s tempting to either drag your heels with endless planning or jump in both feet first. Of course, striking the right balance between the two is key to success and a great start is understanding these 7 challenges.
We’ve talked a lot about the benefits of migrating to SAP HANA and covered what ABAP code is. However, you could be forgiven for wondering why adapting custom code is so crucial to a successful HANA migration project. With that in mind, here are 3 key reasons for cleaning up your custom ABAP code.
We’ve talked a lot about our HANA-readiness tool Gekkobrain, as well as the benefits and challenges of adjusting your ABAP code for SAP HANA. But how does Gekkobrain work? And what is it that sets our tool apart?
DevOps is tricky for SAP companies. It rhymes with something not well enough governed for an enterprise world for some, but really it doesn’t have to be.
At Gekkobrain we get asked a lot why we have built a DevOps tool now that we automatically convert ABAP and analyse your HANA readiness.
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%?
Gekkobrain is the only software for SAP that uses data to identify custom programs that create extraordinary business value and provides insight into all issues allowing for faster transformation, better performance and savings on cloud hosting.
