- S/4HANA code remediation is one of the most critical parts of S/4HANA implementations.
- In this article, we will explain why it is important to pull the remediation effort forward.
S/4HANA means radical changes in the code that companies have developed. In this article, we will make the proposal that companies that plan to move to S/4HANA should not wait until the implementation to perform the code remediation analysis.
The Problem Getting Accurate Information on S/4HANA Code Remediation
SAP has published its perspective on remediating code for S/4HANA. Both SAP has its consulting partners have consistently underrepresented the complexity involved in code remediation to customers in order to make the migration to S/4HANA seem to be less work and less cost than it actually is. In this article, we review the material on remediation without any SAP bias.
The Confusing Aspects of S/4HANA Code Remediation
SAP’s explanations of the process and how to use the tools for S/4HANA code remediation are extremely confusing and requires determining a path independent of SAP.
The Major Factors in S/4HANA Code Remediation
S/4HANA means using HANA and this means that the tables change, that code that was originally written to be portable between databases now has to be altered for only HANA. It means that SQL must change. Overall, S/4HANA upgrades will be the most extensive and trouble-prone code remediations that an SAP customer will normally have faced (for their SAP systems at least).
Code Remediation Analysis Versus Code Remediation
Code remediation analysis is different than actually performing the code remediation. The code remediation analysis or CRA is simply the process of determining what items need to be changed and then planning the work effort and even the resourcing. One typically attempts to obtain a list of code items to be remediated, and then determining the severity of most of the remediations, and then applying an appropriate time estimate (which then goes to budget) for each remediation. This can be done without owning any S/4HANA software because the rules of how the code needs to be changed are known.
The Approach of SAP and their Consulting Partners
SAP and SAP consulting companies typically want this analysis to be pushed into the implementation when they are firmly in control of the project. The strategy is to keep the unappealing details away from the customer until they have signed so that it reduces the resistance on the part of the customer to move to S/4HANA or to move to S/4HANA in a particular timeframe.
Rather than listening to SAP or their compliant consulting partner and perform the code remediation into the project it actually makes much more sense to pull the remediation analysis forward so that the implementing company can incorporate the remediation estimate into the project plan before consultants or SAP hit the project in force.
Getting to the Detail of TCO
The Mechanics of TCO
- Understand why you need to look at TCO and not just ROI when making your purchasing decision.
- Discover how an application, which at first glance may seem inexpensive when compared to its competition, could end up being more costly in the long run.
- Gain an in-depth understanding of the cost, categories to include in an accurate and complete TCO analysis.
- Learn why ERP systems are not a significant investment, based on their TCO.
- Find out how to recognize and avoid superficial, incomplete or incorrect TCO analyses that could negatively impact your software purchase decision.
- Appreciate the importance and cost-effectiveness of a TCO audit.
- Learn how SCM Focus can provide you with unbiased and well-researched TCO analyses to assist you in your software selection.
- Chapter 1: Introduction
- Chapter 2: The Basics of TCO
- Chapter 3: The State of Enterprise TCO
- Chapter 4: ERP: The Multi-Billion Dollar TCO Analysis Failure
- Chapter 5: The TCO Method Used by Software Decisions
- Chapter 6: Using TCO for Better Decision Making