Documente Academic
Documente Profesional
Documente Cultură
SEARCH
()
Bluefin (/) › John Appleby (/blogs/john-appleby) › Tips for a successful SAP Business Suite on HANA migration
Related SAP Suite on HANA vs SAP S/4HANA – the differences explained (/Blogs/Mark-Chalfen/April-2016/SAP-Suite-on-HANA-vs-
SAP-S4HANA-the-differences)
The SAP® Business Suite 4 SAP HANA® (SAP S/4HANA) FAQ (/Blogs/John-Appleby/February-2015/The-SAP-Business-
Suite-4-SAP-HANA-(SAP-S4-HANA))
Larger organisations are breaking their journey to SAP S/4HANA into several steps to reduce risk. The first
logical large step is the upgrade of the core ERP system onto the SAP HANA database platform. I reached
out to my team to answer the question: How do we ensure the success of an SAP Business Suite on HANA
migration? Here's what I found out.
A production copy will have the full database size, and so you have the beginnings of the timings
for a cutover plan, you can build a detailed run book based on a simulation of production, and
you have the current code set (development systems often have a different code-base to
production).
Because of the amount of data that needs deleting, we often find that housekeeping often takes 2-6 months to complete. The clean-up jobs
can take a really long time to run, and you don't want to impact business operations, by needing to be too aggressive.
If it's ready in time, you could even use it for your first sandbox (see point 1). Either way, you want it running for some time prior to cutover, so
any teething hardware configuration errors are resolved prior to production migration.
In the past we have rolled in all manner of changes including Linux Application Servers, VMWare, Unicode Conversion, Enhancement Pack
upgrades, etc.
You will have a project management office, Basis, ABAP and Test Management resources already available, and extending the scope is
incremental compared to doing a separate update at a later time.
The SAP Business Suite on HANA is the first step for organizations to get to S/4HANA, and there will be more testing in the years to come, so
it really makes sense to do a good job of test management now. Evaluate your test coverage as compared to business process, ensure you
have modern tools in place and look at test automation where appropriate.
It is critical to do custom code remediation on HANA, because SAP spent a lot of time optimizing the Business Suite on HANA, and your
custom code will not be optimized by default. This can lead to severe performance problems, and issues with functionality.
SAP Solution Manager is the starting point for this, with tools like Custom Code Cockpit (CDMC), Usage & Procedure Logging (UPL) and
Clonefinder, which help you understand your custom code. We also partner with tools like smartShift, which takes the custom code from your
existing system and applies a set of algorithms to automatically remediate your custom code - reducing the cost, and human error.
It's important to identify those processes that are important to the business, and benchmark them. This might be some critical month end
reports, but in one client’s case it was an approval mobile app for promotions - an app used by C-suite executives.
Once you have benchmarked them today, you can ensure they are measured as part of the test process, and additional focus can be put on
ensuring they are optimized for the HANA platform. This will help with the communication strategy.
a. The first is the Run Book, which is a step-by-step guide to the migration and typically spans a few hundred pages. It means that if you need
to switch out resources at the last minute, due to unforeseen factors, you can bring in a very experienced resource to look after the next step
of the project. In addition to this it ensures that at 5am on a Saturday morning at the end of a long shift, mistakes are less likely to be made.
b. The second is a set of project plans. We recommend 3 levels: High-Level, Mid-Level and Detailed.
High-level plan: used to communicate with the steering group, and it has the milestones defined on it, so a C-suite stakeholder can see
where the project is at a weekly granularity in PowerPoint.
Mid-Level plan: typically printed onto a large sheet of paper and is human-readable, so all project members can understand progress;
it's usually planned at a day-by-day level in Excel.
Detailed project plan: is in Microsoft Project, and often several thousand lines long, and updated by the Project Management Office.
For both of these reasons, we recommend you run an extended hypercare. A go-live window is typically 1-2 weeks after month end, and we
recommend you run it for 6-8 weeks after that, rather than the usual 2-week window. This enables you to immediately take advantage of the
HANA platform improvements and use the existing project team to capitalize on the benefits early.
What this means is that you can afford to be aggressive with your timeline. You still need to do a great job of planning, testing and executing,
but it is possible to move quickly, and be risk-averse. For example, we have moved a large SAP BW client to HANA in the manufacturing
industry in 8 weeks, and a large SAP ECC client to HANA in 16 weeks, including a large amount of code remediation and thousands of test
cases.
Final Words
Thanks to Lloyd, Brenton, Srinivas and Anna for their input into this blog. It's been a reminder to me that with a project like this, the team is
greater than the sum of its parts: each person had a unique and relevant perspective to this story.
(/blogs/mark-chalfen/april-2016/sap-suite-on-hana-vs-sap- (/blogs/james-appleby/february-2015/s-4-hana-after-23-years-
INSIGHT INSIGHT
s4hana-the-differences) of-r-3,-welcome-sap-r-4)
SAP Suite on HANA vs SAP S/4HANA – the differences S/4 HANA: After 23 Years of R/3, welcome SAP R/4
explained 10 Feb 2015
22 Apr 2016 James Appleby
Group Chief Executive
Mark Chalfen
SAP S/4HANA Global Lead
Insight (/Insights/cat_Insight)