Everybody is talking about HANA migration
Every event or workshop that SAP customers attend right now is somehow about HANA. There is no way around the topic. It seems that the whole world is only about HANA and everyone is talking about it.
We found that that is only true to a certain extent. Yes – everybody is talking about HANA. But does that mean that everybody is already migrating to HANA or planning their migration to HANA or are already on HANA and I am one of the last ones to migrate? No, no and no.
We find there is a large gap between what is said at events and what is actually happening. So if you don’t have your plan in place yet, don’t worry, you are definitely not the only one and there is still more than enough time. I am sure that a lot of SAP systems will not be on HANA by 2020. In 2020, however, I hope everyone will have their plans is place because migration projects we have worked on so far always lasted at least 1 year from the first idea till the successful migration.
I would like to just give some small piece of inspiration for the people working on their HANA plans, as there are some topics that keep coming up in every migration project, regardless of the industry, system’s specificity, or company size.
Reduction of HANA size – Housekeeping and Data Model changes bring a lot of benefits to the business case
Trying to figure out the right size for your SAP BW on HANA can be quite a challenge. So many questions need to be answered. The sizing report already gives a good indication. It tells you the actual sizes, compression ratios and the growth of the system based on actual data. Two questions come up though:
1. Is there a way to reduce the overall size to make the whole thing cheaper and help my HANA business case?
2. Will there be any changes to the data models that will significantly impact the sizing?
For the first question, the answer is yes. Many systems have a significant housekeeping potential. This can save you quite a bit and it also gives you wiggle room in your sizing. If some other area grows larger than anticipated, you can clean up a bit and make some room.
In our migration and preparation projects we use our BW Fitness Test software to analyze the distribution of data within the SAP BW system. From the analysis we can build a plan how to reduce the systems overall size. On average we save 30% of the size.
As for the second question, data model changes can also help a lot. Check for yourself if you can reduce redundancies in layers and therefore have less Infoproviders:
Code Changes – Can be quite a lot of work when preparing SAP HANA migration
Make sure you have a good picture of what code changes must be done before or during the migration. There are many ways to analyze this, including tools from SAP. This can be a huge effort driver and can delay projects, so it’s key to be well prepared.
On the positive side, on HANA you can benefit from simplified data models. Having a more lean data model with less layers will reduce size needs and at the same time reduce maintenance effort. This can be a piece of work to change, but it really helps you lot. Again, here the key is a good preparation. Know your situation well and you will have less surprises:
Migrating to SAP HANA calls for a lot of preparations. To see how a system readiness analysis might look like, check out this demo.