If you were talking to someone whose organization is considering SAP S4HANA on AWS, what would you say?
How would you rate it and why? Any other tips or advice?
I think there are some processes that could be improved but it's a great solution. I would rate this product an eight out of 10.
The advice that I would give to people who want to use S/4HANA on AWS is that a specific study needs to be involved in the implementation process. It is what we call a discovery session. The idea is to discover all the independent needs for the use of the product. This includes things like the size of the organization, the size of the industry, the number of users expected, the revenue, et cetera. It should also include projections into the future aspects of organic and inorganic growth. The budget may be the main issue for many organizations. The deployment plan should be created based on keeping all these discovered factors in mind. This can affect the deployment model or choices as to whether to go for SAP S/4HANA on the cloud, on-premises or if another ERP may be a better choice. But in any case, all the factors need to be taken into consideration. It is not a black and white decision. On a scale from one to ten where one is the worst and ten is the best, I would rate SAP S/4HANA as very near to a ten. Maybe nine because there is no competitor like SAP in the market right now to compare the product to and maybe there is room for improvement. I think that Oracle and Microsoft are looking to close the gap. But, looking at the current market share of SAP, it is at the top so it is near to a ten.
Planning is very important before undergoing an S4 implementation and upgrade. The functional components need to be planned and tested thoroughly. Otherwise, the lines will not be met. Try to do a Greenfield implementation because it will be much simpler. I would rate it an eight out of ten.
There should be the ability to deploy with clustering of different servers. They should add different types of advisory management. I would rate it an eight out of ten.
The advice I would give to someone who is looking into implementing this product is to wait for a year basically so the product will mature and stabilize. The company and the users will learn what the issues are that have been discovered by other people and then maybe it is OK to take on S/4HANA as a project. The project itself is going to take eight to nine months to get completely on HANA. If this part of your business is the backbone of your industry, you can not afford to make this kind of risk. On a scale from one to ten where one is the worst and ten is the best, I would rate the product overall as between a five and a six. Closer to a five at this point. The problems are that the GUI should be updated and the time needed for real user issues that will come up, be identified, and be rectified. Probably after that, you will start seeing the results with the product moving in the market and raising awareness and popularity. It is more of a wait-and-watch as of now in my estimation.
We use both the on-premises and private cloud deployment models. I'd rate the solution 7.5 out of ten.
This solution is fantastic, and I fully recommend it as I recommend all SAP solutions. All of their products are good for SMEs or for large enterprises. From the functional side, there is very little room for improvement in this solution. There are always enhancements that can be made, of course. It is not easy to find people with knowledge of the HANA database. People skilled in HANA are rare and expensive, unlike Oracle, where you can find thousands of CVs for database administrators. I would rate this solution an eight out of ten.