HOW TO TURN S/4HANA CHALLENGES INTO STRUCTURAL IMPROVEMENTS

As an SAP R/3 ECC customer, you might have noticed that SAP has launched its new HANA database platform1. And that SAP has built its new ERP package S/4HANA on that platform. And, probably, you then also have heard that SAP will stop supporting its ECC package at the end of 2027 (or end of 2030 if you decide to pay for it). In that light, several ECC customers have already switched to using S/4HANA or have decided to do so. Yet quite some customers are wondering whether and when they will make the transition to S/4HANA.

A simple Google search shows positive comments. The database is faster, a number of tables have been combined into a lesser number of tables and the possibility to create new Fiori apps keeping the software core clean is often mentioned.

You can go for a ‘technical transition’ yielding ‘a faster database’. Yet you can also go for a full swing structural improvement. Structural improvement starts with the foundation – in case or ERP this means Master Data Management. It is more work, but the value will be much higher. That’s what this paper focuses on.

This whitepaper describes the steps that one can take to get these structural improvements.