Should You Trade In Unused Licenses for S/4HANA and HANA?

Introduction

In this article, we will evaluate a strategy that is proposed by Snow Software on their website. Snow Software makes software that is used for auditing SAP software. The article by Snow Software is quite interesting and is very specific in what it proposes, and it provides specific recommendations.

I want to set the table properly before we get into Snow Software's article. I don't have anything against Snow Software. I happen to like a lot of the articles on their website and several weeks ago I read every one of their articles related to SAP and quite a few others not related to SAP. Snow Software has a blog that brings in a number of authors with different license domain expertise.

I don't happen to agree with the recommendations in this article, and I invite a representative from Snow Software to comment on this article and to have a collegial discussion. These are involved topics and even people who are knowledgeable in the area can disagree and that is quite reasonable.

Understanding Snow Software’s Logic for S/4HANA

The logic for Snow Software’s proposal is laid out in their article Use S/4HANA to Get Rid of your SAP Shelfware?

In that article they layout the following logic for purchasing S/4HANA. Let us get into their quotations.

SAP Business Suite 4 SAP HANA. S/4HANA, for short, is SAP’s latest technology. But it’s also much more than that. S/4HANA represents a fundamental shift in how the mega vendor will generate long-term revenue streams. What is often less-discussed is what S/4HANA means for you, the customer. Not only in terms of technology; but in terms of an opportunity to reshape your relationship with SAP. Without over-dramatizing things, it’s a once-in-a-lifetime opportunity. Why? Because SAP needs S/4HANA to be a success. It needs to demonstrate to investors that it has a business model that is not stuck in the era of on-premise perpetual software licensing. And because it needs to sell S/4HANA licenses, it is offering excellent deals to existing SAP customers to move fast.

So, what can be seen as left out is that S/4HANA has not been a success and it has had plenty of time to become one. It has a massive installed base (with ECC/Business All in One).

Now, while it is true that SAP has a strong desire to show that its business model is not suck in a on-premises state, SAP really has Wall Street fooled already on this topic. SAP has successfully adopted cloud speak, and is constantly cloud washing their products. The more you cloud wash, the more Wall Street rewards you. So we have yet another example of an industry that is driven by the opinions of people who don't have any expertise in the area.

Secondly, (and don't tell Wall Street or they will be very very sad) S/4HANA is unlikely to be delivered by SaaS. In research that I am currently performing into S/4HANA to determine what has actually occurred on S/4HANA implementations, it turns out that very few of the implementations have been in the cloud. And in the few that I can find that are stated to be in the cloud or SaaS, they are not cloud or SaaS at all. Instead, they are non-multi-tenant or simply hosted solutions. Customers can expect none of the traditional benefits of SaaS from S/4HANA when delivered this way.

Finally, S/4HANA has nothing to do with the cloud or SaaS.

The quoted paragraph from Snow Software continues:

And therein lies a huge opportunity for those existing SAP customers, who have typically seen their investments in SAP license increase year-on-year over quite significant periods of time. This is an opportunity to reverse that trend and focus in driving deals with hungry SAP account managers on the licenses and technologies you really need, not the ones you’ve been force-fed over recent years. To understand the scale and opportunity of this shift, we must first look to the past.

It is very difficult to argue that anyone “needs” S/4HANA at this point. S4HANA comes with all types of implementation costs and maintenance costs. These costs are far higher than any potential license cost benefit from moving to S/4HANA. In fact, the majority of costs associated with SAP come in maintaining SAP systems, not purchasing SAP systems. I cover this topic in detail in my book on TCO, Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making.

The quoted paragraph from Snow Software continues:

The fundamental change is that the open architecture of R/3, with the ability to employ third-party databases within the system, is giving way to a more specific database that you’ll require as part of the platform – SAP’s HANA. This is all being done with the promise of improved performance and scalability through in-memory databases.

Well, the promise of the performance improvement is not really analyzed by Snow Software’s article. But as HANA is an analytics database primarily, there is no evidence that an ERP system will run much faster on HANA due to software. Here it is important to draw a distinction between the software side and the hardware side of HANA.

HANA combines a changed database with SSD memory (instead of spinning disk) so the performance will automatically increase because of the hardware change (SSD), but not necessarily due to the software.

The quoted paragraph from Snow Software continues:

The faster it migrates everyone, the quicker it can stop focusing its investment in resourcing and maintaining R/3. So, in a perfect world, SAP would spend nothing on R/2 today and, 10 years from now, it won't spend any money on R/3.

Moreover, S/4HANA revenue is heavily scrutinized by investors in SAP. The faster they see adoption of this new platform, the quicker that is reflected in the share price for SAP. SAP as a stock needs a growth leg to the story despite its strong position and cash flow.

The transition to S/4HANA requires the replacement of third-party database systems with HANA and there is a monetary uplift from doing this.

Ok, so this is a strange way of saying that the cost will be higher. The cost of HANA is quite high and the expensive software is just the beginning. The following quotation will focus on support costs, but the support costs are based upon the license cost. Let us continue with the quotation to see how this is a problem.

The quoted paragraph from Snow Software continues:

SAP Enterprise support customers currently pay (by default) 22% of license costs in annual maintenance for the use of third-party databases within the architecture of their systems. SAP has steadily over the past few years increased this amount from the 15% level in advance of its migration mandate. In lieu of paying an annual 22% of license costs for your database (typically Oracle), you will pay 15% of license costs for HANA*. Additionally, as an incentive to move to S/4HANA, SAP’s extension policies may enable you to apply unused SAP licenses against a credit for the new purchase. A reduction in the software application value means reduction in overall maintenance to be paid on HANA. *Note that individual circumstances may vary.

The problem is that Snow Software is making the case for the lower cost of the annual license cost for HANA. However, HANA is the most expensive database on the market. So if you decline from 22% to 15% maintenance, the maintenance is lower, but the base is much higher than the database that HANA replaces.

Secondly, HANA comes with other liabilities, such as indirect access liability, that impact the costs of other software, which are a whole other can of worms and which I have covered in part in other articles.

Conclusion

I find the strategy presented by Snow Software to be problematic. Here is a synopsis.

1. Total Cost of Ownership: It is far too focused on the simple license math. It leaves out the all important aspect of implement ability of S/4HANA. And these issues are far more cost impactful. These costs are far higher than any potential license cost benefit from moving to S/4. In fact, the majority of costs associated with SAP come in maintaining SAP systems, and Snow Software’s article is not observant of this point. This true even if unused software is traded in for HANA or S/4 HANA and if the maintenance on HANA is reduced to 15%.
2. S/4HANA Maturity Issues: It is difficult to see how any company could have taken S/4HANA live at this point. That will not be true at some point in the future, but it is true now. I will elaborate on this point in my research which is due out in around 5 weeks from now. But most of the S/4HANA implementations that have "gone live" at this point are not what we would typically consider real implementations. And below that statement resides quite a lot of very interesting detail.

Therefore, applying the strategy above will simply result in having the license for S/4HANA that cannot be taken live for some time. Snow Software is not taking into account that S/4 HANA will most likely sit unused or in a partial demo state for this time. This would not be a problem as S/4HANA will normally be purchased at a discounted rate. Not HANA, which is required to run S/4HANA will not be purchased at a discount.

Therefore every year maintenance will be required to be paid on a very expensive database, albeit it at a reduced rate. And that is just one of the limitations of the strategy.

About Shaun

Shaun Snapp is the author of many books on technology and SAP. He is the Managing Editor of Brightwork Research & Analysis. Brightwork is a website focused on publishing storylines that do not have a way of getting out through the traditional mediums in enterprise software.

See Shaun's LinkedIn profile here. Think about connecting with him, as he likes to connect to his readers. His other LinkedIn articles are here. Follow me here.

Shaun's Other Articles on S/4HANA

The Planned First Research on S/4HANA Implementations

The Logic of Trading in Unused Licenses for S/4HANA and HANA

S/4 1610 Information

How SAP Controls Perceptions with Customer Numbers

Why SAP Will Have to Backtrack on S/4 on HANA

How the Overall SAP S/4 HANA Suite is Not Yet Released

Time to Jump off the Fiori Bandwagon

The Math of Probable S4 & Fiori Usage

What One Actually Gets with Fiori

This covers what one actually gets from Fiori. This article gets into how Fiori has been misrepresented by SAP and its partners in the sales process in order to get people all bubbly about S4, and what a huge surprise so many companies will get if they rely upon Fiori.

Why SAP S/4 HANA Should be Free

How Accurate is the Messages on SAP S/4HANA?

Getting Clear on S/4HANA Terminology

Does HANA Actually Have a Simplified Data Model?

How Gartner Got Fiori So Wrong

This article covers how Gartner got Fiori so wrong. Gartner clearly did close to zero research to praise Fiori and recommend it, without having any understanding of how Fiori actually works.

Is SAP's Run Simple For Real?

References

[Use S/4HANA to get rid of your SAP shelf ware | Snow Software](https://www.snowsoftware.com/int/blog/2016/09/20/use-s4hana-get-rid-sap-shelfware-pt-1#.WBzBfY_XJ-Y)

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.

Chapters

• 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