- SAP proposed that ECC customers should move to HANA to prepare for S/4HANA.
- We evaluate the logic of this proposal.
We received the following question in our article on SAP Layoffs and a Warning on HANA?
See our references for this article and related articles at this link.
“You left out “Advice for ECC customers” contemplating moving to SOH. They should continue to run their stable ECC on AnyDB and upgrade to the latest versions to be able to use new features such as In-memory computing without having to make changes to their ABAP codings, while waiting for the dust to settle on all the reorganization going on.”
Moving ECC onto HANA, or as you say, SOH never made any sense. The original argument was that it would prepare a company to move to S/4, but it was just a way to sell HANA licenses. There were so many things like this that SAP and consulting firms proposed, like running a HANA sidecar, etc. All of these leveraged the idea that HANA was inevitable. But now it is quite clearly not unavoidable. And why SAP stopped reporting HANA customer numbers back in 2015. https://www.brightworkresearch.com/why-did-sap-stop-reporting-hana-numbers-after-2015/
I recall all of this because I supported SAP sales initiatives back in the heyday of the HANA zeitgeist. The sales teams I helped said all kinds of things that look increasingly inaccurate in retrospect.
So here are a few critical points.
- Customers that move ECC to HANA will see no performance improvement over whatever database they replace. ECC cannot leverage the analytics benefits of HANA because ECC has minimal reporting. And AnyDB already has in-memory/multimodel in the more recent versions of their databases.
- Customers that place ECC on HANA will see more expense.
- Getting ECC on HANA is not a stepping stone to anything. It is merely a waste of IT budgets.
ECC on HANA has no legitimate logical support.