Merging several non-SAP ERPs into one single SAP ERP

[former_member737518]

Hi guys,

I'm new to SAP and I have a question purely out of curiosity. Let's say you have a manufacturing company which is spread across different countries under a divisional structure and all these divisions have their own product line (segments) and their own ERP system (AX, SAGE etc.). Each ERP could contain thousands of items with multi-level BOMs. And let's say now, you have come to a level where you need to take a strategic decision to merge all these ERPs into a single one and that would be SAP ERP. Does anyone have any insight what would be the extent of such a project in terms of timing? How long it would take to have all these ERPs successfully integrated into SAP and get to the same operational level as they were in the previous ERPs. I'm not looking for a precise answer, I'm more looking to get insights from people that have experienced such implementation. The idea is to get an overview how messy this could be

Please feel free to share any opinion you might have.

[Former Member · Accepted solution]

Hi!

Tipically the Headquarters will contract a company to help during implantation at global level, and other companies (or the same company with offices abroad) to help at local level. First step is quotation and analysis, where they will present a chronogram. Depending on the scope, the size of the company and complexity of operations, I would say that it would take more or less 2 - 6 months. Then the works begin with the BBP (business blue print), where the processes are mapped and the company chooses key users to help on implementation. This should take another half of year. Getting this defined, the consultants start to work on customizing and developments, while the company solves the infrastructure issues and starts with training and procedures. Then there is the final period, with tests including both consultants and key users. I would say that it would take maybe 3 months (again: there are many variance here depending on several factors). In parallel, master data should have been mapped, uploaded and checked. So a formal meeting (called go-non go meeting) take place at high level of IT and direction, and the plug is pulled from the old system to the new. Tipically some problems will be faced in the first days, but consultants will be there to help operational people as part of a standard contract. So we are talking about 1 to 2 years until you get the system running, and probably some more months to people be comfortable with the new system.

Your company also might want to divide the project in sub-projects, with the same steps each one. Let's say that they could start with one plant as pilot, and then make a roll out to other plants after this. It allows to deal with last data and people at time, and increases the experience of central team by learning from previous errors.

The company I work for started with SAP in Europe (where the Headquarters is) and then moved for roll out in Asia, North America and finally South America. Each turn it was smoother and quicker than previous.

Nevertheless, it is a huge effort and it is key to choose the right people and support company to this enterprise. Also keep in mind that mapping processes carefully and checking master data with absolute attention is a must. The bright side during this hard work is that the improvement begins even before the system is on, since you have to look deeply to your business rules, processes and data.

Please let me know if you have other questions (and forgive me if my English is not that good!).

Best regards,

Marcio

[former_member737518]

Thank you for your answer!