Skip to Content
avatar image
Former Member

Merging a SAP System with another SAP System

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Sep 23, 2009 at 09:29 PM

    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?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member 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.

  • avatar image
    Former Member
    Sep 24, 2009 at 05:57 PM

    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...

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 15, 2010 at 02:08 PM

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

    thanks,

    Venkat

    Add comment
    10|10000 characters needed characters exceeded

    • 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