Zjef Mallaerts - - Digital stories
SAP S/4 HANA is all about simplification. Yet many companies are hesitant about moving their current SAP Business Suite to S/4HANA. A good preparation is a great start. Let’s zoom in on a key topic to address in a transition process: migrating your custom code to the new S/4HANA data model.
Let’s start with the why. What makes SAP S/4HANA the platform of choice? Simplicity is the name of the game! Thanks to the power of the SAP HANA in-memory platform, SAP has been able to simplify the SAP Business Suite data model dramatically. Performance gains at the database level have enabled SAP to completely remove intermediate result and aggregation tables from the data model. In many modules – FI/CO, SD/MM and more – the number of tables containing master data has been drastically minimized! Not only does this speed up overall performance, it also greatly reduces the memory footprint of your database.
SAP has adapted all standard code in the S/4HANA system to comply with the new data model. However, when it comes to your own customer-specific coding (“Z-code”) such as custom transactions or user exits, you are responsible for making sure that your code is adapted.
What are key steps to consider when preparing for your S/4HANA conversion project, and, more specifically, your custom code migration?
Now that you’ve carefully plotted out what needs to be done and have stripped away all unnecessary data, start adapting your custom code. Keep reading to learn more about the 3 major types of modifications you’ll need to implement:
Keep in mind that only some of these activities are mandatory, while many are optional functional/performance optimizations. After all, when it comes to the scope of your project, you’re in the driver’s seat. Looking for somebody to help you navigate the road to migration success? Flexso can help – find out how below.
We can help you optimize your migration by helping you with the following steps during your preparation phase (no S/4HANA system is required at this point in your project):
Contact us for more information!
1/25