Comprehensive software reviews to make better IT decisions
SAP S/4HANA and HANA Licensing Series – Part I: The Forced “Upgrade”
Current SAP ECC customers have a decision to make, as SAP has announced the end of ECC support effective 2025, in effect mandating a move to its next-generation ERP solution, S/4HANA. This is in spite of sources reporting that the S/4HANA codebase is over 90% identical to the legacy ECC product!
Mandated upgrades by enterprise software vendors are nothing new. The extension of these often artificial deadlines are not new either. In this case, however, SAP is mandating not just the typical upgrade but a net new purchase of the S/4HANA solution. You see, SAP’s legal beagles have designated S/4HANA a “logical successor” to ECC vs. a “legal successor.”
What does this mean in plain English? It means that there is no upgrade path to S/4HANA in spite of the many years and often millions of dollars spent on SAP enterprise support. It means that migrating to S/4HANA requires a net new license purchase. It is critical for SAP customers to become informed of the new aspects dealing with licensing and costs for S/4HANA and HANA before entering negotiations with SAP.
And if that pill wasn’t hard enough to swallow, it is equally important to realize that the only database certified to run S/4HANA is, you guessed it, SAP’s HANA database. This is a deliberate maneuver on the part of SAP to dislodge Oracle (and other DB solutions) off of the SAP ERP technology stack. Essentially, displace the competition while gaining that business for yourself.
SAP tried to drive business at the database layer through their acquisition of Sybase some time ago. Do you know anybody running Sybase? I don’t either. SAP has steadily declined to invest more in that product in recent years. In short, SAP is both forcing a new software license purchase for those customers that want to move to S/4HANA and simultaneously limiting customer choice at the database layer.
This is the first in a series of short notes that aim to provide a rapid-fire base of the nuances, license changes, and performance attributes of S/4HANA vs. ECC and will also touch on the HANA database product. The takeaway for now is that a move to S/4HANA should be viewed as a re-platforming event, not an upgrade. As such, organizations should plan to treat this option under the guise of a competitive ERP RFP.
Want to Know More?
Thor, the Norse God of Thunder, tells Jane Foster, the woman he’s trying to impress, that on his home world of Asgard, the realm eternal, science and magic are two sides of the same coin. Had Jane been a part of the operations teams at Google (or other mature online service providers), she would have immediately realized we have a similar technology right here on good old Earth. We call the science site reliability engineering (SRE), and service level objectives (SLO) is the magic behind it. SRE is a powerful concept for organizations that are serious about keeping their customers happy. It is therefore important for them to develop well-thought-out SLOs and make certain that management is intellectually equipped to derive valuable business perspectives from them.
Hell hath no fury like a customer not being able to access an online service when they want to. They expect the online services to always be on, always be accessible, and always treat them like there’s no one else in the world who matters more. Thank heavens then for giving these online services the ability to use site reliability engineering (SRE) to keep their customers happy, engaged, and most importantly, feeling valued.
Info-Tech members moving to Agile are frequently unsure of the role of PMs and the PMO in an Agile environment. Any organization used to traditional (Waterfall) project management will need to make adjustments in support of Agile or risk losing the benefits.
GitHub has announced that, effective April 14, 2020, all of its core features will be free for everyone. This will include private development within organizations that have previously paid for some subscription plans.
Many Info-Tech members are wrestling with how to best manage their software development productivity while working from home, especially for teams using a Waterfall approach. Sprinkling some Agile practices into their normal routine could improve transparency and show continuous value delivery.
When deciding on how to license your products or components, you don’t start with debating open vs. closed source code. It starts with asking simple questions around your overall goals.
Not all metrics are good and using poor metrics can have a serious negative impact on your organization. Maximize the value of your software development lifecycle (SDLC) metrics by using this thoughtful and judicious approach to ranking and selecting them.
RPA projects fail more often than one would expect. The ease with which RPA tools allow workflows to get designed and implemented makes it easy to avoid building a strong foundation for the work being done.
We live in a metrics-fixated world where having more metrics is always thought to be better than having less, and Software Development Life Cycle (SDLC) metrics are no exception. But the truth is that any badly chosen or managed metric will do more harm than good to your organization. To avoid these pitfalls, take ownership for SDLC metrics away from managers and put it into the hands of those who can best manage it: your development teams.