cancel
Showing results for 
Search instead for 
Did you mean: 

Can ECC EHP4 fresh installation be done by using copy existing EHP4 system

Former Member
0 Kudos

Hi Gurus,

We installed our sandbox system as ECC 6.0 ABAP Stack only (EHP4 ready installer).Operating system is Windows Server 2008 R1 Standard Edition with MS SQL Server 2008.After that we did EHP4 Upgrade on ABAP Stack.Our system is now ECC6.0 EHP4 ABAP Stack.It took around 12 days for whole activity.

This was time consuming process and we do not expect this much time for Installation of ECC 6.0 EHP4.

We are planning to do Developmenet setup and we want to proceed as follows in order to save time.

1) Take Export of SAP Sandbox system using SAP standard export method used for homogenous system copy(source system) which is not released for customers yet so no configurations in it.

2) Prepare target system by Installing SQL2008 Database on target Devlopment server.

3) Start ECC installation on target system (this is EHP4 ready installer)

4) During Database installation provide export of Sandbox system (taken in step 1) as DB

5) Complete system installation.

This way I will have ECC 6.0 - EHP 4 available with lesser time

any thoughts to this approch.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

You need to know that the export that was taken by you was at the time when functional configuration was done in the system or before the functional team did the configuration.

if the export is before the functional team did any changes the you can proceed further.But if the export is taken after the functional team had made the changes in the system then you can landup in a problem as there can be some changes that you would not want to take in the Dev env. So you will have to spend time in the post refresh steps.

So its better you can calculate the time you need to refresh or go for the installation.

As you are doing the refresh first time you can have certain new issues.

Let me know your comments

Thanks

Rishi Abrol

Answers (3)

Answers (3)

Former Member
0 Kudos

We followed almost the exact process to build our DEV system as the ECC EHP 4 Ready install process is indeed lengthy. We are also planning to do the same thing now with our QA build as we further built on to the DEV build (copied from Sandbox) by adding 21 language imports. This process will save a tremendous amount of work and the SQL db backup was performed prior to any function team members accessing and configuring the system. As the Basis lead, I've proposed this process for all remaining builds (a training system, 2nd DEV, 2nd QA, and PRD). However, management is questioning this as a Best Practice and the supportability of this method by SAP. Does anyone (specifically someone from SAP) know if this process for a PRD build would prevent SAP supportability?

We have 2 other existing ECC landscapes (regional) and 1 was built with this exact same "system copy" installation process while the other was built all from scratch. To date (several years being live) we have not seen any issues or differences between the 2 systems that would be a result of the different installation methods.

Thank you for any feedback on this topic.

Former Member
0 Kudos

Hi David,

A Production system built this way is supported by SAP.

Best Regards,

Matt

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

> We installed our sandbox system as ECC 6.0 ABAP Stack only (EHP4 ready installer).Operating system is Windows Server >2008 R1 Standard Edition with MS SQL Server 2008.After that we did EHP4 Upgrade on ABAP Stack.Our system is now >ECC6.0 EHP4 ABAP Stack.It took around 12 days for whole activity.

Time depends upon how much you optimize parameters when you started upgrade of your EHP4 ready system. Like how much R3trans process, background processes etc, you choose during upgrade. If you will run it by default parameters then it will take more time.

Thanks

Sunny

Former Member
0 Kudos

Hi Greg,

Yes you can do it. We are planning to do the same and SAP is fine with it. However in case you are using it to build production environment it would be a good idea to ensure that the source system is as clean as possible i.e free of transactional,customizing,master data etc.

Regards.

Ruchit Khushu

Former Member
0 Kudos

Thanks all for your replies

It certainly helped me move forward.

Thanks,