Skip to Content
author's profile photo Former Member
Former Member

Cutover from SAP to SAP

Hi All,

I have a situation where a company is taking over another company and they both are currently using SAP.

In terms of data migration, what are the important details that we would need to consider as far as Materials Management is concerned?

Are there any tools for SAP to SAP data migration?

I am wondering if there are any separate strategies available for SAP to SAP transfer, compared to the usual case of old non SAP system to SAP system cutover.

Any help would be much appreciated.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Apr 24, 2011 at 04:42 PM

    A SAP to SAP migration is often underestimated, because you think that both system are using the same tables and structures.

    I made the expirience that it is much more complicated than replacing any other legacy system, because you don't come with a better system replacing a weak old one. Both companies are using a good sofware and want keep their way of running it.

    In migration of legacy system data you map one or 2 dozen fields for a material master and can then focus on the migration.

    in SAP to SAP you usually map any field (hundreds more), and you will see values in fields you never thought about and which are or became even unknown for the consultants running this SAP system.

    Technically it is in some parts different to other migrations, instead of downloads to Excel and then loading with LSMW from Excel, you can directly send data via ALE with IDOCs to a file, you then use this file as source for your LSMW, Pretty easy if you then use the same IDOC to post the data to your SAP, so source and target structure are equal, and can easily be mapped.

    The most difficult part was always content in fields you did never expect to have some.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 25, 2011 at 01:48 AM

    Before the actual migration, you need a proper Business Blueprint (or similar documentation) explaining the new process and conversion) 'in as much detail as possible'. No different than any other implementation.

    This needs to reconcile:

    - difference in processes and functionality used

    - master data (e.g. number ranges, length of material master)

    - org. structure (company codes, plants etc.)

    The advantage of migrating SAP to SAP is more on the change management side - users know how to use SAP and (we hope!) understand the concepts and terminolgy.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.