6 Tips for Improving Your ABAP Code Performance

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email

So you want to improve the performance of your ABAP code? Well, in that case, start out by making it HANA ready, because 99% of the changes you need to do to make it HANA ready is simply making it better.

For instance, SELECT* has always been a very bad idea, because it puts unnecessary strain on the database by selecting all fields. If you only need the field containing the customer number, why then do a SELECT* and select all fields? You will fetch way too much data compared to what you need.

This type of SQL statement is stupid and it’s really bad for performance. In AnyDB as well as in HANA, where it is particularly bad. So – clean it up and select the fields you need in the code. (Tip: Gekkobrain for SAP HANA can fix the for you automatically)

Hold on, you think. What are the fixes needed for HANA?

The picture above shows an actual screen dump from Gekkobrain for SAP HANA and shows you, which code issues we found in a customer SAP system.

Priority 1 Issues – Mandatory

That’s issues that has to be fixed, because the system might otherwise not work after migration to HANA.

Priority 2 Issues – Performance

These issues are not mandatory per se, but they are very important, because they have ad adverse affect on runtime performance and thus should to be fixed in a HANA upgrade. AND these are the issues, you should fix already today on AnyDB!

Priority 3 Issues – Performance related

Like the issues above, these are not mandatory but it’s highly recommended that they are gone through and fixed for performance reasons. Again – worth while looking at the most impactful ones here already on AnyDB!

So – summing up the 6 tips for cleaning up ABAP today

So – even if HANA migration is 1, 2 or 5 years out in the future, do yourself, your SAP system and especially your users a favor, and clean up you code today. Take a look at the following 6 tips:

  1. How many code performance issues do we have?
  2. Which issues do we need to fix after an automatic cleanup? (as mentioned, Gekkobrain can take care of the most serious ones for you)
  3. How long does it take to fix the issues?
  4. How do I prioritize the issues?
  5. How do I keep track of progress?
  6. And finally how do I keep track of new code?

Those are very important questions to ask yourself long before you even think abvout HANA, because most SAP performance problems actually arise from bad custom code. And – you ought to get that cleaned up.

Interested in improving the performance of your SAP systems? Book a free demo today to get your ABAP code optimized.

Scroll to Top