It should be noted that it is possible to get exceptions to the above NetWeaver Hub Strategy where upgrading the whole landscape at the same time is not possible or where systems will be decommissioned before support ends – SAP will evaluate your unique usage scenario and grade it Green (within guidelines), Amber (outside guidelines but supportable for a defined period) or Red (not supported), – this can be requested via SAP Support. It is also worth reviewing the support horizon for the Operating Systems / Databases running under the SAP system to find out when support end.īecause of the above SAP have created a NetWeaver Hub Strategy, which encourages customers to upgrade NetWeaver systems to at least 7.31, core ERP to Enhancement Package 7 and other applications to EhP3 ( see Note 123213 – requires SMP user). I have discussed these in more detail below :Īs messaged by SAP since 2012 support for NetWeaver Java 7.0x ends in 2017 and this should prompt ALL customers to review their landscape now.

I need a platform to support Digital Transformation.

I am missing out on new features that I am paying for.I see 3 topics being used to create the business case to move :. In this blog I will share some common patterns I have seen with the customers that we have helped with this transition, which I hope will help you to build your roadmap to S/4 HANA (or at least to EhP7). With the announcement of S/4 HANA and all the benefits that it brings, ALL SAP customer should be asking themselves how they plan to evolve their SAP Business Suite investment to S/4 HANA.

Sap erp ehp7