But then this is a NW-Portal update project and will not be a Business Suite update project, and the decision is made by the user, not forced by SAP.Ĭonclusion: Users can make an update to ECC 6.0 EhP4 without the need to perform an upgrade of the Portal to 7.01, the decision to make this Portal upgrade will depend on user needs to use new features includes on it. refer the SAP Note 1676665 - Setting up Microsoft SQL Server 2012. Upgrade the existing MS SQL 2008 R2 to 2012 R2. Current ECC system NW 7.00 SP 23 to Minimum sp level 28, along with MS SQl latest service pack. Product version EHP 4 for SAP ERP 6.0/ NW 7.01 = all new EHP4 application functionality available for EP 7.01įrom NetWeaver perspective, if a user wants to use new Portal features, then it is up to him to plan and run a portal update. I think you have to upgrade the MS Sql 2012 R2.Product version EHP 4 for SAP ERP 6.0 = all new EHP4 application functionality available for EP 7.00.To be able to use this concept there exist two different product versions which you can select in the Solution Manager - Maintenance Optimizer: Please note that ECC 6.0 EhP4 contain a NW Foundation 7.01, but the EhP4 has been designed in a way that users have the free choice of updating the Portal to NW EhP1 (aka 7.01) or staying on EP 7.00, this option will be related to the usage of a new feature included in the Portal 7.01 and not as a mandatory request to use it.

Normally it's recommend to have NetWeaver Portal in same or higher version than the backend system, however now with the EhP4 for the ECC 6.0 or the Business Suite 7.0 a new recommendation apply. By considering above we choose SAP ERP 6.0 EHP 7 SP5 as our target release as it would not arise the need to upgrade our Database to DB2 10.5 and we can continue with our current DB2 version i.e.

How to upgrade from sap ecc 6.0 to ehp7