Remember these points for Migration SAP ECC On Hana!
Seven points for success.
After a lot of good and bad experiences during Migration to SAP ECC ON HANA, it was possible make a list with very important points.
These points refer to SAP HANA Version, EHP Version, O.F. (Kernel, Library, File system and etc), Appliance and other information that are ommited on Guides, Notes and Sites.
Let’s go to the list:
01 – Human Resources.
- > Is Your Team prepared for these challenges?
- > Does Your Team or Partner have all the necessary knowledge?
Answer: Check all information about the skill, cases and past experiences, “Hana and Oracle SAP is not the same thing”. You will be told most of times that they are.
02 – Size Database versus Memory Size
- > The sizing analysis is very important for the project. Forconcept of memory, size is successful case.
Answer: Do it!
- > Yes, your database will be compressed.
Answer: The volume of the compression may vary between 20% or 30%. There is a simple calculation for one preview result: divide your database size by 3.5.
Ex: 600gb / 3.5 = 171,2gb (approximately).
03 – Prerequisites
- > What is the best choice: cloud or appliance ?
- > Datacenter In-House or Partner Datacenter?
- > How much is the cost?
- > How much time is necessary to execute it ?
- > How difficult is it to fix this issue?
- > We need more disk space now!
Answer: The real factor for the cost of the Project is how prepared you are. Programing and Preparation is essential for a good Project. Time to execute the activities of pre-project (Check List and), sizing database, benchmark with other companies and, one point very important, what is your motivation to begin this project?
Each point that was not properly observed creates a deviation point, which will be responsible for new costs, new deadlines and the need of more resources (human, Time, Physical or budget) for the same objective. So, the question is: Can I actually start it?
04 – Check, Double Check and Triple Check
- > Times
- > Costs
- > Prerequisites
- > Activities
- > Results and Deliveries
- > Status (Work in Progress, Completed or On Hold)
- > 99,99% is not 100% (alignment, set point expectative and check if is totally clear understanding between the parties.).
- > Time for Response (defined by priority, risk and complexity)
05 – Know the process, the steps, the terms and people.
- > when will it be the preview test?
- > When will we make Backups and who will do it?
- > Who will take the Checklist?
- > Who will take the SPAU?
- > Who will take the Test?
- > How much time to execute UP-Time?
- > How much time to execute Down-Time?
- > When the system will be Online after due Down-Time?
06 – Fast and Furious (expectation management)
- > How much faster?
- > My problems will be solved and will be the end of all low performance.
- > New developments with more speed and less complexity.
- > Standard and Generic transactions much faster.
Answer: No, it’s not true! Although migration may produce very positive results, there are recommendations for the use of new transations H., corrections on the abap generic programs, conversion of tables for column and a lot of items for observation.
07 – The day after of the go-live.
- > Monitoring
- > Support
- > Performance monitoring
- > Follow always the Hana’s recommendations
- > Schedule a new SAP Earlywatch Check
Nice...you can add - code remediation and optimization, we generally using Panaya and Solution manager CCH tools