Hardware upgrade + ECC 5.0 Verus Hardware upgrade + ECC 6.0

[Former Member]

Hi all,

We're currently on 32BIT Windows 2000 SQL2000 ECC 5.0. We're considering a hardware/OS upgrade to bring us to 64bit Windows 2003/(Maybe 08) SQL05.

The question is, obviously we'll have to implement our ECC on this new hardware. Should we stick with ECC 5.0 or should we consider a bigger implementation by moving to ECC 6.0?

We do have an ECC 6.0 Upgrade planned next year, and according to our previous record with "all together" HardwareO/SDB+APP Implementations we'd like to think it's better to stick with ECC 5.0 for now and then have the ECC upgrade by itself next year.

What are your thoughts? Would sticking with ECC 5.0 a good idea? Would it save us a lot more time?

Thanks in advance,

Samer

[Former Member · Accepted solution]

Hi,

Mainstream support of ECC 5.0 is going to end on 31.03.2010, going forward you will have to pay extra maintenance charges to SAP.

I think it is worth if you could plan your SAP upgrade along with your h/w and DB upgrade. If your system is non-unicode you need to plan unicode conversion as well.

However if you are planning to take extended maintenance then ofcource your ECC5.0 system will be supported till 31.03.2013. So you can plan your SAP upgrade after 2 year.

Hope this will help you.

Regards,

Sachin Rane.

[Former Member · Accepted solution]

Hi Sachin,

Thank you very much for your thoughts, this will definetlty be considered during planning.

You've touched on an important issue, the unicode conversion. I have few question I'm wondering if you or someone else can comment for me.

My background is Basis, however can you please explain what are all issues that should be covered on Unicode. Few things that come up to my head:

1. How do I know if my system is unicode, non-unicode? Is this a Basis configuration, other than the kernel and the database? Or should I check with our programmers and they'll know?

2. If required.We're also doing a SQL05 upgrade, would that have any effect on a unicode database conversion?

3. What is the normal time frame for a unicode conversion? What are the tools/resources required?

Many thanks in advance,

Samer

[Former Member · Accepted solution]

Everyone,

Please don't mind my first question, just figured how to know if your system is unicode.

http://www.allinterview.com/showanswers/58920.html

[Former Member · Accepted solution]

Hi,

First I want to clear that you Do Not need to go to Unicode as a must during Upgrade, you can keep non Unicode during upgrade and keep working that way if you only use single page code and in fact it is better to move to Unicode after upgrade is done.

If this was my project I would do HW/OS/DB system copy (this is homogeneous system copy and it is very straight forward), then begin my Upgrade project to ECC 6.0 and IF required by the business do the Unicode conversion or viceversa, first UC Conversion and then ECC 6.0 upgrade.

[Former Member · Accepted solution]

Thanks for the thoughts AC. It looks like we might go in this direction:

Project 1:

1. HW/OS/DB system copy.

2. Reinstall ECC 5.0 on the new HW/DB.

Project 2:

1. Unicode Conversion.

Project 3:

1. ECC Upgrade to 6.0

Now in project 1 and per your comments, what kind of work would be required to reimplement ECC 5.0. (Which is what we have now on the older hardware)

Thanks,

Samer

[Former Member · Accepted solution]

Hi,

Basically is after OS and DB is installed in the new HW, then install Central Instance and do a detach-attach database but it is better to get a look at the system copy guide available at service.sap.com/instguides

good luck

[Former Member · Accepted solution]

Hi,

1) Go to system --> status --> here it will show you unicode or not.

Then go to se16 --> put table TCPDB and execute. Find out how many code pages are installed in the system. If it shows more than one then your system is MDMP and if not then it will be single code page.

Your upgrade and unicode conversion will depend on above information.

you better go to following site for unicode and upgrade information

http://service.sap.com/unicode@sap

http://service.sap.com/instguides

2) You can go with all project in single shot using CU&UC method. But here scenario will be more complex.

3) Upgrade and unicode conversion time is depend on your h/w and DB size. better you do the h/w sizing first. You can use SAP quicksizer tool which is available on service market place. Also involve h/w vendor in this excersice.

4) also on sdn you can find case studies for such upgrade, go through it they will give fair idea about the upgrade and unicode conversion.

Hope above information is helpful for you

Regards,

Sachin Rane.

Edited by: Sachin Rane on Mar 3, 2009 7:43 PM

[Former Member · Accepted solution]

Thank you Sachine and AC for your well input. I'll do all studies and get back to you if I have any questions. Anyone else have an input please shoot!

Regards,

Samer

[allaine_tabilin · Accepted solution]

Hi,

Do you also have the details of the modules or add-ons you want to implement (for ECC 5.0 and ECC 6.0)? That would also help on determining the duration you need for implementing either one of them.

Thanks,

Allaine

[Former Member · Accepted solution]

Hi Allaine,

That's a very good question and I wanted to touch on that earlier with VC's comments.

I do know what modules will be required. And to confirm, that would be part of the Central Instance installation VC mentioned above.

Thank you,

Samer

[Former Member · Accepted solution]

HI,

before you will upgrade to ECC 6.0 you have to migrate to new HW - 64bit platform for SR3 installation medias. And on new HW you will just use your current DB, so there is no reimplementation or decision about modules etc. Afterthat go for upgrade, it's not important if straight after migration or later.

Jiri