The road to HANA-readiness can long and arduous but there are things you can do to prepare yourself for the journey. Even if you haven’t started planning for it, there are two things you can do right now to help with your future SAP HANA project?
There are two important elements of HANA-readiness you could look into today that could potentially save you significant time and expenditure:
- Making sure that you have UPL or SCMON active in your productive enviroment
- Making sure that all new ABAP development or changes to existing custom codefollow the HANA Readiness guidelines from SAP
What is UPL or SCMON and why should I activate it?
UPL stands for Usage Procedure Logging, and by enabling this feature in your productive environment you can track the exact usage of all development objects – both custom code and SAP standard code. (The new name is SCMON).
Best of all, it doesn’t put any strain on your system, so there is no reason not to enable UPL. It starts logging usage from the day it’s activated, so the earlier it’s activated, the more accurate the results.
So, why is it important to enable this feature?
Well, approximately 60% of all custom ABAP code is not used in the productive enviroment at all and if code isn’t being used, there’s no need to get it HANA-ready.
By importing UPL data into Gekkobrain you can identify and eliminate a significant amount of your custom ABAP code, in turn saving your significant time and effort.
To get a clear picture of which custom code you can safely get rid of you’ll need data from the last 12-15 month. So, the earlier you get UPL activated, the better.
Ensure all new code is HANA-ready
There’s little point in spending time getting your existing code HANA-ready, if your developers are creating new custom ABAP code that causes more problems.
Make sure you take the time to teach everybody in your organisation who handles code about SAP’s best-practices for developing ABAP code for HANA.
One technique for ensuring all new code is HANA-ready is to check at the point where you release a development task for a test transport to go to your test system.
Gekkobrain has developed a small piece of ABAP code which you can implement in the BADI: CTS_REQUEST_CHECK, which will check this automatically for you and notify the developer when they try to release the task for testing.
As a service, we provide this code for free, including a small guide for how to set it up.