cancel
Showing results for 
Search instead for 
Did you mean: 

Release upgrade efforts - equivalent support packages

pankaj_pabreja
Participant
0 Kudos
1,209

Hi All,

We are planning to perform the upgrade of our ECC system from ECC 6.0 EHP5 SP13 on Windows 2008/MSSQL 2008 to ECC 6.0 EHP8 SP11 (Latest stack) on Windows 2016/MSSQL 2016 . It will be done in 3 phases due to OS/DB limitations:

1. ECC EHP5 SPS update to atleast SP 15 to make it ready for MSSQL 2016.

2. Migrate the ECC EHP5 to windows2016/MSSQL2016 servers.

3. EHP8 upgrade from EHP5 on new servers.

Now, my query is regarding the first point. The equivalent level for EHP5 SP15 is EHP8 SPS08 and hence we can define the target as EHP8 SPS11 for the upgrade.

If we update the ECC EHP5 to the SPS 15 in the first point, its equivalent package for EHP8 will become SPS 11, will it reduce the timelines/efforts for the 3rd step?

Is it advantageous to have the support pack of source release equivalent to the target support pack during release/EHP upgrade? Does it reduce the efforts of the upgrade?

Regards,

Pankaj

pankaj_pabreja
Participant
0 Kudos

Correction on query:

If we update the ECC EHP5 to the SPS 17 in the first point, its equivalent package for EHP8 will become SPS 11, will it reduce the timelines/efforts for the 3rd step?

View Entire Topic
S_Sriram
Active Contributor
0 Kudos

Hi Pankaj.

1. Is it dual or single ABAP stack?

2. As you said three steps to upgrade to EHP8 you can follow the same if possible do the mock test before starting the live landscape.

BR

SS