Please share with the community what you think needs improvement with SAP S4HANA.
What are its weaknesses? What would you like to see changed in a future version?
This solution works with the configuration, if the prerequisites are very clear and can be configured it works perfectly. If you need to simulate something, as a predictive tool this kind of simulation is not very accurate and it has limitations. This is something that could improve. In an upcoming release, the allocation process should be revised and improved.
It's been just one year that we started using this product, due to the fact that we need to have different integrations as well to other systems. With S/4HANA, when SAP started, everything worked in a single SAP system. Slowly then it's been delegated or divided into multiple SAP systems. That's why we have around 25 different SAP products running in our landscape. Yet, at the same time, S/4HANA is the core. It's the core component. Going forward, I believe more systems could be consolidated into S/4HANA. We need to reduce the number of SAP systems running in our landscape. S/4HANA has the capacity to host many other SAP products, therefore we can discontinue some of the SAP products. Currently, we have now the Global Services, the Governance, Risk, and Compliance, and Enterprise Portal, BW, Supply Chain Management, Warehouse Management, et cetera. If SAP could consolidate many of the systems so that we can reduce the number of systems, that would be ideal. The solution can be a bit expensive. We would like to see more DevOps capabilities in the future. The solution would benefit from offering more serverless features in the sense that when you deploy SAP, it's a pretty big deployment and you have a lot of dependencies or you are closely tied up or you have a dependency with the hardware vendor and the hardware providers and the certified hardware and items like that. At the same time, all these deployed components and these files are possible to deploy without a server as well. Slowly SAP is providing some of the features so that you can deploy this in containers and so you don't have any dependency on the running hardware. That way, you can restart the systems without any downtime or the end-users will not feel the difference. Aspects like that need to be improved. We do have here monthly maintenance due to the fact that sometimes we need to recharge the system and we have seen from the end-users there will be certain downtime as well. If there is no dependency with the hardware and if it goes serverless, then we can have zero-downtime maintenance.
The two things that need to be improved are price and customization. These are two dynamic changes that every customer will want.
When it comes to the delivery of features, I would like it presented in a more user-friendly way. Every year, when a new version is released, it comes with a very thick booklet of 300 or 400 pages and it is a little difficult to comprehend. This is something that should be simplified. A simple comparison between the older and newer version would be very helpful for customers and consultants. The default UI has been the same for a long time and in my last few projects, I've found that it wasn't fast enough.
The theory-side of the solution needs to be improved. They need to come up with a simple way to explain to their customers how to properly use it and perform analysis and move on from there. In the next release, I would like to see more integration scenarios with the cloud, straight out of the box.
The solution isn't lacking any features per se. Clients aren't coming to us and saying "we need this or that." The cost of the solution is quite high. It needs to be adjusted. The integration could be better. They have many different kinds of house platforms, and then it becomes complicated to have integration within all of these different systems.
The common issues being raised right now by the end-users are mostly related to the usability. Especially on the Fiori interface. I think they're a manufacturing company and they're implementing lean manufacturing. They are actually counting the number of clicks and screens that are being used by their end-users so they can have a more efficient and intuitive approach on the Fiori apps. In terms of what features should be included in the next release, there would be too many to mention. I would probably say right now, as part of the planning session, they're going to go through the entire gamut of features where they can improve and where we're lacking in some parts. We're planning to implement a trial for support and warehouse management. But it's a big list right now and I can't think of anything specific. In terms of what could be improved, I would say the usability aspect of it for the users. Additionally, from the corporate perspective, some of the more stringent integrations across modules and also allowing integrations from third-party applications.
This is an integrated system so it is very complex. It is not like Windows or like Microsoft products where you can use Word or you use Excel and it is familiar and easy to use. The interface is something that is very confusing from my point of view. It can and should be simplified. It needs some work on the front end to be more user-friendly and customizable to the user's needs. It is not a very good product from the perspective of ease-of-use. Trying to implement it is like you want to prepare some food. You have raw materials like spices in a pile but there is no recipe as to how to mix them. It is a recipe missing the proportion to mix the spices in. In the case of S/4HANA, that recipe depends on how the organization requires it to operate. A better result depends upon the implementation partner's decisions in handling the wide range of choices offered by the product. If these decisions are not good, once the product is already developed, you may come to know after years of using it that it was not implemented optimally. Then you end up making customizations and work-arounds because of this initial implementation. That is bad practice. Customization and work-arounds will only lead to more complexity. It is a very big product that can not be understood in a short span of time and implemented quickly. Meticulous planning is ultimately important. A lot depends on the implementation partner and if they understand your needs. An implementation partner who rushes in too quickly with a solution can get it wrong and that can cause major problems in the long run.
Every business has some unique requirements which can mean customizations are required. What I'd really like to see is the development of an industry specific solution for the food industry, in particular the supply and demand side that's very critical to us, given that there are issues with products that have a shorter shelf life.
* S/4HANA 1610: We found very less Fiori apps — a few apps not working. * All module Fiori apps need to be tuned.
I'm working at a pharmaceutical company. Our user base is 300 + we have 1600 field users.
Which ERP solution is the best choice for our company: SAP Business One or SAP S/4HANA? Please pprovide some technical details along with your recommendation.
I appreciate your help.