Your switch to SAP S/4HANA with msgFIT

The strategy depends largely on the objective of the conversion. The scope of the conversion thus needs to be defined in advance: How many source systems are affected and are being converted to one or more SAP S/4HANA systems? Is only the current data transferred or also the entire history of the data? How high is the process uniformity of the source systems - and are standard processes to be used mainly in the future SAP S/4HANA system?

The msgFIT analysis tool provides answers to these questions and as a result returns a data-supported recommendation for the right conversion strategy: whether migration, blue, brown or green field. After analysis of the source systems, the use of the data, the processes and also the functions is transparent. You can also use the result to compare the processes in order to make a comparison with the potentially used scope items on the basis of S/4HANA.

Am I forgetting something or am I taking unnecessary ballast with me? msgFIT shows you exactly which scope is currently in use and which processes or functions will no longer be needed in the future. msgFIT also shows you the use of transactions and programs, including those developed in-house In addition, after the analysis you will know which
organizational structure is used and can therefore leave out the unused part.

Thus only the part actually used is integrated into the conversion.

Where is the starting point? Which systems are similar and how do you get them on SAP S/4HANA? msgFIT compares your systems and explains exactly in which order you should set up your SAP S/4HANA platform.

Usually, one S/4HANA platform is selected that is supplied with data and processes from the source systems. The order of the ERP systems is determined by the degree of process coverage - the higher the coverage, the earlier the system is transferred.

For APO, EH&S and industry solutions, the functions must be compared with the possibilities of the S/4HANA platform. In this case, the systems that can be transferred and cover a sub-process in the end-2-end process are prioritized. For data warehouse products BW/BO and all front end applications, it will be decisive if a side car strategy is still required – if so the systems will be converted separately to HANA (BW4HANA) – if not, the data must be migrated to the embedded to the embedded BW in S/4HANA (e.g., when switching off APO).

An on-prem solution for production companies and cloud for service and sales companies?
msgFIT analyzes your system and matches the processes to the scope items – you can see exactly whether your project can be implemented in a multi tenant edition (MTE) or in a single tenant edition (STE).

In the case of MTE, you always need the SAP Brand Guardian, which safeguards the feasibility of your processes in an MTE. Owing to the smaller vertical process complexity for service and sales companies, MTE is more suitable here.

For operational purposes that require integration into the shop floor, an STE or an on-prem solution may be more suitable.

Which country are you starting with? If the country strategy is not dictated by the operational purpose, the correct sequence for the roll-out strategy must be determined.

The cloud/non-cloud strategy must be defined beforehand, because, for example, not all 
countries can be localized in the MTE. After taking external influences into account (e.g., equipping a country with a new system within a certain time frame), the question must be answered as to whether a pilot should generally be implemented before the main locations.

msgFIT searches for the best pilot, namely the location that represents the group complexity in miniature. Thus no political solution is necessary.

Which data would you like to take with you to your new S/4HANA platform? msgFIT analyzes your system and explains in detail which functions are used in your system. Based on the usage and the definition of which processes you will use in the future, you can exactly choose which data you want to use in the future.

A data migration usually includes historical data. A cutover usually transfers only the data that is necessary for current operation. Which historical data is correctly transferred to a sidecar BW4HANA in the scenario must be taken into account when considering the reporting requirements?

In any case, the data to be used in the analytical apps must be transferred to the embedded BW in the S/4HANA platform.