The Evidence That The S/4HANA Suite Missed Its Release Deadlines

Executive Summary

  • SAP missed their deadlines no S/4HANA releases.
  • We provide the evidence for this missed deadline.


During the review process for the S/4HANA implementation research, the topic was brought up that if SAP did not have clear dates on the release of the overall EM suite, how can it be proposed that S/4HANA missed its deadlines.

SAP S/4Roadmap

Here is a published roadmap from SAP on S/4HANA from the publication SAP S/4HANA Enterprise Management Introduction and Innovations for extended Supply Chain.

In this slide from SAP, it shows Simple Finance (now Finance) was to be released in 2014, but that deadline appears to have slipped and Finance was released and generally discussed in February 2015. In fact, the official release date is a bit hazy. The is a SAP article on SAP’s site (which I have footnoted) that show S/4HANA was released in early February. There is an article about S/4HANA being “launched” in June 2014 at SAPPHIRE, but that is not necessarily the same thing as being released. Most likely that was a convenient time to give people an advanced view of S/4HANA. Certainly, in 2014 there would have been almost no S/4HANA Finance implementations. 

However, in this slide, SAP is predicting S/4HANA as a suite will be released in 2015. The plan was always to introduce the Finance module first, and for the rest of the suite to follow shortly after. This is the message that was delivered to account after account, telling customers that they should jump on Finance, and by the time they had implemented Finance, the entire suite would be ready to implement. It is now 1/3 of the way through 2017 and S/4HANA is still not a complete product. 

This is the message that was delivered to account after account, telling customers that they should jump on Finance, and by the time they had implemented Finance, the entire suite would be ready to implement. It is now 1/3 of the way through 2017 and S/4HANA is still not a complete product.

The question here is how great is SAP’s forecast inaccuracy.

How different was what occurred from what SAP said would happen?

Well, if S/4HANA was to be introduced in 2015, and S/4HANA is still not complete two years later, then we can’t say by how large of a margin SAP missed its deadlines.

It can only be said when S/4HANA as a suite is a complete. SAP is misleading customers by stating that S/4HANA is becoming incrementally more complete with each release, but obviously, that makes no sense. Completion is when the functionality within each of the modules is complete. It is quite possible that SAP could have completed another module of S/4HANA by now, or in the past if it had applied its development resources to just that module. However, SAP has chosen to develop all the modules incrementally.

Furthermore, it must be considered that SAP never stated that S/4HANA would be developed incrementally (as S/4HANA is currently being developed). Currently, we are awash in things like Simplification Lists, and various versions of S/4HANA that are incrementally developed versions of S/4HANA. But that was not SAP’s messaging in 2014. The proposal of SAP was that the new ERP system would be introduced int two phases. Finance in 2014 (in a complete form) and then the rest of the suite in 2015 in a complete form.

State of S/4HANA Finance

In April of 2016 Dennis Howlett of Diginomica has the following to say about the state of S/4HANA.

“The free S/4 HANA trials are available, I’ve tried some of the cloud modules but if I’m candid, they’re a tad anemic and barely qualify as modern. I poked around in the financials and the marketing module the last day or so and found that while holding promise, SAP hasn’t taken advantage of modern idioms to present a truly compelling offering. Asking me to select a company by its number and not its name for instance seems arcane. Asking me to name product segments with underscores between names is geeky and requires extra thinking.

Taken together, S/4 HANA must be viewed as a work in progress. On the upcoming earnings call, I am hoping that SAP will provide some clarity around S/4 HANA beyond the customer counts.”

This was interesting, because according to Dennis Howlett, even in April 2016, S/4HANA does not appear to be a complete product. However, SAP originally communicated a release in 2014 (the month unspecified) but the proposal here by Dennis Howlett is that over two years later S/4HANA Finance is still not complete.

Fact of the Matter with S/4HANA Finance Customers

The fact is that companies that implemented S/4HANA Finance do not have a complete ERP suite to connect to. That is a new development in the history of SAP’s ERP system. For a number of the companies on the S/4HANA list of implementations, the public case studies, these companies are only financing entities, and therefore they do not need the rest of the ERP suite. But for customers that intended to connect to the rest of the ERP suite, one has to wonder what their state of mind is now that the have invested in S/4HANA Finance.

The Media Coverage of the Missed Deadlines

This would seem to be a pertinent fact that would be reported by media entities that cover IT. However, I cannot find anyone covering this topic. Media entities like ComputerWeekly will report when SAP produces a press release, and also takes advertising from SAP. but in terms of checking whether previous statements/predictions actually came true, there is literally no coverage of the topic. A media entity in the IT space cannot expect to receive advertising if they spend time verifying vendor and consulting company statements. Therefore, the model seems to be to simply publish announcements by software vendors and consulting companies, and the more advertising they pay to these media entities, they more coverage the software vendors and consulting companies receive.

This specific topic was covered in more detail in the following article IT Media Output and the Fake News Debate.

See our The S/4HANA Implementation Study. for real story and details on actual S/4HANA implementations.

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


The Real Story on ERP Book

ERPThe Real Story Behind ERP: Separating Fiction From Reality

How This Book is Structured

This book combines a meta-analysis of all of the academic research on the benefits of ERP, coupled with on project experience.

ERP has had a remarkable impact on most companies that implemented it. Unplanned expenses for customization, failed implementations, integration, and applications to meet the business requirements that ERP could not–have added up to a higher Total Cost of Ownership for ERP were all unexpected, and account control, on the part of ERP vendors — is now a significant issue affecting IT performance.

Break the Bank for ERP?

Many companies that have broken the bank to implement ERP projects have seen their KPIs go down— but the question is why this is the case. Major consulting companies are some of the largest promoters of ERP systems, but given the massive profits they make on ERP implementations — can they be trusted to provide the real story on ERP? Probably not, however, written by the Managing Editor of SCM Focus, Shaun Snapp — an author with many years of experience with ERP system. A supply chain software expert and well known for providing authentic information on the topics he covers, you can trust this book to provide all the detail that no consulting firm will.

By reading this book you will:

  • Examine the high failure rates of ERP implementations.
  • Demystify the convincing arguments ERP vendors use to sell ERP.
  • See how ERP vendors take control of client accounts with ERP.
  • Understand why single-instance ERP is not typically feasible.
  • Calculate the total cost of ownership and return on investment for your ERP implementation.
  • Understand the alternatives to ERP.


  • Chapter 1: Introduction to ERP Software
  • Chapter 2: The History of ERP
  • Chapter 3: Logical Fallacies and the Logics Used to Sell ERP
  • Chapter 4: The Best Practice Logic for ERP
  • Chapter 5: The Integration Benefits Logic for ERP
  • Chapter 6: Analyzing The Logic Used to Sell ERP
  • Chapter 7: The High TCO and Low ROI of ERP
  • Chapter 8: ERP and the Problem with Institutional Decision Making
  • Chapter 9: How ERP Creates Redundant Systems
  • Chapter 10: How ERP Distracts Companies from Implementing Better Functionality
  • Chapter 11: Alternatives to ERP or Adjusting the Current ERP System
  • Chapter 12: Conclusion