Why It Is Important to Pull Forward S/4HANA Code Remediation

Executive Summary

  • 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.

Financial Disclosure

Financial Bias Disclosure

Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.

S/4HANA Implementation Research

We offer the most accurate and detailed research into S/4HANA and its implementation history. It is information not available anywhere else and is critical correctly interpreting S/4HANA, as well as moderating against massive amounts of inaccurate information pushed by SAP and their financially biased consulting ecosystem.

Select the description that best matches you.

Option #1: Do You Work in Sales for a Vendor?

See this link for an explanation to sales teams.

Option #2: Do You Work for an Investment Entity that Covers SAP?

See this link for an explanation for investment entities. 

Option #3: Are You a Buyer Evaluating S/4HANA?

For companies evaluating S/4HANA for purchase. See this link for an explanation to software buyers

Search Our Other S/4HANA Content


TCO Book



Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making

Getting to the Detail of TCO

One aspect of making a software purchasing decision is to compare the Total Cost of Ownership, or TCO, of the applications under consideration: what will the software cost you over its lifespan? But most companies don’t understand what dollar amounts to include in the TCO analysis or where to source these figures, or, if using TCO studies produced by consulting and IT analyst firms, how the TCO amounts were calculated and how to compare TCO across applications.

The Mechanics of TCO

Not only will this book help you appreciate the mechanics of TCO, but you will also gain insight as to the importance of TCO and understand how to strip away the biases and outside influences to make a real TCO comparison between applications.
By reading this book you will:
  • 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