SAP Cloud: ready & on point
SAP extends ERP maintenance: What does this mean for your S/4HANA strategy?
SAP recently announced that it will extend ERP maintenance for some companies until 2033 - subject to a few conditions. This gives companies that have not yet finalised their migration strategy a little more time. Nevertheless, one thing remains clear: the future lies in the cloud, especially in the S/4HANA Public Cloud Edition. But what does this mean for development teams working with extensions and customisations in the various cloud variants?
Extension strategies for S/4HANA Cloud - what development teams need to consider
SAP is pursuing a clear standardisation approach with the S/4HANA Public Cloud. While customers can continue to make in-depth customisations in the private cloud, enhancements in the public cloud are no longer possible through traditional modifications or in-depth interventions in the SAP core. Instead, development teams should utilise new concepts and technologies offered by SAP:
1. SAP Business Technology Platform (BTP) as a central extension platform
The SAP BTP is the central tool for extensions in the public cloud. With the SAP Extension Suite and Integration Suite, new functions can be developed without changing the standard code. Development teams should therefore increasingly rely on side-by-side extensions that interact with the core system via APIs. The best thing about this is that the update capability of the core system is guaranteed at all times. Gone are the days of classic SPAU synchronisation!
2. Embedded Steampunk: ABAP in the cloud
With Embedded Steampunk (ABAP Cloud), SAP has created a way to implement ABAP developments directly in S/4HANA Cloud. This allows companies to use existing ABAP expertise to develop cloud-compatible extensions. However, there are clear restrictions in terms of access options and modifications.
3. key user extensibility tools for the public cloud
Key user extensibility tools in SAP S/4HANA Public Cloud enable specialist departments to make adjustments to the software without in-depth developer knowledge. Processes can be optimised efficiently with functions such as user-defined fields, form adjustments and simple automations. This allows companies to react flexibly to selected new requirements without jeopardising the stable cloud core.
4. private cloud developments: More flexibility, but not always future-proof
In the private cloud, there is more scope for customisation through the use of classic ABAP solutions. Nevertheless, development teams should ensure that their extensions are future-proof and that subsequent migration to the public cloud is made easier. SAP already offers support for this as part of the development tools.
Conclusion: development teams need to reposition themselves
SAP is focussing on the public cloud. Development teams should therefore familiarise themselves with new technologies and methods. Using SAP BTP, switching to ABAP Cloud and complying with cloud development guidelines are crucial. Those who adapt their enhancement strategy now will be more flexible and better positioned in the future.
Now is the right time to look at the new possibilities - because the future of SAP development lies in the cloud.
Mercoline supports companies in future-proofing their S/4HANA strategy. With our experience in cloud extensions and SAP technologies, we can help you find the right solution for your requirements.
Would you like to find out more about getting started with the SAP Cloud? Read the first part of our blog series ‘Cloud Ready & On Point’.