A roadmap for the IT departments of SMEs
Business One as a system for global players
With SAP Business One, SAP has rounded off its portfolio and not only created an ERP system (SAP ERP) for global players, i.e. corporations, but has also been offering a powerful ERP system for small and medium-sized enterprises since 2002, which is now used in more than 40 countries.
In the luggage brings SAP Business One the required integration platform B1if with, which among other Add ons is supplied free of charge. However, this integration platform is not only used for integration in SAP ERP, but also provides the Connection to third-party applicationsthat one cannot or does not want to replace.
Integration projects as a challenge
In the Group environment, the deployment of SAP Business One in subsidiaries and branches with more than 20,000 installations worldwide. Nevertheless Integration and rollout projects the IT departments medium-sized companies always face great challenges. Especially with regard to cost and time frames, the basic prerequisite for the success of such projects is the Determining, checking, answering and - last but not least - documenting of complex issues and solutions. The solid relationship of trust between the client and the consultancy firm is fundamentally important for the success of the project.
So what should you basically consider in order to be well prepared for the implementation of ERP projects?
At the beginning there is the target question
At the beginning one must sensible use principles define and formulate the requirements of the new ERP system. It applies Clarity about the project goal to create. Questions like the following serve to fence off the field of action: Which ERP system does the parent company use? Do you want to replace another legacy system? Which subsidiaries are to be provided with an ERP system?
At the same time, only then is the basis for deciding whether SAP ERP or SAP Business One should be introduced in the subsidiary. If the subsidiaries are complex, a categorisation workshop is recommended. During its course the Condition of the master data determined and set, How and to what extent to harmonise them are. If necessary, a detailed master data concept will be prepared in any case before the start of the project.
Now and later: Analysis and concept
Once the initial situation has been worked out, the next step is to determine the necessary Total licence requirement per licence type to be calculated. Depending on the location of the server, it is necessary to clarify whether licenses Global or local must or can be acquired. This applies not only to the software to be introduced, but also to the operating systems required for the servers and the workstations to be connected. For answers to technical questions, the following are required As-is analysis and target concept therefore indispensable! To avoid later Avoid cost explosionsmaster data harmonisation and the master data to be mapped. processes also included in the analysis and conception.
In addition, it must be clarified which programmes and systems will be connected to the future integration platform, which intercompany processes which master data should be made available to the individual subsidiaries and which evaluation tools should be used.
Here we go!
The task now is to use the knowledge gained to be put together before the start of the project and in a Specifications to document that also Country-specific legal requirements for financial accounting taken into account. The Specifications is the basis for the time, technical and resource-related project plan including go-live dates.
It accompanies the project work from the development of the prototype, the so-called template, which covers all identical processes/functionalitiesThe system is then rolled out to the company's offices around the world, where country-specific adjustments are made to the system.
This approach very quickly shows Savings potential and guarantees reliable success also larger international projects.