SAP S4HANA on AWS Reviews

I mainly use SAP S4HANA on AWS for the entire accounting process, starting from the GL process, P2P procure-to-pay, and in terms of accounts receivable, accounts payable, and invoicing. It covers the end-to-end accounting operations.

SAP S4HANA on AWS is mostly well secured because you need a VPN of the company you are working in to log in and view only with the VPN. It is not possible to connect to a random network, and it is very safe. In terms of usage and automation, SAP S4HANA on AWS is very good at automation, where instead of manually punching entry by entry as with Tally, Zoho, or NetSuite, you can do a bulk upload and close it from one GL to another GL entry from one T-code to another T-code. These are all the options and features, and it is user-friendly. Once you learn SAP S4HANA on AWS, you tend to know how to customize things and what features you want. You can add in features by working closely with the SAP team, whether it is a direct SAP team or through a contract with some agent. There are numerous things you can do; it is not limited to only one function. You can have end-to-end control, and back-dated entries are not possible as in Tally or Zoho, which is very good in terms of security and safety. There are no accounting frauds; we can even identify who has done an entry by name. It is very secure; a password gets locked automatically after two incorrect attempts, and you have to contact the SAP team for that. Data privacy is very good, and overall, it is a better option.

Regarding real-time analytics features in SAP S4HANA on AWS, you can integrate with Qlik or Power BI, and I believe there is also an analytics component within SAP itself. SAP S4HANA on AWS provides one analytics tool, and these tools can be integrated and customized however you want. It is very easy to do analytics; you can download reports or integrate those reports with Power BI. It is very convenient that way.

When it comes to AI capabilities integrated with SAP S4HANA on AWS, I am not certain because most of it comes via tools such as Qlik and Power BI. There are multiple other things that can help you integrate and work on it. For example, integrating Power BI with N28 or Cloud is convenient with tools such as Copilot. However, I am unsure how it works in SAP S4HANA on AWS because most organizations do not allow integrating AI with SAP S4HANA on AWS.

Regarding points of improvement for SAP S4HANA on AWS, there are numerous features available; it depends on how you want to customize and utilize them. If you have someone knowledgeable about end-to-end SAP S4HANA on AWS customizations or a consultant to assist, there is no risk involved. However, for smaller data, SAP S4HANA on AWS works, but it is not as efficient for mid-tier companies where the employee count exceeds five hundred or six hundred; ideally, it fits companies with more than one thousand employees on the higher side.

I have been working with SAP S4HANA on AWS for three years.

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

For scalability and the ability to expand, I would also rate it an eight. Everything I evaluate tends to fall between eight and ten, so there is no issue as far as SAP S4HANA on AWS is concerned.

Regarding the initial setup process for SAP S4HANA on AWS, it is a bit complicated, but not too complicated. I would describe it as medium to good. You can customize features and set up according to your needs, and the time required depends on what features you want. Overall, it is mostly easy; you can add some features and go live within two to ten days.

AWS disaster recovery features are managed by my IT team, and I know AWS is very good. Everything is auto-saved, and there is no issue if SAP S4HANA on AWS is stuck somewhere; data can later be retrieved from AWS.

The main benefits end users receive from SAP S4HANA on AWS include saving time and streamlining processes.

The main issue is the pricing, which is typically too high for small companies.

When comparing products, SAP S4HANA on AWS stands out above everything; I cannot truly compare SAP S4HANA on AWS with other options due to the multitude of features it offers, such as Salesforce. SAP S4HANA on AWS is undoubtedly the leader.

When comparing products, SAP S4HANA on AWS stands out above everything; I cannot truly compare SAP S4HANA on AWS with other options due to the multitude of features it offers, such as Salesforce. SAP S4HANA on AWS is undoubtedly the leader. I would rate this product nine out of ten overall.

SAP S4HANA on AWS is useful when comparing it with on-premise solutions because everything is maintained in the cloud. With managed services, you do not have to worry about your data center or managing it. Even when taking managed services for the application part, you are freed from all the headaches and burdens from the local site.

There are two primary use cases. One is that customers want to get rid of their isolated hardware and all associated infrastructure. The second is that SAP is pushing the next era toward cloud applications, such as SAP on cloud, and they are no longer going to support on-premise solutions.

For the Pakistani market, there are still two reasons for changes. The first is cost, and the second is that financial institutions are bound to move their assets to the cloud due to financial regulations. The cloud data center should be within the country. Other countries prefer to have their data in their own country as well. We want hypervisors like AWS or Azure to maintain their data centers in Pakistan as well, which will bring more value to their cloud offerings.

SAP S4HANA on AWS arrives with the SAP BTP business technology platform services. Most of the BTP services are available on AWS compared to other clouds.

SAP S4HANA on AWS is primarily a cloud solution, but I have a few customers who would still like to have on-premise solutions as they transition to the cloud. I am doing the conversion from their existing system to SAP S4HANA on-premise.

SAP S4HANA on AWS is a stable solution with new versions like twenty twenty-one and twenty twenty-two, which are quite stable. My policy is always to recommend customers to go one version behind the latest.

SAP S4HANA on AWS is also scalable.

I would recommend SAP S4HANA on AWS because it is more secure, and the performance is much better compared to other clouds.

I want to improve the cloud data center by establishing a local data center in the country.

I have been using SAP S4HANA on AWS for almost two years.

I have not used the technical support of SAP S4HANA on AWS, and I have not heard anything from my customers regarding technical support.

The setup for SAP S4HANA on AWS should be straightforward.

It took me almost two years to deploy SAP S4HANA on AWS as I am working on bringing customers to the cloud, especially with RISE with Citi. For RISE with Citi, I am promoting customers to be on AWS cloud because of the availability of BTP services.

The deployment process for SAP S4HANA on AWS involves asking the customer to provide the thirty check reports, the process discovery report, custom code analysis, and all such reports within the first three days. If customers can make these available and facilitate the migration, the system can be migrated to the cloud.

For the deployment and maintenance of SAP S4HANA on AWS, a minimum of two or three persons is required, such as two consultants from the customer side and one cloud engineer who supports the migrations.

Customers need to pay for a license on a yearly basis with a one-year strategy.

I believe SAP S4HANA on AWS is a little bit more expensive than other solutions.

I have three or four customers using SAP S4HANA on AWS on AWS. The same three or four are on Azure, and one is planning to go to SAP cloud. I have given this review a rating of 8.

One of my use cases is pretty simple. This is an ERP solution, and the whole idea is to streamline my sales and distribution systems, materials management, procurement, warehousing, and production, in case I am a production company that can work on the production part. Then I have quality management, human capital management, and sales and distribution. There are many use cases specifically for this particular ERP. It's an ERP solution. To put it in one line, it is like having a solution integrated across different lines of business within my company.

Specifically, in terms of manufacturing, SAP S/4HANA is a very good solution. I have top-line solutions across different verticals. Especially for manufacturing, it offers great integration with my costing. I can know exactly how the costing works and identify any gaps in the costing area. The costing and personnel planning integration are among the strongest areas of this solution.

There are many things already there. There just needs to be a document approval workflow, which is not limited to procurement and other documents. There might be an additional document approval workflow on top of already existing functionality. Usually, that is managed in a different system outside the ERP. SAP introduced flexible workflows, which are even better if I want customized workflows for my documentation within the procurement domain.

I've been using it for about two years now. Overall, I have been using SAP for seven or eight years.

There are incidents where there are certain glitches, however, they are specifically because of the configuration that people have made and based on the decision I made during the implementation project.

There are no concerns in terms of scalability. The processes on the system are very scalable. AWS has been running probably 96% of Fortune 500 companies across the globe, so scalability is not an issue.

The support is top-notch. There are no issues whatsoever. Usually, when I reach out to SAP, they will either address it themselves or engage further. They have a support model available, with first-level support handling initial issues when I integrate the system. Then on the second level, it is escalated to our provision provider. On the third level, the principal is involved. 

The support model is pretty neat, and there are no issues in terms of supportability support. A score of nine out of ten would be appropriate for them.

Positive

Installation is very straightforward, however, implementation takes years or months based on the project's size.

In manufacturing, the requirement might go from ten to 12 people. If I'm a sales-oriented company, such as an FMCG or something else, then I might need around seven or eight people at the very minimum. It is not an easy task to migrate. If I'm moving from a different ERP to S/4HANA, I need a proper project that probably spans several months, with significant engagement from both the business side and the technical side. I need an opportunity partner on it. Processing to SCE S/4HANA takes a bit of effort.

For SAP S/4HANA, there's a specific center of excellence needed post-implementation, which focuses on continuous improvement and ensures smooth operations. I need a full-fledged team of SAP consultants and technical people within my company, whether I am a big or a large organization. I need a whole team to manage this entire system.

There is a lot of ROI potential within the system, but it all depends on how well it is implemented. On a very good implementation, usually, if the scale of the business is large, the implementation can give a payback within six, seven, or eight months of implementation.

When I compare it with new entrants or alternatives like open-source ERPs available in the market, the pricing is very high. It depends on what I compare it with.

Overall, I would rate the product nine out of ten.

I am using modules like finance and sourcing for procurement with SAP S4HANA on AWS.

The reporting capability is good, providing very in-depth information. It manages complexity in various industries such as banking, manufacturing, and trading. The configurations are quite comprehensive, and the product can handle many complex scenarios.

The user-friendliness is questionable. The interface and interaction with the technical team require intensive training. They should also improve their user interface.

I have had many years of experience with SAP S4HANA.

The product is versatile and can manage complexity beyond expectations. The consultant's knowledge is a significant element in its scalability.

Technical support is rated seven out of ten. The technical side needs improvements, particularly in logging issues, which remains a challenge.

Neutral

I switched from Microsoft Dynamics to SAP. Microsoft Dynamics lacked certain features, and they are going off the shelf in a few years.

It's complex and not straightforward. On a scale of one to ten for complexity in setup, I'd rate it around four.

We had a small team of ten to 15 people including project managers, sponsors, process owners, leaders, and champion users. It's critical to have a structured team in place for deployment.

SAP is not cheap, with many hidden costs encountered during implementation. On a scale of one to ten for expense, SAP is a nine out of ten.

I recommend SAP S4HANA if your team is well-prepared and your internal organization is educated before implementation. 

Overall, I rate SAP S4HANA nine out of ten.

Neutral

After the implementation of ETP for S4HANA on the customer site, the customer may need support. We need to change some reports, do some enhancements to the workflow, and fix issues. Support environment, you know, technical support. I am the head of technical support and understanding and responsible for the growth of S4HANA. I also look after the tool's integration.

The most valuable feature of the solution is that it is one of the most professional and integrated software ever. The tool covers many modules, like production, planning, management, and finance. It is a very scalable tool that can be beneficial for any company.

Sometimes, the tool has bugs. These issues can be resolved with antivirus software.

The support team's response time is an area of concern where improvements are required.

I have experience with SAP S4HANA on AWS for ten years. I work in the support environment for SAP S4HANA, hosting the tool for many vendors.

It is a very stable solution. AWS is one of the most preferred hosting environments. AWS is very nice. One should not forget that SAP prefers AWS as a host. SAP likes to have AWS in its hosting environment. SAP S4HANA is a software at the surface, hosted by AWS. SAP S4HANA acts as a SaaS tool.

I rate the stability an eight out of ten.

There are many modules in the product that are used, and the total number of people using the product is around 200. For every module, there are five to ten consultants.

Based on my experience with SAP support, I can say that it has simply improved. Seriously, I rate the support a six or seven out of ten. The support's response time is not much, but we have to wait for an answer, and so on.

Neutral

I am working in an environment involving two companies. There is a company to take care of the implementation and deployment. After the customer has checked the system and accepted the user acceptance part, and if everything is good from the customer side, including areas like setup and implementation. My company, as a support, works with the customer for all the other issues. Mostly, my company is involved with the implementation and solving issues, like performance issues, enhancing reports, and so on.

There are a lot of things hosted on AWS, financially and business-wise. It helps very much with cost savings. If you compare AWS with any DB in your environment, it can get very costly during the hosting phase. There are a lot of financial cost savings here, and people should know that.

Based on my general knowledge of what the AWS product is called in the market, I would say it is not available to normal users. For information technology or at a universal technological level, for security, there is a need to have some environment, so we need to have some package installed in the laptop. I need to check the paperwork related to SAP and see if any skills are required for a person to use AWS, especially if they have zero knowledge about the tool.

It's a very costly tool. It costs thousands of dollars. You need to learn, and gain knowledge about the tool through learning.

SAP S4HANA is hosted not only in AWS but also on Azure or any other hosting environment.

My company deals with all kinds of integration, including areas involving EC-ECP, ERP, course module integration, and internal integrations.

With the support environment of AWS, I don't notice any problems. AWS just acts as a hosting environment, and then maybe if it is a very stable environment and from time to time there is some maintenance done, then it is good, and there won't be any problems. For my customers who have been using the tool for years, I haven't seen any issues, to be honest. Some issues were related to the integration part of the tool. Problems are meant to happen with different tools, but there is nothing serious with the tool.

It is one of the perfect tools.

There are not many many things that are announced about the product like in the case of Oracle. I haven't heard much about SAP ECP and whether they are going to integrate the features together. I have no idea of what is going on with SAP ECP and AI. I had used Google to find out more about AI in the tool, but it did not grab my attention. I believe that the AI part will be present in the product in a couple of days.

The product is sold in Egypt and has been in use since 2016, but the support center was planned to be decommissioned. My company moved the support center from Egypt to India. My company was offered an opportunity to move to Oracle's support.

SAP S4HANA database is very stable, especially when it comes to the in-memory database and so on. All in all, AWS, I moved to ECP.

I rate the tool a nine out of ten.

I have used the solution for the IT systems of a German client and for our data center. I also build sandbox servers, and then I build SAP S4HANA. So, now I am working on a POC environment, which is a PCC that is SPS 7 with HANA 2.0 SPS 05. I'm doing this tech upgrade which is a requirement of critical use for SAP S4HANA, and then multiple systems with the current patch. I'll start with SAP S4HANA installation into the POC environment and will do this backup with Commvault. Then, I will start with the database for the HANA readiness check. And I will resize my hardware with analytics browser support, and I will do this readiness check with the functionality and run the report. So I will keep a check on if the objects come, and I have to be forwarded with this functionality, how they can soon, you know, do online check, and they will do the modifications.

The documentation part on SAP S4HANA includes the technical guidance and sites where they have been given a map of transit gateway and API gateway, and you see environments over there, and if you have to check about EC2 instance sites where they have given the prerequisites before moving to AWS. So, we have to check SAP notes first before moving to SAP S4HANA. For instance, if I want to move SAP S4HANA 2022, and I want to find the conversion from EHP 7, but then I have to check for EC2, along with figuring out which is the supported environment over there for analytics, SAP S4HANA, because they have given a set of prerequisites before moving to EC2. Then we have to stick to IPs, and we have to design the solutions, and with the system going into a POC environment, with Overlay IP and configure for the SSR application part. According to that note, we have to plan for this, whether SAP is for the HANA system or if we should go with Fiori embedded solutions. Designing should be not only for SAP ECC, but you have to be thorough with the GRC component and BW of SAP since, for SAP S4HANA, we need to do a readiness check. So we have to simultaneously do two reports in one POC system. And for DRC, we have to download some add-ons, and we also have to do some maintenance, optimize the stack files, and we have to do some uploads as a standard practice. I can say that we have to check the release node first, which is the OSB part. So, SAP HANA 2.0 SPS 05 with the latest patch we can do, and it is supported on SAP HANA 8.6 and 8.7, whereas SUSE Linux Enterprise Server for SAP Applications 15 SP3 supports SAP HANA. So it depends on how we can go fast with the readiness checks, and we can deploy this solution. You have to do modifications to your POC environment first and into this, and then, again, we have to run some prerequisites check nodes related to FI, and fewer issues should come from the frontend team, and the backend will look after SAP S4HANA. So that could be with the functionality, we have to provide MM and SD to those who can do the online custom code analysis for PPE and vendor masters, and so it could be a collaboration team with a functional team that we have to be data support, then you have to fix it here. Within a week, the POC will be from my side, and it should be from the business activity, which is potentially completed within a week. All the activities from the basic side, I can complete within a week. I have done migrations that are successfully running. With the internet supply, I have it for systems like POC and marketing. But I don't have any issue until you know the way any systems will require, whether it may be Azure or maybe AWS. But I can speak for AWS because, security-wise, it's a very good feature. When it's in Azure, we have to be aware that Red Hat support is not good. So we have to go with either Windows. People might be aware of ransomware taking to Windows servers. So I will not go with that solution, but I will go with this S4HANA on Red Hat and SUSE Linux. So, the solution could be very good over there, and we can deploy it into HANA, and I know that form part is very well that we have to do some AMI integrations for that, and we can build the servers within a day. POC from my side based on my activities can be done in seven to eight days because we have to check with our transit gateway, IP, and network integration.

We can run once the POC is done since, after that, we can run the parallel without development, quality, and production. So, if our production is on the HA part, we can take downtime for that. But before that, we have to do a parallel QA because it's very easy to move it via some transportation on the sandbox. We could move it later on to development and quality and then later on to the POC, when the live production will start, after which SAP will let us do more. It all depends on which solution we are going for, and it may be public or private editions of SAP S4HANA. With the public edition, we talk to SAP's third by itself. The private edition is chosen by companies with AWS. So if we go with the SAP on BTP public cloud, it may fall under the delay side, but with AWS, it will be fine.

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.

I have experience with SAP S4HANA on AWS. SAP S4HANA, I did my certification and two live projects, including all the features and implementation parts. Regarding SAP S4HANA, I have eight years of experience. With SAP S4HANA on AWS, I have an experience of more than two years. Considering the on-premise version, it should be more than four years.

With a stable environment, it should be running very nicely. We have 203 servers for our database. So we are taking the backup of applications and databases to be on the safer side if anything happens with the CPU of Amazon.

Stability-wise, the solution is ninety-nine percent available. So, whenever we do DR setups and everything, the availability is on from primary to secondary. So there is no loss of data with or without the switch. I guess it is available with other zones and DR always. Stability-wise, I rate the solution a nine out of ten.

Scalability is always available in the solution. So if we go with scaling up its storage part and decide to have an eighth or twenty-four TB storage is possible with high quality and production. Nowadays, forty-eight TB is supported by AWS, and the medium will be twenty-four TB for SAP S4HANA. As a requirement, we can deploy, you know, our requirement with six GB or maybe twenty GB requirement. So we have to do calculations, and the customer can tell us how much TB they need. I recommend it for those who want to analyze data and identify if they need 24 TB storage with all the backups, servers, and everything.

The size of our clients depends on the data. The size of the data depends on ECC, GRC, and BW parts.

Technical support is very good from SAP and AWS. They immediately provide us with support on the AWS side. I rate the support a nine out of ten.

Positive

I have implemented Commvault on AWS. The difference between Commvault on AWS and SAP S4HANA on AWS is the difference and saving in cost. So I deployed the Commvault solution for the deduplication. If my HANA contains 6 TB of my data, with deduplication, it will need only fifty percent size to contain that data since it can compress it. So, I could say my cost is fifty percent right now on both zones for all databases. I like Commvault's features. Also, the billing part is reduced because of AWS.

The initial setup is not complex. The initial setup is a straightforward process. For those who work on SAP S4HANA on AWS, it's simple. Otherwise, more time has to be given to development. If there is some pressure to deploy SAP S4HANA on AWS, then the person doing the deployment has to read all the books of technical documentation side, and he has to go step by step with SAP on AWS technical documentation where he is preparing the clusters or without clusters, and how the planning strategy over there, whether it's just planning to go with HSR, without HSR, or software management. So, it all would be different from the technical part or the optimization side. I did just design over here, along with the implementation part. So I know this in and out of AWS.

For a new setup, a person will have to follow the books and details given by SAP on AWS technical documentation. Considering that if certain steps are missed out, I rate the initial setup an eight or nine on a scale of one to ten, where one is difficult, and ten is easy. So, it's a very large theory part with the embedded solution, but the functional team should be given a very good exposure related to extended warehouse and other such details related to SAP. So I think if I can rate myself, I can rate SAP S4HANA's initial setup an eight to nine. It is hard to be deployed with the technical document. It's single documentation to be referred for deployment.

For HANA, I can say thirty minutes to deploy the solution. Now, consider the downloading part of the software. It should take a day. Also, a good developer can do it within a day. We have to do a testing part of hardware system efficiency for SAP. So, there's one tool available over there, and we have to download that report whether the hardware is properly working or not in relation to I/O file data logs and volumes, and then we can just do the NFS part of switching after the setup of HANA. Then, we had to do the testing part of how the backup will take time since stop and start in SAP will be very fast, but how much data load will take time, so we had to check, monitor our index servers and on an upgrade and, you know, SAP installation results, while also we to do a configuration with our paths, applications, and everything. So that should be done on SAP S4HANA.

On a scale of one to ten, where ten is the highest price, I rate the solution's pricing an eight.

I know the PTP part of the public cloud is for business analytics from the IT side. I'm not updated with S4HANA's new certification, but I did my old one. I have very good exposure to SAP S4HANA. I'm certified in all areas, not only in AWS as a professional architect, but I work on the Azure side. I work with multiple backup solutions, SAP side, and, especially, I have very good expertise in AIX and Red Hat Linux. I am very good at the cluster part and SAP workloads. I recently passed all the examinations, which were very hard examinations.

SAP I work on all S4HANA on AWS, ranging from 1610 to 2022. So, I am just doing this upgrade to SAP HANA 2.0 SPS 07 right now, which is coming to the market. And we are planning to resize that hardware. I am including multiple activities in S4HANA on AWS. So multiple activities should be SAP, patching, high base, and a few more related stuff. Also, I recently did very good projects related to the data center, which is normally for the ERP, including BW, HRM, and CRM, which are in a patch with the correct version. So all are in sync now, and so all servers are running very fine without any database loss.

With the solution, I know how to do the IT, MC, and business function part while also knowing how we can pull the data from SAP S4HANA on-premise to the automation side. I have completed my projects very fast, with and without conversion, along with greenfield and brownfield. With my expertise, I can deploy it very fast on servers, including AWS.

In IBM, they want SAP S4HANA on AWS. They are not happy with Zoho Cloud and Paradigm solutions for the last two years. So, now they are ready to move to AWS because of its speed and security features.

I rate the overall solution, including the overall software that is SAP S4HANA on AWS, a nine out of ten.

The most valuable feature of SAP S/4HANA on AWS for our large company is the robust database management capabilities offered by AWS. With extensive data and a sizable client base, this ensures seamless operations, responsiveness, and overall reliability, addressing our enterprise-scale needs effectively.

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

I have been working with SAP S4HANA on AWS for two years.

I would rate the stability as an eight out of ten. Improving it would be beneficial, especially during high-information processing times. The challenges arise due to the substantial volume of data, given our role as a company in the oil and gas industry.

I would rate the scalability of the solution as an eight out of ten. My company uses SAP S/4HANA on AWS 24/7 and we have about 100 users.

SAP tech support could be better. There is a need for more responsiveness. Opening issues sometimes takes a considerable amount of time for SAP to address. Overall, I would rate the support as a seven out of ten.

Neutral

I would rate the easiness of the initial setup as an eight out of ten. It took about a year to deploy the solution. We deployed SAP S/4HANA on AWS with a team of around 13 people, including IBM specialists for implementation and license management.

Implementing SAP S/4HANA on AWS has sped up our processes, making them more efficient. We have seen a clear improvement in our organization's performance.

I would rate the costliness of SAP S4HANA as a nine out of ten. I believe the cost of SAP S/4HANA can be a factor for smaller businesses. However, the robustness, integration capabilities, and the long-established foundation of SAP make it worth the investment, offering substantial value for the functionality it provides.

Before choosing SAP S/4HANA on AWS, we evaluated other options, including Oracle. We chose SAP because Oracle didn't meet our needs, and SAP offered more integration compared to Oracle's fragmented models for various functionalities.

My advice to new users would be to consider implementing SAP S/4HANA on AWS, especially for companies of a similar scale to ours. It is important to sync with SAP for guidance, and it is a good idea given the size and needs of the company. Overall, I would rate SAP S4HANA on AWS as an eight out of ten.

We were doing a migration from ECC to SAP.

We deployed the database from another team called ECC into an SAP HANA system. The implementation project took about eighteen months. That team handled the technical aspects. My responsibility was configuring the module for the client, ensuring it allowed them to procure materials, make purchases, and process payments.

How SAP S/4HANA on AWS integrates processes with business objectives is highly effective for any business, whether an SMME or a large enterprise. Their integration of business processes is among the best available. The specific integration and functionality depend on the subscription and the client's needs. SAP S/4HANA can meet various standards and client requirements. They offer human capital management, procurement, sales, distribution, and project management solutions. Each business element can be effectively managed through its modules, making SAP S/4HANA on AWS a versatile choice for any business.

I have been using SAP S4HANA on AWS for one year.

It is quite stable once you implement it well. Once you go live with the green light from AWS, they have good technical support for their engineers. You don't have enough capability as a service provider, and you need to call them. They have several great engineers who can assist you and ensure you don't have a failing project.

It improves your profitability. As you have designed AWS, they can assist you in ensuring that you meet your requirements.

Every time we launch a ticket, they respond immediately and assist us with anything we need. I am quite impressed with their technical support.

We use a tool called ServiceNow to log our tickets. AWS responds promptly and closes the tickets efficiently. We then rate them based on their response and our experience. I was part of the team providing feedback on their service.

Positive

Deployment is quite complex. There is a failure in terms of implementation. You didn't do due diligence to ensure that you fully understood the client's requirements and the capability of the system itself.

The database is quite easy to access, making it straightforward to gain insights into areas that need development in terms of business processes and identifying gaps. It is also essential to understand the skills requirements of your workforce. You need to assess where your SAP skills are lacking and where training is needed.

The integration with AWS helps in understanding business requirements effectively. AWS offers modules such as the Analytical Cloud Module, which can be utilized to identify areas of leakage, track revenue sources, and measure productivity and machine efficiency. 

Implementing SAP S4HANA on AWS can be quite expensive, and a proper feasibility study is necessary. However, if you have the financial resources, it significantly assists in improving productivity, scaling your business, and enhancing the profitability and efficiency of your company.

The AI integration is quite perfect. The recent developments we're using include HANA integrated with AI. AWS is emphasizing their analytical cloud, which allows us to draw AWS reports. They also have a Business Warehouse where you can store your information and then analyze it to create useful insights.

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

Currently, I'm working with SAP S4HANA as a technical support, and the technical support has been good. We have numerous customers, and we support a variety of hosting environments, including public and private clouds. Our organization is an SAP Gold Partner, and we have a technical team of over thirty consultants handling both technical and functional aspects of SAP S4HANA. We provide maintenance and troubleshooting support for the product, serving a diverse range of customers.

I appreciate the reliability and performance of SAP S4HANA on AWS. It demonstrates high integration and stability, making it a widely used choice in various industries, including manufacturing, such as factories, carmakers, and battery production. It effectively covers a broad spectrum of business areas, which is beneficial.                 

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.

I have been working for 10 years with SAP S4HANA on AWS.

I would rate it a nine out of ten.

I would rate it a eight out of ten.

Everything is alright but the area of improvement would be the support's response time.

Neutral

Our company is structured with separate teams for implementation and support. The implementation team consists of over a hundred professionals dedicated to efficiently deploying SAP S4HANA for our customers. We prioritize professionalism and ensure the software's effective implementation, emphasizing its strong security features.

It is a significant investment, around six hundred thousand dollars, and it involves both a one-time on-premises installation on servers and a cloud subscription with different flavors for SAP S4HANA.

I recommend it to other users and would rate it 9 out of 10.