EHP6 Upgrade

[Former Member]

Hi Experts,

We are planning to Upgrade from ECC6.0 to ECC6.0 EHP6.

OS: WIndows 2008 R2, DB:DB2 [ According to PAM OS and DB are ok]

Apart from Basis team insllation, is there any Application member activity required for this upgrade?.

Also please let me know how long does it required for the DEV system[ECC6.0] upgrade to EHP6.0?

Thanks

Thiru.

[Reagan]

Morning

Apart from Basis team insllation, is there any Application member activity required for this upgrade?.

One Basis person for the complete upgrade activity. One developer for SPDD and SPAU tasks

Also please let me know how long does it required for the DEV system[ECC6.0] upgrade to EHP6.0?

1 week would be sufficient.

Regards

RB

[Former Member]

Hi RB and All,

Can you answer to above questions?.

Thanks

Thiru

[Former Member]

Hi Thiru,

1. As mentioned in the note you have to update the components before proceeding with the EHP upgrade.

2. If you use the solution manager all the existing components will get it included in the XML file for the EHP upgrade. Also you can add any addons to be included along with the stack XML generation.

Hope you are clear.

Regards,

Raja. G

[Former Member]

Can SPAM/Saint be used or we have to use SUM for upgradation like fund management or HR copmponent from 600 to 606??Also I would like to know is it necessary to patch the components like sap_basis,appl etc or We can do all this in one shot using stack xml generation and SUM .Hope it's clear.

[karthikeyan_natarajan4]

Hi Asim,

When you want to upgrade from 600 to 606 for the HR or any other component its needs your EA_APPL and SAP_APPL to be in the same version. SAP_APPL will need SAP_BASIS and SAP_ABA should be in the same version.

Hence, it's always generate the stack.xml file using MOPZ and download all the files, then use SUM for upgrade.

[Reagan]

Hello

Can SPAM/Saint be used or we have to use SUM for upgradation like fund management or HR copmponent from 600 to 606??Also I would like to know is it necessary to patch the components like sap_basis,appl etc or We can do all this in one shot using stack xml generation and SUM .Hope it's clear.

SUM is tool which is used for all maintenance activities like patching, upgrade, etc. It is doing the tasks which were previously done through SApehpi, SAPup, SPAM, SAINT and JSPM.

The reason why we need to create a stack file is because there will dependencies between target release you have chosen. The Maintenance Optimizer will take care of this and create the stack file accordingly for you.

Regards

RB

[Former Member]

Hi,

There is not much involvement for the application team during the upgrade. Most of the task are performed by the Basis Team.

You might have to get them to fix any issues if they have modified any standard sap object and you are getting issues because of it.

You might require them during the upgrade when you have to fix the SPDD changes.

But once then upgrade completes you might need them to fix all the SPAU changes and to retrofit the code to help the old functionality work. This time frame will depend on the number and the type of customising done in our project and the amount and the seriousness with which testing is done in your project.

I think from the Basis side if all is good and green you might require 5 days during the uptime and 1 day for the downtime.

The stats given for the time frame are quite generic and will change depending on different things.

Like : CPU,Memory,Memory configured in the system, Processes allocated to the system,Network and the IO read write, database performnace and size of your system, Number of sp you need to apply etc ..

Thanks

Rishi Abrol

[Former Member]

Dear Deepak, Ho,Abol,

Thank you for your quick response.

1.According to Note#1566412,  It states that EHP6 equivalence level for ERP 6.0 will be SP20.

In my case,

1)Is it mandatory to upgade the  the Support packages from SP 07 to Sp20 and then Updating EHP components to EHP6 ).?

Or

Is it possible to club the support package and  EHP components with the one upgrade activity (SUM) ?  [After downloading via the Via solman] with stack file]

2) regarding the EHP 6 package component selection, my cusotmer simply asked us to do the EHP6 upgrade. in this case Is it better to include all the EHP6 components or ?..

Thanks

Thiru

[Sriram2009]

Hi Selvan

   1)Is it mandatory to upgade the  the Support packages from SP 07 to Sp20 and then Updating EHP components to EHP6 ).?
Or 
Is it possible to club the support package and  EHP components with the one upgrade activity (SUM) ?  [After downloading via the Via solman] with stack file]     

Yes you have first upgrade SPS to 20 and then start the EHP installation thru SUM tool

 2) regarding the EHP 6 package component selection, my cusotmer simply asked us to do the EHP6 upgrade. in this case Is it better to include all the EHP6 components or ?..

In your environment you having solution manager you can calculate thru 'MOPZ' that will be very easy way to find the EHP6 components

Thanks

Ram

[Reagan]

Hello

Create a stack file for EHP6 upgrade using the Solution Manager.

The stack file generated will calculate all the packages for the EHP6 upgrade.

Read this:

Solution Manager Maintenance Optimizer (MOPz)

Use the Solution Manager Maintenance Optimizer (Transaction DSWP) to

         select the needed Technical Usages you need to install in order to use the Business Functions of interest

         calculate a consistent target state of your system landscape,

         calculate all needed Software Components and required Support Packages

         download all these calculated packages with the Download Manager

Regards

RB

[Former Member]

This is incorrect. You can reach equivalence level while doing the upgrade. It is equ privalence level not pre-requsite level.

PS: Equivalence level is not defined by enhancement pack level alone but you also need to consider target SP level within the target EHP level.

[Former Member]

Pretty simple, applying an enhancement packages is comparable to a release upgrade. So basis will do the upgrade, development has to do SPDD and SPAU and the application conultants have to test functionality after the upgrade (happens on the test system).

The upgrade on the DEV system takes about one week, given you do a downtime minimized upgrade. This means 3-4 days uptime phase and 1 day downtime phase, the speciality on the DEV system is you cannot do any development work during uptime because development will be locked.

Cheers Michael

Edit: be sure to reserve enough time, when you don't have a lot of experience with upgrades in your place. Even setting up a sandbox system to dry run things might be useful.

[former_member188883]

Hi Thiru,

Apart from basis you may need to have ABAP and Functional team for performing SPDD and SPAU adjustments as well as support testing post upgrade.

Ideally it should take 5 - 7 days to complete an upgrade from ECC 6.0 to EHP6 per system.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

We are planning to Upgrade only one ERP system.

1) In this case, Approximately how many abap and Application consultant required for this upgrade?.

2)After DEV upgade,

Is it possible to perform the PRD upgrade  with in Two days down time?.

Thanks

Thiru.

[former_member188883]

Hi Thiru,

1) In this case, Approximately how many abap and Application consultant required for this upgrade?.

Minimum of 1 ABAP consultant is required. Exact number may depend upon total number of custom programs and tables defined in the system.

2)After DEV upgade,
Is it possible to perform the PRD upgrade  with in Two days down time?.

Technically it is possible but not recommended. Before starting upgrade on PRD , you need to ensure the a Production copy ( either sandbox or QAS) has been upgraded and tested well.

This is to ensure that in Production there are no unknow issues which may lead to increase in downtime.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Is it possible to perform the PRD upgrade  with in Two days down time?.

SUM has a new option called Near Zero Downtime, that lets you minimize the downtime required for production (or any system) to just a few hours.  I have used it on copies of our production system and had a downtime of 2 hours as compared to 24 hours needed before.  You might want to check note Note 1678564 - Executing and Monitoring nZDM/SUM to see, if your DB2 version is supported. 

I you can't use nZDM, it really depends on the size of your system, so you should run a test on a copy of production to make sure you know what to expect.