SAP S4HANA on AWS Reviews

Our organization has found the modules to be beneficial as we've progressively increased their usage. Initially, we began with finance, costing, procurement, and payroll, and then expanded to include planned maintenance and additional maintenance-related modules.

Reporting transparency and user-friendliness are the key benefit of deploying SAP S4HANA on AWS. Furthermore, the solution offers a plethora of modules that have proven to be valuable, and there are regular updates available.

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

I have been using SAP S4HANA on AWS for approximately five years.

The stability of the solution could improve.

I rate the stability of SAP S4HANA on AWS an eight out of ten.

We have approximately 100 people using the solution in my organization.

I rate the initial setup of SAP S4HANA on AWS an eight out of ten.

I rate the support of SAP S4HANA on AWS a ten out of ten.

Positive

I have not used another solution similar to SAP S4HANA on AWS.

The setup that we have done for our business has been straightforward.

I rate the initial setup of SAP S4HANA on AWS an eight out of ten.

I rate the price of SAP S4HANA on AWS an eight out of ten.

I strongly encourage organizations that are not currently using SAP S4HANA on AWS to consider implementing this software as per their budget and planning.

I rate SAP S4HANA on AWS a ten out of ten.

My company's clients use SAP S4HANA on AWS to manage some of their daily work.

With SAP S4HANA on AWS, my company's clients find the real-time information system to be interesting.

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

I have been using SAP S4HANA on AWS since 2015. My company has a partnership with SAP.

After the implementation phase of the product, it becomes a very stable tool.

Scalability-wise, I rate the solution a four out of ten.

The capability of the product to integrate with other applications is one of the biggest problems I face when dealing with the implementation process.

Most of my company's clients who use the solution are medium-sized businesses.

The quality of the technical support provided for the product is something that depends on the managed service provider of the solution, which could be good or bad.

I rate the technical support a five out of ten.

Neutral

Based on the opinion of my company's customers, who find the product's initial setup process to be complex, I rate the product's initial setup phase between seven to eight on a one to ten scale, where one is a difficult setup process, and ten is an easy setup process.

The solution is deployed on the cloud and on an on-premises model.

The solution can be deployed in a year and a half to two years.

It takes around four to five years of using the solution to experience a return on investment from the product.

I rate the product price a six on a one to ten scale, where one is cheap, and ten is expensive.

I rate the overall tool a seven out of ten.

We use the solution for SQL database.

SAP S4HANA offers advanced analytics management, providing flexibility in handling complex SQL applications and enabling simplified predictive analysis. We are integrating with Amazon Athena, leveraging its cloud-based big data capabilities. By combining our data warehouse, operational data, and ERP solution, we can harness the power of Amazon Athena alongside robust machine learning tools.

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.

I have been using SAP S4HANA on AWS as a customer and a partner for one year.

The product is stable. We didn't have any issues, but there might be issues that come up because of services.

I rate the solution's stability an eight to nine out of ten.

I rate the solution’s scalability an eight-point five out of ten.

If we have any issues, we can contact Amazon support.

The solution is a little expensive. It is a managed service. Once we install the service, it will be highly scalable. Additionally, it streamlines analytic data.

If your application is bigger, then you definitely need to install the solution.

Overall, I rate the solution a nine out of ten.

S4HANA is an analytics suite. It's a cloud-based solution for managing an enterprise. Each enterprise has different departments, like finance, procurement, sales, quality assurance, planning, etc. The system has the capacity to manage all these departments in a single box and they're all integrated. 

The purpose of the solution actually is to manage all the organization's activities within your organization on a single platform. For example, when you register a transaction from procurement, the finance part of the system deducts it from the balance sheet. The same thing happens with sales, maintenance, or any other department. It helps you visualize your data in real time and make decisions.

SAP S4HANA is the same regardless of whether you host it on AWS or Azure like water is the same whether it's in a black or white bucket. It's the same solution. But within the solution, you have different models. Each of them is equally important depending on the industry.

We first deployed S4HANA for HSDF in 2017. We did OiServe during the lockdown and now we're doing it for NEP.

S4HANA is a highly stable solution because it's on the cloud. The solution is available 24/7.

S4HANA on AWS is scalable. We currently have three clients on it: OiServe, HSDM, and NDEP. The others are using on-premise solutions. So I will count those ones.

The support is okay because there's a support structure for that. You need to have first-level support and second-level support from a partner. SAP provides third-level support. SAP also has a platform where the partner can raise the ticket to SAP when there are issues that the partner cannot resolve.

S4HANA can be complex if your customer makes it complicated. At the same time, it can also be a straightforward solution if you meet a customer who is just willing to use the best practices. It's the same as SuccessFactors. You have standard rapid deployment and tools that SAP provides to deploy S4HANA within a short period. Some clients complicate the entire thing and say, "Well, I want to do this." In those cases, the project can last six months or longer than a year.

Or deployments for HSDF and OSA took six months. We expect to complete MDEP in six months because they have a simple process.

S4HANA is expensive. It costs much more than SuccessFactors. However, depending on the company, you can also get it at a steep discount. In Nigeria, they're trying to reduce the price because of the exchange rate issues. They're working on that, but generally, the solution is fine. It's an excellent tool. 

I rate SAP S4HANA on AWS eight out fo 10. I won't give it a nine because there is still room for improvement. 

SAP S4HANA on AWS is used mostly for SAP. Amazon AWS is one of the biggest installed bases for SAP solutions is why we selected Amazon AWS mostly for our clients.

The most valuable features of SAP S4HANA on AWS are that it's simplified and the analytical capabilities are good.

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 have been using SAP S4HANA on AWS for approximately two years.

SAP S4HANA on AWS is highly stable. I have not found any performance issues.

I rate the stability of SAP S4HANA on AWS a four out of five.

The scalability of SAP S4HANA on AWS is very good.

I rate the scalability of SAP S4HANA on AWS a five out of five.

The support was good. We only interacted once or twice with them, but not on a continuous day-to-day basis. Wherever we interacted with them it was good.

I rate the support from SAP S4HANA on AWS an eight out of ten.

Positive

The initial setup of SAP S4HANA on AWS is easy. The full implementation of the solution could take between 15 to 20 days. If it is only one system and it is a straight version with no upgrades and other things, then it will be only maximum of five to 10 days.

We use different teams for the deployment of SAP S4HANA on AWS, and currently, we are using two people.

We have approximately three to four people supporting this solution for maintenance.

My advice to others is this solution is straightforward and the deployment is very easy. I would suggest choosing Amazon AWS for SAP S4HANA if you have a nearshore data center to avoid any latency issues if we are in a different time zone.

I rate SAP S4HANA on AWS an eight out of ten.

S4HANA can be used for multiple functions throughout industry from material management to finance and production planning. I'm an SAP technical consultant.

The solution provides good performance and SAP is constantly releasing new features. 

The AI aspect of SAP S4HANA can be improved upon. 

We've been using this product for 17 years. 

Stability has definitely improved over the years. Many customers are migrating to this solution but it requires a change in how business is done, which is too difficult for some companies. Moving involves a lot of digitization, a different GUI. 

The solution is scalable. 

Support for SAP is not that simple but AWS provides good service. Complex problems can take some time to solve, but they usually have a quick response time. 

This is a complex application so the initial setup is not straightforward and requires planning and expertise. Migration time depends on the size of the landscape and the database. It can take a couple of years in an enterprise environment. The main work is around configuring the solution. Deployment usually requires a team of six to eight people. Managed services or maintenance depends on the size. Our in-house consultants are multi-skilled in both SAP and the cloud.

It's important to plan, prepare, and choose a service partner with adequate experience. 

I rate this solution eight out of 10.

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.

I have used this solution for the past seven years.

With Azure, there are a lot of tools available for monitoring SAP-related information. When it comes to AWS, the infrastructure isn't specific to SAP. The monitoring and backup solutions that are available with Azure are missing with AWS.

For example, take a case for HCM enrollment. For Sonic, you need to go with the SBD devices. It should be separate. The SBD devices need to be provisioned with the three nodes with AWS. We have a fencing agent in Azure, which would be cost effective, rather than provisioning three additional VMs. It's a minimal cost, but there are additional loads which need to be done on top of it.

I would rate the stability as nine out of ten. Almost all of the public cloud providers provide the same kind of stability.

The scalability is good. 

SAP has an auto-scaling feature, but Azure doesn't.

There weren't a lot of challenges with the setup.

I would rate the setup as five out of five.

It's expensive. It would be good if AWS and Azure could reduce the computing cost for people who move to the public cloud.

I would rate the pricing as four out of five.

There's not a lot of difference in the pricing of AWS and Azure. AWS is about $1 or $2 higher than Azure. Azure is cheaper when it comes to the computing part. From the partner side, I feel we are getting more benefit when it comes to Azure Cloud.

I would rate this solution as nine out of ten. 

When it comes to Azure, if you're already using existing solutions, it's easy to leverage that into a public cloud.

There are challenges with implementing AWS in India, but not Azure.

We use SAP S/4HANA on AWS for an enterprise environment encompassing multiple departments and functions like JBA, operations, finance, HR, and EIBM.

The product efficiently manages the data center without manual intervention.

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

We have been using SAP S4HANA on AWS for more than ten years.

I rate the product's stability a ten out of ten.

I rate the product's scalability a ten out of ten.

I have been using SAP for 20 years. The initial setup process for deploying it on AWS is similar to the on-premise infrastructure.

SAP S4HANA on AWS has reasonable pricing.

It is a complete enterprise application. I recommend it to those looking for an ERP product to deploy on AWS. I rate it a ten out of ten.