Our evaluation of your answers

Conversion analysis

With the abat Conversion Accelerator, we have developed a methodology that clearly structures and simplifies all the necessary steps for the planned conversion. All relevant points are checked, and the existing SAP system is analyzed regarding technical and functional feasibility. All activities are collected in a backlog and ordered chronologically. In this way, the effort required for a system conversion can be defined very precisely. The project becomes "tangible", and the subsequent conversion can be implemented in a targeted and accelerated manner.

Identification of the Simplification Items

Simplification items can be used to check the possibility of switching to S/4HANA, indicating the effort required. In addition, the technical delta between the current release and the target release is shown. The Readiness Check, i.e. the higher-level service, already provides initial conclusions as to which processes are being used and in which areas a return to the SAP standard is possible based on best practice processes. This also includes the identification of added value. The list of simplification items can also form the basis for further activities such as the derivation of change and training measures.

Custom Code Check

To ensure the continued usability of existing processes and enhancements in the system, customer-specific code adjustments were to be implemented as part of the system conversion. abat has extended the SAP standard Custom Code Check with additional checks. This results in opportunities to optimize existing solutions. The result shows in which areas simplifications are possible, e.g., on return to the SAP standard or the simplified data model.

SAP Fiori Recommendation Report

The report checks in SAP ECC as well as S/4HANA systems which transactions were frequently used. This evaluation provides a recommendation as to which Fiori standard apps cover the process scope examined.

The result of this evaluation also provides the required standard SAP roles. With the help of these roles, the required content can be fully activated via Fiori Rapid Activation.

We recommend this procedure for Rapid Activation sandbox systems to enable a look and feel of the new interfaces at an early stage. In addition, this automatically determines for which of the transactions used there is already a UI5 interface and which transactions are still called from the SAP GUI.

We do not recommend activating all apps from the library, since unused apps might be activated as well, which leads to a confusing and in performant app landscape.

Migration Analysis

The transfer of existing data is a fundamental part of the introduction of S/4HANA. The question can also arise as to how a streamlining of the previous system in the system conversion approach is possible. abat provides clarity as part of the migration analysis as to which data is necessary for the changeover to S/4HANA. As part of the analysis, options and tools for migration are jointly identified. Another component is handling archiving data that is no longer required for direct access. Through early decisions and an optimal strategy, the project duration can be shortened, complexity in the project reduced and costs reduced. As a result, you get the security to deal with your data.

Process Innovation Check

Future success is essentially dependent on how much innovation a company dares to undertake. Especially in the context of digital transformation and rapid changes, in which entire markets are realigning themselves through disruption. The innovation building blocks of abat help, give security and provide ideas to maintain the right mix of change and innovation as well as stability from the tried and tested. AI-supported drone inventory, chatbot support in the sales process and Robotic Process Automation (RPA) are just a few examples here. 

Risk/potential Analysis

As part of the definition of an overall IT strategy, we also recommend performing a risk/potential analysis. The Business Scenario Recommendations Report (BSR Report) and the SAP Readiness Check for S/4HANA, which are run on the current ECC production system, serve as a basis. Based on the transactions currently used in ECC, the BSR Report shows the added value for processes and business scenarios through S/4HANA.

The Readiness Check shows all functionalities in the existing ECC system that have changed, been omitted or optimized in S/4HANA. It also lists the points in the customer's own programs that need to be adapted during a transition to S/4HANA.

For brownfield transitions, the Readiness Check is essential to make the necessary adjustments to the customer's own programming or to plan for the consideration of the changed functions.
In the case of a greenfield transition or in the hybrid approach, the check is used to divide the necessary major changes and adjustments in processes and Z programs into risk classes in the risk analysis.

Evaluation Matrix

As a basis for creating a project plan and a proposal for the project approach and an implementation variant, workshops are held with SAP process experts. The customer's requirements are collected and various alternatives for the introduction of S/4HANA are presented based on the requirements. A criteria catalog is created to evaluate these alternatives. Here, individual criteria that come into play in the decision are categorized, weighted, and evaluated together with the customer. Based on the criteria catalog, abat creates a quantitative basis for decision-making, evaluating the various alternatives. The goal is to identify the optimal transition strategy for the customer, i.e., a strategy that is best suited to the customer's individual initial situation and requirements.

Knowledge Transfer

For a successful S/4HANA transition, it is important to build up the relevant know-how required for this project phase.This knowledgeadds value to any further discussion on the subject of S/4HANA.
In the first step, the S/4HANA basics aretaught, which  clarifies the scope of the planned project and the associated opportunities (for standardization, innovations, synergies, etc.). At the same time, reservations are to be discussed and eliminated in dialog.
In the second part, the potential of S/4HANA is presented. With the solution, SAP promises the path to the "Intelligent Enterprise". abat presents corresponding concepts from the areas of Internet of Things, Fiori interfaces and operational reporting.

Scoping

For the process analysis, SAP's best practice processes for an S/4HANA implementation are used as a basis. As part of the preliminary analysis, the processes per module are discussed at level 2 (grouping of similar processes, broken down by area of responsibility or tasks), if necessary, in more detail. The goal is to identify the processes that are relevant for the prototype (scoping). In the follow-up, end-to-end processes that are required for the prototype are then compiled and any additional customizing requirements that may be necessary for building a prototype are identified. These processes are presented to the customer, in fit-to-standard workshops, as part of a system demo.

System Demo

In a look-and-feel approach, SAP's best-practice processes, supplemented by additional customizing settings, if necessary, are presented as a prototype in specialist workshops for processes selected with the customer. They form the basis for the fit-to-standard analysis, which in turn describes differences between the SAP best-practice processes and the target customer processes.

Prototyping

Based on SAP's best practice processes and enriched by additional abat best practice processes as well as configurations, master and transaction data, a prototype is created in the system. Due to the early inclusion of the system, the added values are identified at an early stage. Likewise, the question "What is the effort of a system conversation for our specific system?" or "What added values does S/4HANA offer me in my process?" can be answered directly, for example. The prototype can be used as an accelerator for the downstream project phases.

Fit-to-Standard

Methodically, the system demo results of the SAP best practice processes are documented by means of a fit-to-standard analysis. It ensures the fit, i.e., the accuracy of fit of the customer processes to the S/4HANA standard process shown. Specifically, the functionality is compared for each process. If there is a discrepancy between the standard process in the prototype and the target process desired by the customer, this is described as a gap. Gaps are assigned to a WRICEF category in parallel. The gaps and the proposedsolutions are described in the preliminary study. An initial effort estimate per gap is made using a T-shirt sizing.

Customized

Whether sizing the system landscape, a value check, identifying additional add-ons or end-2-end process solutions or your individual questions. Based on many successfully S/4HANA transformations, we know that every company and initial situation is different. We do justice to this with our customized building blocks for successful conversion in S/4HANA transformation projects. Together with you, we define the scope and content of the transformation.