Conversion, conversion or redesign - the word "conversion" means all of these things. And that's exactly what it's all about: Most companies will be facing a system conversion in the next few years - from old software to a modern ERP system such as SAP S/4HANA. This is not only important in order to remain competitive, but also to be fit for the digitization requirements of the coming years. The crux of the matter: this is a project that takes a lot of time and should be approached in a structured manner. "Wait and see" is therefore not a good method - especially not because consultants' resources are limited and a company risks being overtaken by the competition. It is therefore better to get into action as early as possible and look for an optimal partner for conversion. And this is where we come in, if you like.

The result is a precise schedule that states what needs to be done, when and in what form. But whether it's full support or individual work packages, the fact is that time is of the essence. This is because the entire process - from planning to implementation - takes an average of 1 to 2 years. So if you want to stay up-to-date, it's a good idea to start the conversion process as soon as possible.

A second development that is gaining momentum is the fact that there is an increasing symbiosis between SAP and Microsoft technology. The reasons for this are complex - whether different functionalities, innovations, costs or goals. SAP and Microsoft have long recognized this and are therefore working together intensively to develop solutions that facilitate this interaction. The following scenario is therefore becoming increasingly common:

But it is also about the database - here too, companies may work with a mix of solutions. For example, in addition to SAP as the ERP foundation, there are also CRM systems, non-SAP products or even Access databases. All of these must be connected in a meaningful way to ensure smooth integration and consistent reporting. This requires a layer, a so-called data layer, which links both, for example SAP and Microsoft technology. At the same time, the desired output must not be ignored. If, for example, the reporting tool Power BI® from Microsoft is to provide the analysis, a strong focus on Microsoft must already be placed in the integration layer. If, on the other hand, only SAP products are used, such a layer is often not absolutely necessary. So it's a tricky project that requires a lot of know-how.

We are responding to this trend by offering a data platform strategy. The aim of this is to get the best of both worlds for the customer. We take a structured approach, make decisions based on the situation and create a customized solution that suits the company. Our advantage? The scc team is at home in both worlds and therefore has in-depth knowledge of both SAP and Microsoft. This enables an optimal symbiosis that takes all framework conditions and wishes into account.

A third development is called sustainability. On the one hand, it is making itself felt in the private sphere, with more and more people questioning their actions in relation to environmental and social aspects. At the same time, it is influencing the economic context. This is increasingly reflected in legal frameworks and conditions, both at national and especially at EU level. In addition, more and more members of Generation Z are looking at their employer's commitment to sustainability when choosing an employer. This fact alone makes it impossible for companies to ignore the issue in order to avoid exacerbating the already difficult search for skilled workers. And then there are customers who want to know exactly where and under what conditions products are manufactured. It is therefore essential for companies to position themselves well here.

But in recent years, a veritable jungle of laws, tasks and opportunities has emerged in this regard. And many can literally no longer see the wood for the trees. Not only is the EU taxonomy changing the framework conditions for annual reports, but it is also necessary to analyze and reduce the footprint of products or comply with the Supply Chain Due Diligence Act. Tools have been created for many of these issues, but most companies despair before they even start: when it comes to dealing with the issue of sustainability. A scenario that we know well. And this is exactly where we come in with our "Sustainability Discovery Workshop".

However, we do not start with a presentation of possible tools, but we start well in advance. This means that the first step is to define the rough framework conditions. In the second, we break the whole thing down into specific goals and challenges or tasks. Because it is also about knowing what you have to do specifically to get to a certain point. And this is linked to the question: what database is needed for this? Concrete tools are only discussed in the final step.