CPU architecture is an area where the solution currently has some issues. Improvement in CPU architecture could improve the performance side and the adherence to the parameters set by SAP. As suggested by SAP, we should do HANA mini checks on a daily or weekly basis. All the parameters related to HANA should be equal to improve performance. So, some of the parameters I can see on the SAP side are related to memory, and so we have to check on each landscape whether the parameters related to SAP are properly set or not. Regarding the right CPU from AWS and SAP recommended nodes, we have to check whether the performance is good or not because we have to give this almost on HANA since, on some side, we have to be swapping that on voice level also, and so that screening part is a requirement from OS/DB side. In short, we have to check all parameters. My solution is IOPS related to EC2. So I have just done a very good optimization. I have seen some parameters related to Linux that is from SAP side, where the problem is very fast, and CPU load is very low. So that is an OS/DB recommendation parameter from the SAP that it should be set over there on all systems. As a basic start, we have to check OS/DB recommendation settings, and everything should be kept on. Those experienced in SAP S4HANA need not worry about any part.

I think overlay IP should be linked to gateway web architecture. It should be in a proper way to the community for the security part. Apart from that, we have to follow Amazon and SAP books. There have to be some adjustments made from the finance and GRC side. So, we have to check some of the functional sides and whether these parameters are properly set in for SAP s1 in terms of logistics, MRV, and some of the code. I can recommend that SAP's 86 custom code should be a proper way to develop a very good experience going online for the custom tools. So, it would be good to improve such features and everything. Also, the system should not be at any end of support since it will impact its performance. I have faced some of the, you know, clients, where they have some end of support, comes into 7209, and they just back it up. I need to get some extended support from the SAP, and some software should be there. So before the end of maintenance, everybody has to awaken all the features of the solution. On a daily production side, we can do this maintenance activity, whether it may be outdated or not outdated, and support patches should be done properly.

Whoever developed the current system that my clients have are no longer available and both engineers have retired, the solution's hardware has become a black box and they don't know how works. They spend an awful lot of time figuring out systems. They should reduce the ID expenditures.

If you go to AWS's site they offer training programs that are very good. SAP does not do the same, if SAP could provide some training that would be great.

There are other solutions that can connect with SAP S4HANA on AWS but there is not a lot of information that is provided on what they can do. If they could provide these details it would be helpful.

I would like scalability to be improved in the future for faster performance.

If we talk about the manufacturing application system in SAP S4HANA, it's not as user-friendly as it could be. However, if they incorporate the manufacturing issues into the inbuilt APO (Advanced Planning and Optimization), it would make it easier for us to consider and customize. For example, I would be able to directly link all the machines and enable them to go online without much effort or manual labor. That's the kind of customization I'm looking for. So, customization is the key aspect I'm hoping to see.

Over the last three to four years, I haven't encountered significant issues with SAP S4HANA. While occasional system bugs are normal in software, the overall experience has been positive. As a business partner, it stands out as a reliable ERP solution.

Businesses are particularly interested in process automation, mobile, and web applications. These are the areas that SAP S4HANA is and should be looking to improve on, especially in terms of streamlining processes and automating certain steps.

The documentation isn't clear enough. There are a few native services that are available for increasing the IOPS. We can either go for the database storage striping to improve the IOPS for the HWCCT requirement, or we can go for the data volume partitioning, which is available with HANA for increasing the IOPS. 

It would help during maintenance to add new storage due to the data growth. It would be easy to go for the data volume partitioning feature with HANA. It's available even with other databases, but there's no comparison with the different features.

There are a few features that are in-built and available with SAP. When it comes to the on-premises solution, we used to go with those options. When it comes to the cloud, most people compare it to their past experience with the on-premises environment rather than the new cloud solutions. They might have an in-house benchmarking comparison or test results for those things, but it would be good if they published that. It would be very helpful for us when we need to take a particular call, or when we need to go for data volume partitioning or data striping.

In Azure, files can be downloaded and easily repurposed based on our solutions, which is lacking in AWS and in GCP.

The AI aspect of SAP S4HANA can be improved upon. 

The initial setup could be easier. It's complex. 

There are times when the solution can become slower. The stability could improve.

Some parts of the solution are complex and take time. That needs improvement, and more experts need to work on that. Setting up applications on AWS servers is difficult. We need to understand how much data we have and utilize it according to the warehouse.

The solution's overall enterprise support could be improved.

SAP S4HANA could be improved by adding a click-to-deploy model.

There is room for improvement in terms of stability. 

The platform's front-end user interface needs improvement compared to other applications.

SAP S4HANA on AWS should be standardized to make its implementation phase easier. The product's implementation phase can be very complex for customers.

The tool should undergo an overall improvement, including support. Data sharing should also be faster. 

SAP S4HANA on AWS could improve by having more data centers because there are limited data centers in the region I am in. Amazon AWS has announced a few more data centers to be added, but they're still not 100 percent operational for SAP solutions.

I would like to see a lower price for the solution.

The cost is a factor for our customers, so that is an area for improvement. That is, compared to its competitors, SAP S4HANA on AWS is a costly solution. 

More availability zones will help customers choose AWS.

I would like to see features that provide easier onboarding for ERP solutions like SAP. SAP has already partnered with S/4HANA on AWS for hosting its public cloud as well. More educational videos for customers to choose this cloud path would be great to have. That is, providing more documentation and marketing material would be better.

For the cloud part, it's very good. However, some customers are a bit skeptical and a bit hesitant regarding putting their data on the cloud. And, even if they want to put their data, the business transactional data, or their company data on the cloud or not, you will still have to take care of all these licenses from a security perspective. Just recently, we had a European client who wants to work with the SAP system, however, they don't want to go on the cloud. They want to go with the on-premise solution. This is possible. For this particular solution, with the AWS angle, it won't necessarily work for them. We'll have to go with the client's requirements. We'll host on-premises.

The integration part is quite secure and stable. Only the part from the customer side that's been raised is regarding their data hosting part on the cloud. Otherwise, we don't see any issue with hosting SAP on AWS. It's always good to have on there since it reduces cost. It reduces your maintenance-wise integration also. 

They are a very big company and their own data centers although you have to make all these protocols and service agreements so that the data will not get lost. You have to take proper care of the data. You have to take daily backups before any availability or any optimization. On-premise we also used to take backups, however, it was very manageable.

There are a few complexities when it comes to licensing that could be simplified. 

The pricing is a little bit high.

The solution is costlier than other products.

We had some storage and legacy migrations problems with SAP S4HANA on AWS.

This is the latest offering by the SAP company. Of course, there are the pros and cons to on-premises deployment versus cloud deployment — especially as far as the infrastructure maintenance is concerned. There is not so much difference as far as activities are concerned. But having said that the cloud deployment is on AWS (Amazon Web Service). It is always the latest offering and the cloud is indeed today's emerging market.  

From what I understand, SAP is already at work focusing on improving the CE (Customer Experience) and the CRM (Customer Relationship Management) as far as S/4HANA is concerned. They are working with having better robotics, machine learning and artificial intelligence capabilities, which can work with this ERP. So there are already new concepts on the way. They are making a lot of use of Python technology, and they are making heavy investments to make it much more user-friendly and customer-friendly. Automation is at the center of their development focus.  

The new product has SuccessFactors. If they can bring it in on-premise as well, and basically replace SCM with SuccessFactors on-premises, that would be great. It will allow for more revenue.

The solution's weakest area is technical support, which needs to be improved quite a bit.

The solution needs a warehouse management feature. Right now, there's a built-in WM, but they don't have an EWM extended warehouse management built-in, in S/4HANA. It's a separate product. So if they can add that, that would be great.

The product can be very complex.

It is not extremely user-friendly.

If you want to learn SAP S/4HANA the resources are not available and it's very difficult to learn. We found that aspect very difficult. 

One thing which is really killing a lot of people using this product is because they have been using it for twenty or twenty-five years and a lot of the customers' customizations are not working anymore.  

A second thing that is a problem for the product is the cost — particularly on the hardware side it is too high. If you have to procure your server for S/4HANA the cost is a problem. I mean hardware cost is killing a lot of people and the costs are complicating matters for those who want to stay with the product.  

For HANA the biggest issue which will need to change is the GUI interface. It is still the age-old GUI and this needs to be changed. All the other competitors are moving to a new phase in development of user experience and they are moving to new interfaces like AngularJS and other technologies that are new. Which things or trends become most popular still remains to be known. But the front-end needs a lot of thought.  

I'm on the developer side of the product and my view, for now, is that the product is fine. I'm comfortable with it. Based on my product experience, I don't have any problems with it. If I would suggest something it would be that they unify the developer tools. 
For the next release, it would be helpful if they would include a common development environment. 

SAP S4HANA on AWS could improve by having the entire solution available as a web solution. They only have Fiori right now, and it's a solution for certain modules, but not for all the modules that SAP currently has. We would like to see the GUI removed, it is not very good. We want it to be web-based.

This solution is very resource-intensive, including high memory and CPU utilization.

This product needs to be made more available for the normal user, like those by Microsoft or Oracle. For example, it should be free for individuals, and usable on a laptop.

Not just S4 but for SAP in general, the price is a little high because they have implemented a new licensing scheme on a number of connections. The price being too expensive is some of the feedback we get from our customers. 

In the next release, I would like to see more support for more cloud providers. Because right now it's only AWS and Azure that it certifies. 

I would like for them to have more integration with virtualization platforms.