SAP Business Suite on HANA migration
- System landscape with several ERP, GTS and SCM systems: a total of 31 affected systems
- Migration from DB2 (DB6 10.05) to SAP HANA 1.0
- Over 40,300 custom objects with over 200,000 findings checked for HANA compatibility and HANA performance optimization
- Simultaneous EHP upgrade of multiple systems
- Parallel migration of the data center by DXC Technology
- Significant reduction of overall project duration through the use of smartShift automation
- Committed transformation time lines by smartShift have been achieved and mostly even be undercut
- Only 7 conversion errors in more than 80,000 adjustments of coding
- Increased performance in batch and online by up to 50% as result of the HANA database migration
- HANA compatibility analysis of add-ons and extensive comparisons to synchronize the system landscape
As the market leader in cleaning technology, Alfred Kärcher GmbH & Co. KG (hereafter, “Kärcher”) commissioned smartShift Technologies (hereafter, “smartShift”) and DXC Technology to perform the migration of their SAP system landscape to SAP HANA, including their central and worldwide used SAP ERP systems. To be prepared for future challenges, the project not only covered the database migration, but also the migration of the data center as well as the upgrade to the latest available SAP enhancement packages. As a specialist in the automated transformation of customer in-house developments, smartShift was engaged to ensure system compatibility with SAP HANA.
Kärcher decided on a two-step approach during its HANA journey. The first step was the migration of the ERP systems to the HANA database. In step 2, SAP S/4HANA was implemented on the application side. The goal of this migration approach was the implementation of technical preparations as well as preparations on the application side to achieve performance gains.
The Kärcher system landscape showed a typical structure. The ERP systems contained a great amount of customer-specific developments, while the SCM and GTS systems involved comparatively few in-house developments. As a result, the first system analyses showed large ERP systems with more than 40’300 custom code objects. The smartShift tools identified over 200,000 individual findings that had to be addressed in Kärcher’s custom code. Of note, only the most important HANA categories (HANA compatibility and HANA performance) were considered in this project. Other transformation rules (e.g., to improve code stability, maintainability or security) were not covered.
The project started in early 2017 with a general planning and setup phase. Initially smartShift performed a detailed HANA compatibility analysis of the installed add-ons as well as system comparisons of the custom code in the system landscapes. The impact of this upfront analysis phase empowered Kärcher to contact its add-on software suppliers to obtain HANA-compatible add-on versions at the beginning of the transformation phase.
Additionally, the project team was able to gather information about the differences between the development, test and production systems with regard to customer-specific coding in order to get a clear picture for the required synchronization.
The complete migration of the ERP and GTS systems was first tested in a development sandbox system and then validated in a production sandbox system.
Every time, Kärcher received the adapted code from smartShift for testing no later than two weeks after smartShift commenced remediation. This significantly reduced timelines with limited development windows and the overall project duration. During testing, Kärcher reported only 7 errors that were promptly addressed and resolved by smartShift. The testing phase was also significantly optimized. A continuous automation rate in excess of
90% was achieved through the help of the smartShift tools.
smartShift’s service team project support was flexible depending on Kärcher’s needs. For example, the requirements were extended during the project and additional systems and objects were added to the scope without putting deadlines at risk.
In all, 5 production ERP systems, 1 GTS system and 1 SCM system are now live. This was achieved within the required total project duration of less than 6 months.
This HANA migration is considered a success by Kärcher – both technically and commercially – and has paved the way for further transformations of Kärcher’s IT landscape.
Kärcher will continue with its migration to S/4HANA. As this and other successful projects demonstrate, the use of smartShift automation can make a valuable contribution to the effective and low-risk implementation of an S/4HANA conversion.
In 2018, Kärcher plans for further HANAmigrations to take place in the system
landscape with active support by the smartShift team.
“Thank you very much for your dedication and commitment over the last few months, especially at the GoLive last weekend. Kärcher and you all formed a team that was always flexible and solution- and goal-oriented, even in difficult waters and has quickly solved emerging problems.”
– David Willen, CTO, Global Mobile Application Platform Provider Company