Merging a SAP System with another SAP System

[Former Member]

Hi All,

We have requirement to merge one SAP system with another SAP system. In this context we have to migrate all data ( control, master and transaction data) from one system to another system also we need to copy all custom programs, custom routines user exits, routines etc..Without any discrepancy to the existing both systems process.

If anyone did this kind of project earlier please let me know what could be the best approach and how to go about it. I would appreciate if you would share any documentation on the same.

I know SAP SLO (System landscape Optimizer) tool is there for the same but we are not going use that in our project.

Thanks in advance.

Regards,

Venkat

[Former Member]

Are you sure there is a way to do this? Imagine how two separate systems can be combined into one without having number range issues as well as not having code related issues with any of the user exits and notes that are implemented in one not in the other etc?

You can migrate data but they will get new numbers, but I don't know how you intend to synchronize customizing data and control tables that you were talking about.

What is the reason behind this merger?

[Former Member]

Hi Srinivas,

Thanks for your reply.

Yes as you said there will be number range issues we are going to create new numbers for that. The reason behind this is we have only three plants which are running on this system also this system is on 4.6c and we need to upgrade and to avoid support cost etc.. Other system is on ECC 6.0 also some of key users using the both system to avoid this also one reason. User exits, standard sap program changes, oss notes etc. are still analysis phase.

We have to do it definitely for long run cost costing. We did the some of separations in the similar line earlier but now itu2019s reverse. So let me know if any best approaches comes across to your mind.

Regards

Venkat

[Former Member]

>

> Hi Srinivas, 
> 
> Thanks for your reply. 
> Yes as you said there will be number range issues we are going to create new numbers for that. The reason behind this is we have only three plants which are running on this system also this system is on 4.6c  and we need to upgrade and to avoid support cost etc.. Other system is on ECC 6.0 also some of key users using the both system to avoid this also one reason. User exits, standard sap program changes, oss notes etc. are still analysis phase.
> We have to do it definitely for long run cost costing. We did the some of separations in the similar line earlier but now itu2019s reverse. So let me know if any best approaches comes across to your mind.
> 
> Regards
> Venkat

This is a gigantic project. I think no one in here can give you all aspects of things you wil have to consider, since some of them may be specific to your business process ... but maybe i can add my 0,02u20AC:

in order to get a faster pace for the repository-adjustment, why don't you make a copy of your 4.6C system to a sandbox and run an upgrade to ECC 6.0 over it. at least you would get the chance to see what pops up in SPAU and SPAM, so could get an overview where you would have to adapt things to make them fit a.) to a ECC 6.0 system and b.) to your 'other' system. it will not be complete, but a start ...

for the migration. do it plant by plant (i assume, all plants belong to different company codes ... otherwise this tactic might not work), and break the objects down to business processes. if you have charts of your business process, you might be able to migrate process by process, enabling smaller 'slices' of datatransfer.

consider setting up an ALE distribution for objects, this might help you transfer data once (and once only!) when all the customizing and configuration have been done. an example could be: material master ... since you might have the same material numbers in both systems already, you would have to 'migrate' the plant-level data only. if you setup an ALE-distribution for MATMAS from 4.6C -> ECC 6.0 and create changepointers, you could transfer only the 'missing' parts.

if i can think of some more advice, i'll come back to this thread ...

[Former Member]

Hi Mylene,

Thanks yeah data belongs to different plants and different company codes.

Regards,

Venkat

[Former Member]

things to consider:

the legal implications in the country you work in for 'carve in' projects. make your CFO hunt down the information you need. for example: do you have to do a balance sheet on the 4.6c system before the merge and one on the ECC-system after the merge? do you need official approval of those?

archiving: the less data to migrate, the better. of course, all with regard to legal implications. careful with archiving user data and financially relevant data, there might be a restriction that you have to keep them for several years.

even if you do not archive - you cannot shutdown the 4.6c system after the merge and forget about it ... you will have to come up with some solution there ... for example: here in this country you have to store financial data (balance etc.) for 10 years. at least in some digital form, so that mostly calls for DART.

i am not about to publish my e-mail address in SDN but if you want to contact me anytime during that project, PM thx4allthefish at www.sapfans.com/forums.

take care, good luck.

[Former Member]

Do they need to all be in the same client? It might simplify things if you upgraded the 46C system to ECC6 and then copied it over as a new client to the existing ECC6 system. You'd still need to deal with any cross-client setting conflicts...

[Former Member]

Thanks to all for their valuable inputs in this regard. Now we completed this task.

thanks,

Venkat

[Former Member]

Hi Venkat

Did you use SLO Client Merge solution to merge the SAP systems. We are palnning to do the same and it would be great if you can share your approach.

RP

[prakash_bhosale2]

Hi Venkat,

Need your help in understanding the approach built for merging 2 sap systems. I am working on a project to merge R4.7 system to SAP ECC.

Could you please share your email id for further discussions.

Thanks in advance.

Warm Regards,

Prakash

[sureshsanka]

Hi Venkat,

I am working on a project to merge sap hr system with sap fi system and now both the systems are on the same release EHP7. Now both the systems are connected through an ALE to synchronize master data objects and budget information and to transfer payroll documents.

I need your help in understanding the solution approach followed for merging two sap systems.

Could you please share your email id for further discussion.

Thanks in advance.

Thanks,

Suresh

[Former Member]

Can you please tell us the approach you used in order to implement this? We're also planning to do this kind of implementation on 2 SAP ECC systems.

Thanks!

Hidee