Migration to S/4HANA – Best Practices from Lenovo IT
Lenovo is a global Fortune 500 company and a leader in providing innovative consumer, commercial and enterprise technologies. SAP ERP Central Component (SAP ECC) is a core IT system of Lenovo. It plays a vital role in supporting global business, including management of the significant amount of sales orders fulfilment and supply chain management.
In a significant step towards digital transformation and become a best-run business, Lenovo IT is migrating legacy systems from non-SAP HANA databases to SAP HANA. This will help the technology giant to get a complete picture of operations and use customer insights to help marketing, sales, and service teams work more productively, grow revenue, and accelerate opportunities.
Before the production ECC migration to S/4HANA, the IT team at Lenovo launched S/4HANA Scale-out Cycle 1 Project in cooperation with SAP, and discovered significant best processes.
Download this whitepaper to understand how the IT team at Lenovo:
- Verified the technical feasibility including functional, technical and custom code adjustments
- Ensured safe handling of the massive data volumes and transactional load
- Tested the appropriate infrastructure configuration for SAP HANA
SAP S/4HANA is the next-generation ERP business suite, a real-time enterprise resource management suite for the digital business built on advanced in-memory platform SAP HANA, delivering massive simplifications (customer adoption, data model, user experience, decision-making, business processes and models) and innovations to help businesses “Run Simple” in the digital economy.
SAP ECC is the next system on the Lenovo HANA adoption roadmap. Currently, Lenovo ECC is running a data size of almost 40TB, facing an enormous volume and high transaction load.
Lenovo continues to follow the SAP HANA adoption journey. One big step is the potential move to S/4HANA for the central ECC system, which covers all Lenovo business transactions as a system of record. Due to the large database size of the current system running on any DB and a legacy hardware technology, it is necessary to design the target SAP S/4HANA system in a Scale out configuration. The Cycle 1 test contained three major steps:
- Migrate the data out of any DB into SAP S/4HANA
- Distribute the data across the worker nodes, to avoid cross node joins
- est selected transactional and analytical business processes from a functional perspective
Sneak Peek into "Best Practices from Lenovo IT’s Journey Towards SAP S/4HANA"
The result of the project is promising. The database size was reduced from 38 TB to 8.5 TB. The runtime for the transactional business processes ran mostly faster or at the same speed than before. A few transactions are running slower. The runtime for ¾ of analytical reports was better on S/4HANA the other ¼ still has challenges.
With the next hardware generation on the horizon and SAP loosening the strict binding of the memory to core ratio for SAP HANA even a smaller cluster with –for example- 2 nodes with 8 CPU sockets each and 12 TB of main memory could provide an even easier setup and better potential of distributing the data and achieve better performance.