Copyright © 2020 hybrismart | SAP Commerce Cloud under the hood | SAP hybris, What Does History Tell Us About The Upgrade Potential Of The Pending SAP Commerce Cloud v2005 Release? Enough of the suspense. For companies looking to migrate to this version however, there is often a lag time in terms of getting budgets approved, getting the upgrade effort sequenced in the broader scope of Hybris solution enhancement work, and then starting the actual implementation itself. SAP Billing and Revenue Management (On Premises and formerly known as SAP BRIM or Hybris Billing) History. — Part 1, Using Native SQL in SAP Commerce Cloud (Hybris), hybrismart | SAP Commerce Cloud under the hood | SAP hybris.
I trust this analysis has been valuable to you. Presumably by the end of 2020 the trend bands would strength further as those currently in progress would have completed their upgrades. Most of us who have been in the Hybris ecosystem for a while have a “feel” for how version-to-version upgrades of Hybris go, the cadence that various companies go through with respect to deciding if/when to upgrade, etc. For the versions highlighted, there is a general trend from “lots” to “some” or from “some” to “none”. It has been nearly a year since the last “major” SAP Commerce Cloud (Hybris) release of v1905. One curious thing about the altered end of life dates is that v1808, v1811, and v1905 all had their end of life dates changed; however, v6.7 did not. , SAP SE acquired hybris on August 1, 2013 for $1.5 billion. It likely benefited from the “major version curse” of v6.x described earlier. Ergo, this extra weight may be slowing some companies down, since they need to secure bigger funding and longer schedules within their overall IT strategy in order to achieve maximum benefit and avoid going “half way”. On the flip side, SAP readily acknowledges that their R&D investments and innovations are being directed towards the cloud, and more or less have been since the 2018 inflection point in the “out of support” line. 3 beats out the also solidly performing v6.2 at the version of choice in 2017. It subsequently moved its headquarters to Munich, Germany. The data set encompasses growth and change in EPAM’s Hybris client base. Well, if you are a customer that isn’t interested in migrating to cloud – maybe you don’t like the new revenue-based licence model; maybe you’re already in the cloud on your own with AWS, GCP, etc.
More recent data was found to be more available and reliable than older data. I still feel, the month and year in hybris version seems irrelevant though SAP has now even decided to have one commerce version per year. V6.0 also gets a “dishonourable” mention as the version that made the graph yet came both in and out with a whimper. You’ll note that no other version band is absent or as thin post v6.0. potentially changed. industry, size) EPAM typically engages with for e-commerce work. Let’s start with versions that stand out, marked by a star in the graphic below: In my subjective opinion, the all-time “most loved” version of Hybris appears to be… v5.7! During a recent “New Feature Highlights” presentation I attended that SAP gave to one of my clients, SAP exhibited a table showcasing the various “major” features/subsystems of Hybris against various Hybris versions. In 2011 private equity firm HGGC acquired a majority stake in hybris and merged Canadian software company iCongo into hybris. While nothing is official until it is official, this month I am expecting SAP to release SAP Commerce Cloud v2005. 2005 looks more like a version released in year “2005” instead of year 2020 and month 05 for an outsider. In the meantime, regardless of your current situation with your own Hybris program, I would encourage you to discuss with your key stakeholders – program owners, IT owners, business owners, partners, SAP – what your upgrade strategy is. The grey dotted line further showcases versions that are not yet out of support but will be by the end of this year (2020). v5.0 behaves a little differently in part because it had the better part of a full year to establish itself.
(ie. In this context, every SAP Commerce Cloud solution owner needs to ask themselves, “Is it time to upgrade?”. In part to emphasis this point and in part simply to demonstrate the analysis approach to more interesting insights yet to come, take a look at 2012 below: What is the data telling us here? History of SAP S/4HANA Earlier versions SAP R/2 was a ... SAP SE brought out a client–server version of the software called SAP R/3 (the "R" was for "Real-time data processing" and "3" was for "3-tier": 1) database, 2) application server, and 3) client (SAPgui)). It also has strong staying power, and continues to be in use today. The release of v5 had seen a significant growth in the number of customers, mainly due to SAP acquisition. (!) Whether you want to seize first mover advantage and go live with v2005 first, or whether you’re more of a wait and see approach, or somewhere in between, my experience from working with clients just like you shows that the best run e-commerce programs have a defined strategy and plan behind how to tackle upgrades (among other things).
Feel free to leave a comment below on the greatest or worst Hybris version of all time. Whether it’s due to lack of proper in-house talent, insufficient bandwidth, or weak prioritization, their e-commerce solutions have suffered and they reached out to EPAM to reinvigorate their e-commerce program.
One of the things I heard from clients in my travels is that they “don’t want to be the guinea pig” and they’d rather “let someone else go first” when it comes to new versions released.
, hybris customers have included General Electric, ABB, West Marine, COS, Thomson Reuters, 3M, Toys "R" Us, P&G, Levi's, Nikon and Johnson & Johnson. To suddenly change that end of life date would potentially upend numerous Hybris solution owners who are mid-upgrade or just about to start. Conversely, for those on v1808, thoughts of upgrading hadn’t likely surfaced just yet, since that deadline was still at least 7 months away.
This opened up SAP to a whole … That is why for a little less than half of the versions graphed above, the year after a given version is released you see the maximum extent of its adoption. There is a natural resistance amongst some (not all) to avoid the latest release.
While technically tied with v1808 in 2019 for adoption, I gave the nod to v1811 due to it’s apparent staying power. Through this “stacked” graph, you can also easily sum up various bands to answer questions like, “What percentage of solutions were using version X or greater/newer?