Contact
- Let’s connect!
- +49 931 784957-25
- hello@ososoft.de
- Kontaktformular
The preliminary analysis of an SAP transformation is the first important step for the subsequent SAP implementation. This is where the concrete course is laid for a clean, targeted and as smooth as possible implementation of SAP S/4HANA.
We use established procedures and SAP tools, such as Adoption Starter Engagement, SAP Activate and the SAP Readiness Check.
In addition, we offer the S4T Analyzer, a specially developed tool that is the perfect complement to the SAP Readiness Check. The S4T Analyzer stands out in particular due to its even closer technical integration compared to the Readiness Check. For example, it is possible to jump directly into the coding, carry out where-used lists and carry out tracing. In addition, interfaces, jobs and authorizations are also analyzed and displayed on an attractive, graphical Fiori interface. You can find details on the solution page of our S4T tool suite .
As part of a comprehensive preliminary analysis, you should also think about which system changes you can implement in advance of an S/4HANA transformation. There are a few options here:
SAP Business Partner
Dissolve your existing debtor/creditor structure in R/3 and create one of the foundations for S/4HANA with the introduction of the SAP Business Partner.
The new General Ledger
With the new General Ledger, you create a closer integration of internal and external accounting and thus take another obligatory step towards S/4HANA.
The new Material Ledger
In addition to managing parallel currencies/valuations, the new material ledger also enables exact actual cost accounting.
Setting up the Fiori infrastructure
With the Fiori interface, SAP creates a completely new and modern interface design that is much better tailored to the wishes and needs of SAP users.
Switching to modern forms
Use Adobe Forms to upgrade your old forms based on SAPscript or Smart Forms to the latest SAP form technologies.
If you now consider all the aspects listed and put them together in an overall context, a clear picture of the ideal transformation approach emerges. These are the following:
Improved performance
The project implementation in the S/4HANA transformation is a major undertaking and a challenge that should not be underestimated. Problems and errors can arise at various points throughout the entire process, which can have devastating consequences. In order to avoid exactly this and reduce the risk of implementation to a fraction, we carry out the relevant projects with great care - but also following our tried and tested strategies.
The first step is to choose the migration approach that is right for you.
Once the right migration approach has been found, the actual implementation can begin. The key here is to be flexible, but still proceed strategically and with a holistic overview of the project. To achieve this, we have developed our very own project methodology, an agile, iterative approach - our S/4HANA transformation roadmap .
The focus here is on clear results and documents at the end of each phase. The iterative processes also keep the project flexible and adaptable.
In this first phase of our project process, we get involved in the project with the entire team. To do this, we divide the introduction into meaningful sub-projects (e.g. country rollouts) and together determine the key people in program and project management.
The aim of this phase is for the project to start with all the data required at this point in time. The people involved in the project are informed and have received all the information they need at the start. Initial structures have been created and the further course of events has been defined. The basis for a successful project has been laid.
For us, analysis and preparation always come first. This is the only way that further work can be built on this solid foundation and carried out successfully. In this phase, we hold workshops to analyze all relevant company processes. We also analyze the current architecture and define the target architecture based on this.
Using custom code and S/4Readiness analyses as well as simplification checks, we check how much in-house development is available in the system and how “ready” the system is for the upcoming transformation.
Once the previous phase is complete, planning and designing the iteration can begin. This involves planning the agile sprints and teams, as well as the effort and capacities. If new requirements have arisen or existing ones have changed, this is planned. In general, ongoing monitoring and adjustment of the sprint planning is taken into account.
Change management measures, integrative and functional tests and the migration itself are also planned and quality criteria and measures are defined.
The PoC phase shows that the project is feasible. To do this, processes are set up as prototypes based on S/4HANA best practices and tested with individual test cases and, if necessary, mass data. In addition, workshops are held to review the processes together with the specialist departments. S/4HANA-specific basic technologies such as BRF+, Adobe Document Services and SAP Fiori are integrated and a fit-gap analysis is carried out to check whether there are still gaps in the project.
The aim of this phase is to reach the PoC milestone. This milestone marks the point in time at which the fundamental feasibility of a project is proven.
The three previous phases confirmed the feasibility and, based on all analyses, precisely designed the implementation. Now the actual implementation can begin: the processes are customized on the customer's SAP system and thus adapted precisely to the requirements, and any outstanding requirements are covered by individual developments. The migration is also carried out. All tests are carried out to check the system that has been set up in this way. At the end, the acceptance workshops for the processes and process strands follow together with the specialist departments.
The goal is a running system that meets the customer's requirements and which trained end users can use safely.
Once the SAP system has been set up, the GoLive can now follow. This may also include cut-over planning with possible fallback scenarios. Once the entire data migration process has been tested and the data has been migrated from R/3 to S/4, the GoLive can be carried out.
Incident management is then set up and the hypercare part is transferred.
After this project, ongoing support and Application Management Service (AMS) is provided. In addition, the project is gradually handed over to the client's organization. Once such a cycle has been completed, the next project cycle can begin. This means that all sub-areas can be introduced successfully and with little risk.
We have also developed an internal project guide to provide further support throughout the entire project. This contains important information on the phases and various SAP modules and sub-areas of the transformation. This means that introducing S/4HANA with us at your side is not just a first attempt, but rather a well-developed, proven strategy with a high guarantee of success and low risk.
