- Sven Denecken made some curious statements about S/4HANA 1610.
- We evaluated the accuracy of Sven Denecken’s statements.
SAP released S/4HANA release information through ASUG, that was released by ASUG in a completely unfiltered form.
In this article, we will check the accuracy of this ASUG article with the benefit of hindsight.
Is S/4HANA Fully Fiori-zed?
“ASUG members can now think of S/4HANA as being fully “Fiori-ized” to prove a consistent user experience across the business suite.”
No that is untrue, and Sven Denecken knew this the moment he said it. Fiori only **covers** parts of S/4HANA, not all of S/4HANA. Actually, this is relatively easily verified.
This is covered in the article.
“We have covered the entire 1610 suite with Fiori now,” says Sven Denecken, SAP SVP for product management. While previously if users were savvy enough they could find some Web GUI in S/4HANA 1511, that’s nearly impossible in 1610.”
This is an easily verifiable inaccuracy. It is quite easy to find areas of S/4HANA with no Fiori coverage.
Are S/4HANA Live Customers?
“Of the more than 4,100 SAP customers who to date have licensed S/4HANA, 8.5 percent or 350 customers are live on the suite. These live customers are either running S/4HANA on-premise or via managed cloud. A handful of organizations have signed up for or are using S/4HANA public cloud edition, but SAP plans a formal launch of the product early next year.”
One might ask why so few customers are live on S/4HANA and if SAP has exaggerated the S/4HANA customer number through discounts. We know that the vast majority of S/4HANA implementations are on premises. SAP only has small companies that do not require customization on their S/4HANA public cloud.
Full Scope S/4HANA?
“Speaking on the vendor’s third-quarter fiscal 2016 conference call, Rob Enslin, SAP’s customer chief, said that over 50 percent of the S/4HANA live customers are implementing “full ERP scope”—which essentially means S/4HANA 1511 or 1610.”
Rob Enslin is a highly unreliable source of information about SAP. In nearly every case we have analyzed of Rob Enslin’s previous comments they have turned out to be false.
Also, this could be in any stage of implementation, but if they are implementing full scope S/4HANA this could also mean a very selective portion of the overall ECC functionality (which is far higher than the S/4 functionality.
Is S/4HANA at Feature Function Parity?
“1511 was already at feature function parity with ECC,” says Denecken. “We think this release, 1610, will definitely prove that and get that question out of the way.” Can customers do all the same things with S/4HANA that they did with ECC? “No, that was never our intention,” he adds. “We’ve carefully built a new product.”
If release 1511 was already at feature function parity with ECC, then was can’t customers do all the same things with S/4HANA that they do with ECC? Isn’t that what the word parity means?
Not only was 1511 not at parity with ECC, 1610 was not either. In fact, the overall suite is not yet released, as is covered in the article How the Overall SAP S/4 HANA Suite is Not Yet Released – Brightwork | SAP
And the second part of this quotation is confusing. It seems to contradict the first part of the quotation. If feature function parity was reached then why can’t you do the same things with S/4HANA? SAP’s response may be that there is simplification involved, but it may also simply be an excuse to contradict the first statement which is incorrect.
“S/4HANA 1610 also adds in all the features of S/4HANA Finance and all future innovation on finance will concentrate on the suite, not a stand-alone finance offering. “We believe the rationale for starting with finance stand-alone will go down,” Denecken says. “We’re not saying it will go away.”
Well, when S/4HANA was first released there was nothing but finance functionality. So now there is functionality outside of finance available. But it is not as mature or anywhere near as complete as the functionality in finance. So, of course, there may be more opportunity to implement more of the suite, but the suite is still highly incomplete.
SAP’s List of Fiori Coverage
- * “Fiori 1.0 for Customer Activity & Retail
- * SAP Fiori EHS Management
- * SAP Fiori ERP
- * SAP Fiori ERP HCM
- * SAP Fiori Fashion Management
- * SAP Fiori Hybris Marketing
- * SAP Fiori Information Lifecycle Management
- * SAP Fiori Master Data Governance
- * SAP Fiori Portfolio and Project Management
- * SAP Fiori Solutions for GRC
- * SAP Fiori SRM
- * SAP Fiori Request for Approvals
- * SAP Fiori S/4HANA Finance 1605
- * SAP Fiori for SAP Simple Finance add-on
- * SAP Fiori front -end server
- * SAP Fiori principle apps 1.0 for SAP ERP
- * SAP Fiori principle apps 1.0 for SAP SRM
This list seems like stuffing the bill of materials to make Fiori look larger than it is.
Let us take one category, Fiori for Master Data Governance. If we look at the Fiori Apps Library and filter by Master Data Specialists and Master Data Stewarts – we find the following “apps.”
- Master Supplier Master Data: Manages suppliers master data for all consuming departments.
- Master Data Governance Consolidation: (Very little documentation exists on this)
- Master Data Governance Consolidation:
- Master Data Governance: Mass Processing:
- Customer Master FactSheets:
- Manage Customer Master Data:
- Manage Product Master
- Material Master
- Approve Master Data
- Approve Master Data – Extended
- MDG Address Library to Approve Customer/Suppliers:
- Master Data Quality Wordlist: This is a list view.
* Another example is Fiori for Hybris. By selecting for Marketing Manager and Marketing Expert, which would use Hybris, no apps were found.
* The same issue was found looking for Fiori for Fashion Management
Of these total 74 Fiori innovations, 17 Fiori innovations are identified for HANA Release 1511
10 additional Fiori Innovations are associated with 1605 and 1610.
SAP point to delivery Fiori apps numbering above 1000 as of August 2016. Yet, this is not an accurate number. SAP has numbered any “workflow” as an app. In a count that was made of non-HANA or AnyDB apps, for the 188 apps, these were categorized into 49 “actual apps.”
SAP’s spokespeople made a number of easily verifiable false statements in this article. This article receives a 2 out of 10 on the Brightwork Accuracy Scale.
Search Our Other HANA Content
Financial Bias Disclosure
This article and no other article on the Brightwork website is paid for by a software vendor, including Oracle and SAP. Brightwork does offer competitive intelligence work to vendors as part of its business, but no published research or articles are written with any financial consideration. As part of Brightwork’s commitment to publishing independent, unbiased research, the company’s business model is driven by consulting services; no paid media placements are accepted.
The Real Story on ERP Book
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