Skip to Content

Best Practice Merge of companies Plant Maintenance Master Data

Hello my estimated Consultants,

I have some weeks working in merge of companies. The objective is to merge company code 0001 center A001 and pass all the operation into 0002 center B001.

Actually they are working in center A001 with PM.

So, I have two scenarios for master data treatment, and I'would like to know which is the nearest of the best practice?

1.- Based in modify with LSMW some fields with 0002 company code information and create some other new (We know that there are some MD that can´t be modified with new parameters):

-Modify Equipment (FL, Company Code, Planner Group, Center, etc..)

-Modify some fields of maintenance plans

-Create new functional locations

-Create new task lists (based on the old)

-Modify Items, put the new number of task list (Planner center, planner group, work center, etc)

-Create new BOMs (based on the old)

-Measurement points and it documents don´t need any modification

2.-Base in create new all the master data

-New Equipments

-New Maintenace plans

-New FL

-New Items

-New task list

-New BOM´s

-Measurement point and it documents, create new based in the old.

I already review with FI consultants and they don´t have any problem with the options, assets & equipment integration is not operating .

I was thinking the best idea is option 1, because you get tractability of the maintenance record, but in the other hand maybe is a cleaner work to create it new. Could you tell me which one is the best option in your opinion? Why? Should I consider something special?

Since know really grateful,

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 28, 2017 at 04:48 PM


    I think you are thinking through this well. By modifying, you get traceability. Creating all new would be a cleaner cutover, but also have obstacles.

    I would go the modify route, especially for Equipment, Maintenance Plans, and Measurement Points/Documents. This history is important for Reliability and Maintenance Analysis.

    I suspect that Finance will want the financial settlement postings from the Work Orders to have a defined cutover date (only in company 0002 after Oct 1st, for example). Consider how you will handle the Open Orders. As a minimum, you will need to have settled all the costs from the Orders, before changing the Co. Code (and settlement object). If you need to close orders and create new ones, you could do manual calls from the maintenance plans.

    Open Notifications have no financials, but otherwise need to be considered like the open orders.

    Will you be able to take the system away from the users for a day to make the changes? The Creating New route would allow you to create all, except the open orders and notifications before the defined cutover date.

    Obviously, with either option, test each of the LSMW and the full set of changes, including functional testing after completing the changes.



    Add comment
    10|10000 characters needed characters exceeded

    • Carlos, sounds like you are on the right path.

      See this blog for making mass changes on Equipment from IE05:

      You will only know the cutover duration needed when you test it. The Create tasks in the modify route can be done before the cutover (with a freeze on changes by the users).

      Help would include getting authorization to create LSMWs (or someone else to create them) to modify the Plans, Task Lists, and maybe the Equipment.

      Good Luck!