SAP S/4HANA Reviews

The solution's use cases depend on the market in which clients use it. I usually work with manufacturing companies. They used the tool for manufacturing, using whatever they needed to implement SAP independently. Warehousing users use the solution to manage inventory. Both retail and manufacturing markets use warehousing, and that's another big area where the tool is used.

The main focus of moving from an old ERP to the solution is that the HANA database runs in memory and quickly answers questions. Since it's already in memory, reports need not be created after the data is loaded in the transactional tables.

The solution's most valuable feature is integration. You're still talking about modules, procurement, and business partners. All of these are different modules in SAP S/4HANA. Everything is connected easily because of the integration of the same database in the memory. It's already connected there. You don't need to change the view.

You can change the view from one perspective to another, but it's mostly the same thing. You are not jumping between modules in such a way that you are seeing the same data differently. Since you see the same database, you are not making mistakes when seeing the customer in procurement or inventory. You see exactly the same data because it comes from the same view.

Everything is integrated in that way. There are no more mistakes in the data not being updated. Every time you access something, it is already updated in real-time. From a business point of view, you see the same figure no matter how you access it.

SAP S/4HANA is an expensive solution.

I have been using SAP S/4HANA for 10 to 12 years.

If there are no customizations, SAP S/4HANA is a very stable product.

You can add more transactions, materials, customers, and vendors. Scaling the solution is not a problem because you are in a private cloud. You need more servers, but the system is prepared to work that way. The solution is more suited for medium to enterprise businesses. Some small customers want to have this kind of ERP, but the problem is that it is expensive.

Without any changes, the solution's initial setup is easy. The process is very, very easy to implement. If there are changes, we need to recommend that SAP incorporate those modifications because they may be standard.

That is a long shot because SAP filters everything, as there are many customer requests. They filter them and implement only the ones they think are useful to everybody. Those modifications are taken into account for the next release. It's a problem for the customer if they need something that is not standard for SAP S/4HANA. If it is a standard for SAP S/4HANA, it's easy to implement.

I rate the solution’s initial setup ten out of ten.

Some customers needing this kind of software don't consider the costs. They think about the profitability they can achieve with the solution's implementation. People concerned about the costs need to evaluate whether implementing this system is profitable.

It depends on the perspective. You need to consider whether this investment is enough to get you to what you are looking for. It's basically a market evaluation of what you are doing.

With the solution's real-time analytic options, you don't need to use anything else. You already have the data in memory, and you can build any query to extract something that was hard to extract earlier.

The business process works fine because there are not too many steps now. Since everything is in memory, the processes are simpler than before. The business processes are cleaner because you don't need to go through too many steps to get the results done. You now have a 360-degree view of a customer.

Whether you are accessing the customer by invoicing or by a business partner, you get the view of these customers all around, and you don't need to jump between modules. Everything is now more easily integrated.

The first approach was to have this ERP implemented on-premises. Now, the solution is going to the cloud. The idea is to deploy the tool depending on the requirements of the customer or the client. The products are already built, and you don't need to do anything else.

You are accessing the solution in a way that is already customized for the customer. You don't need to do anything additionally. The ERP is already ready to be used. Then, you have hybrid implementations, partly in the cloud and partly on-premises.

Also, you can have everything on-premises but in a private network. So, it depends on the client's requirements. Everything can be done depending on the client's requirements, but the solution can be deployed everywhere.

Customers are currently looking to migrate from ECC into S/4HANA. The improvements or benefits will come from implementing S/4HANA. These customers are not so worried about how it is going to work because they want to do the initial migration. A lot of customers are doing that at this time, and it is a potential market for us as implementers on which we can rely for a long time.

SAP provides a module that facilitates migration from any system, not only ECC, to SAP S/4HANA. The idea here is to provide layouts already built. The customer or client only needs to populate this layout and then push it into the solution, which is easy. However, depending on the client, some things may not completely reflect what the customer or client needs. So, they need to do customizations.

Those customizations need to be done before in SAP S/4HANA, and then this special module for data migration needs to be modified. It could be totally different from what the standard SAP is doing. So, they need to do other programming to get this data loaded into specific modules being modified for that client.

The idea is to get the benefit of what SAP S/4HANA is offering. The idea is not to customize anything. However, we always have something that is not specific for a client and needs to be modified. The module itself is capable of modifying what is required. If you modify the tool too much, the next version will not be implemented quickly.

That's why the recommendation is not to modify anything. The processes already built into the solution are enough for any kind of market. However, if you are doing it, you need to comply with what SAP recommends. If the new version is coming, you can implement it quickly, or you will have issues like in the past. Heavily customized ERP systems are complex to migrate to the new versions.

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

We use SAP for business processes.

SAP S/4HANA has significantly improved processes by enabling a more intelligent enterprise. With tools like SAP Business Technology Platform services and AI scenarios, data processing and decision-making have become much smarter and efficient.

The features that I find most helpful in my day-to-day operations with SAP S/4HANA are primarily related to data management. Real-time data analytics has significantly enhanced decision-making processes by providing instant insights into business processes and trends. The user experience with the SAP S/4HANA interface has also seen notable improvements, particularly in terms of a more friendly and personalized UI.

There is room for improvement in areas such as security features within SAP S/4HANA, which could further enhance the overall usability and effectiveness of the platform.

To make SAP S/4HANA better, there's a focus on enhancing responsiveness and reducing operational costs. This includes improving automation within the system to address strategic needs and accommodate users who primarily speak English, which is an ongoing effort.

I've been working with SAP for around seventeen years, specifically focusing on SAP S/4HANA since around 2015. I work with SAP as a partner.

In terms of stability, I would rate SAP S/4HANA at around nine out of ten. 

The initial setup of SAP S/4HANA was challenging, but it's vital to understand the manual innovations, tool design, and integration, especially with new features and core aspects. Learning and staying updated with new innovations is crucial for IT professionals, as it provides valuable insights into business processes and concepts. The duration depends on specific business requirements, typically taking around four months to complete.

I would rate the pricing at around six to nine out of ten depending on the edition and deployment type.

SAP S/4HANA's integration capabilities are highly impactful on the IT ecosystem due to its seamless integration with both SAP and non-SAP systems through the integration suite. I would recommend SAP S/4HANA to anyone who needs an efficient ERP system with a user-friendly interface, strong security features, and the flexibility of deployment options. For those concerned about security, on-premises deployment is recommended, while for others, a hybrid approach with cloud integration can be advantageous. 

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

I have two major clients for SAP S/4HANA. The first is in the UAE, using real estate modules, and the second is US-based, CVS or Century Business Solutions. In the US, the solution handles all customer-related activities like sales orders, accounts receivable, accounts payable, and refunds, integrated with both mobile and web apps. For the UAE client, it manages real estate information, allowing customers to place orders and receive offers online via mobile and web apps. After customer confirmation, it facilitates contract agreements and integrates finance and accounts-related information. 

Clients share their requirements via emails, and if I have any confusion, I directly communicate with them through video or audio meetings using Google Meet or other resources. As a technical consultant, I handle both technical and functional aspects. We primarily use FSR forms, which clients deliver via email. We read and verify these requirements from the customers and strive to use standard functionalities to the fullest and implement the required functionalities directly using the standard system.

Regarding migration from previous system to SAP S/4HANA, it had no negative impact on business productivity as data was smoothly transferred using tools like BDCs and LSMWs. Data is crucial, and SAP S/4HANA easily integrates with previous systems, ensuring no errors or hurdles for clients.

SAP S/4HANA delivers all essential possibilities to customers for various sections. In the current modern age, we use SAP for graphical outputs, reports, and smartphone accessibility. If users want to see financial outputs via diagrams, we use SAP by Design. For specific confirmations via mobile app or web app, we use few other applications. If users want only source forms and not hard copies, we use AR forms.

The most advanced functionality in S/4HANA is the OData service. It's crucial because everyone wants to integrate third-party applications with SAP S/4HANA. SAP HANA uses advanced OData services, integrating with Azure HANA. We also use SQL services and Java security, allowing every language to interface with SAP, choosing tools specific for our requirements.

In my opinion, there's room for improvement in SAP S/4HANA based on customer requirements. The solution already includes advanced technologies like AI functionalities, but improvements can be made in areas like UI and pricing. For example, making the UI more user-friendly or reducing the cost could enhance the overall experience for clients and customers. The goal is to provide everything customers need with just one click, ensuring convenience and efficiency in accessing information and performing tasks.

In terms of stability, I have a good impression because when we meet all customer requirements, they are satisfied and find it reliable.

I would rate the scalability of SAP S/4HANA as good, around eight out of ten. Our clients vary in size, ranging from small to medium to large enterprises, covering different levels of businesses.

My experience with the technical support, is about a ten to twenty percent involvement on my end since I primarily handle technical aspects.

My experience with the initial setup of SAP S/4HANA is quite easy, as I've been working with SAP for around nine to ten years. Regarding deployment time, it depends on the complexity of the requirements, ranging from a few days to a maximum of one month.

As for pricing, it depends on the business size and flow. If it's a medium-sized business, it might seem affordable, but for larger businesses with complex processes, it could be considered expensive.

If a client faced challenges with their previous system, I would directly communicate with them, understand the issue, and demonstrate how SAP S/4HANA can address specific reports or modules, ensuring around a ninety-nine percent success rate in resolving issues.

I would rate SAP S/4HANA a ten out of ten because of its seamless integration with third-party software and ease of use.

Overall, it's being used mostly for analytics. It's basically the movement of goods between various warehouses. That is also pretty much used.

The output that we get, maybe the analytics part, is even faster compared to what we used to see on the ECC system. It used to take a few days for the analytics reports to come out of the loading, etcetera. It took a lot of time. However, now it's just a matter of a few hours to get the reports generated. That is one of the things.

I don't see any additives as of now. Any of the standard APIs or whatever is available to be integrated is done so easily with the S/4. 

It's been four or five years.

The team regularly checks on the logs, audit logs, et cetera, and they review a few important KPIs as well. So no issues are present as of now since everything has gone through proper testing, et cetera.

There are no issues in terms of onboarding. Probably, in terms of scalability, we have to plan for that.

The initial setup was kind of complicated. It went through with proper planning, et cetera.

We have separate teams handling the introductory part and the application parts or the tech team's parts.

Moving from ECC to S/4 is a kind of transformation program which involves a lot of changes, including organizational change planning. That is very crucial. All these things should be taken care of when planning this transformation. 

I would rate the solution nine out of ten.

I'm an architect. S/4HANA is an intelligent enterprise. When an organization needs an application or software to run its operations, S/4HANA comes into play. SAP is the market leader in ERP. S/4HANA is not a traditional ERP anymore, but an intelligent enterprise. That's the power of S/4HANA.

The integration capabilities of SAP S/4HANA and AWS are excellent.  SAP S/4HANA is an intelligent enterprise. It can harness data and provide the right data at the right time for decision-makers to carry forward the operations. 

For integration, you have SAP BTP, a platform as a solution that can work with S/4HANA. There are also other tools like SAP CPI and SAP Process Orchestration. So, there are a lot of tools available for SAP to integrate with the outside world.

AI capabilities are good with SAP S/4HANA. When WE combine SAP S/4HANA with SAP BTP, there is a use case in the healthcare industry where it can detect yearly symptoms and save lives. This is referred to as SAP Business Technology Platform.

S/4HANA is a very large application. There is no one specific tool I can pick. It depends on the customer, the use case, and what the business needs. Different industries will find different business functions helpful. 

If it is a construction industry, probably something related to the construction function will help you. If it is a logistics industry, if it's a logistics function, it's a separate one. So, depending on the type of industry, you will have a different business function that will come into place.

Most of the Fortune 500 companies use SAP S/4HANA, so I don't think it's unfit for any particular industry. But if a customer has limited requirements, like only sales activity, then they can choose Salesforce. They don't need SAP S/4HANA. It's not a proper comparison because we can do a lot with S/4HANA, like HR, sales, distribution, production planning, quality management, transport management, and more.

In future releases, I would like to see more availability zones and VPCs so customers have more freedom to choose. Also, more training so customers can utilize the training enablement.

I have experience with S/4HANA for around seven or eight years.

AWS is premium. From a cost perspective, AWS might be on the higher side. The users have to check if the required availability zone is available in the customer's region. Sometimes, only Azure is available. I don't see any issues of that sort. It's very mature.

The customer service and support are very good. There are options for SAP called RISE with SAP. You can make a note of it. With RISE with SAP, customers can choose their hyperscaler. It can be SAP HANA Enterprise Cloud, AWS, Azure, GCP, or even Alibaba. When it comes to support, you can go with a single contract with the RISE with SAP option, so you get one support contract.

The support comes from SAP, not AWS. The support is the same for AWS or Azure. Some customers will enter into an exclusive contract, while others will go with a generic contract. For the sake of an answer, I can give it an eight out of ten.

Positive

Every implementation has its challenges. Sometimes, the challenges are with the project timeline, sometimes with resource availability, and sometimes with the business process meeting the requirements of the business. 

Especially with a product like SAP, such a big project, there are challenges, and that's when project management comes in to make sure the project is delivered successfully.

We have multiple deployment options. We have S/4HANA on public cloud and S/4HANA on private cloud. Depending on the customer's appetite, we can choose which one they want. 

Even within the private cloud, we have options like greenfield, which means we implement from scratch; brownfield, which means we convert an existing system; or bluefield, which is loosely related to a data migration approach. So, it depends on the customer's appetite.

SAP S/4HANA is a solution, and AWS is just an infrastructure provider. Some customers might prefer S/4HANA on Azure or Google Cloud. It depends on the customer's requirements.

Customers will have access to the latest innovation from SAP and will be updated with the business process libraries. They can stay ahead of their competitors in the market because of the innovations provided by SAP. 

They also have lots of tools or options available to integrate with the outside world.

I would recommend using it. Overall, I would rate it an eight out of ten. 

Based on my knowledge and experience during the transformation phase with the tool, I think the product provides things in a very planned manner in terms of the data, migration with different phases and testing, and servers to move to, making it a very easy process and very comfortable to move to it from another solution.

The product's high cost is an area of concern where improvements are required.

I have been using SAP S/4HANA for a few days. I am not a user of the tool, but I work as a support in my company to help integrate the solution with some other software products. I look into the secondary sales systems. I am not the core user of the product.

My company's technical team and IT team may have had the need to contact the solution's technical support team.

My company switched over to SAP S/4HANA from SAP ECC, which was a legacy system and did not operate in real-time while there was need for some customizations leading to different challenges. Globally, every organization has moved to tSAP S/4HANA for improved processes and real-time analytics. I think the core objectives of the founder of the organization stems from the aforementioned details.

The solution can be deployed and implemented in a year because my organization has a very huge infrastructure of SAP. My company has bought different modules and data from SAP, so going through the documentation and everything takes time during the implementation phase.

Whether the product is expensive or not is something that may vary from company to company. If I consider my organization, I feel that the product is a bit expensive. Myorganization is not currently using big modules like S/4HANA and the other different modules. Though National Food Limited is a global organization, I think the tool is costly. National Food Limited wants to grow up with the technology since the founder states that they have a certain benchmark in the world. The product is worth the money.

My background is in providing support for software tools our company uses for order booking and for secondary sales software, which consists of mobile booking for markets and stores. For analytical dashboards, my company uses Power BI, which is connected to the software tools we use in the company. For integrations with SAP S/4HANA, my company has connected a few databases with inbound and outbound APIs.

My company is very satisfied with the tool and I believe that it is going to be a very good transformation for our organization. Before my company used to work on SAP ECC, and now we are migrating to SAP S/4HANA. Everyone in our company has very good experience with SAP. Now, my company is going to go live in a week or two.

My company uses the tool to make end-to-end processes easier, and we have a consultant named Reynold from PwC. My company uses the consultancy service offered by PwC to manage National Foods Limited and SAP.

My company plans to use the tool for real-time analytics or decision-making. I think the founder of my organization admires the fact that with SAP's technology, we are able to use real-time information and it is a good improvement in the strategic area and the directions. SAP Integrated Business Planning (IBP) Forecasting Algorithms can definitely be helpful.

I am not able to comment much about the solution since my company is still in the transformation stage.

The user interface of SAP S/4HANA is user-friendly. In different modules, like financial and production ones, I have experienced the use of the tool with different people who have mentioned that it is a very helpful product for them.

I have worked with Fiori UI/UX and also with SAP IBP and SAP SAC. In SAP, the dashboard can be managed in real-time.

The product helps increase the data processing speed, especially in areas like workflow. When it comes to the financial aspect, the tool provides very strong financial and credit limits, which is a very good feature of the tool, as it can help the organization move to a certain level.

I rate the tool a ten out of ten.

The POD applications are very useful to us. There are a few POD apps which we are using for the different business scenarios. They are quite interesting.

The initial setup is pretty straightforward. The documentation is very good.

The solution can scale well.

The solution is stable.

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.

We've been using the solution for the past year or so. It hasn't been that long.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's very reliable. 

The solution is scalable. At the same time, it depends on where you deploy your systems. If you deploy your systems in Azure, then it would be using the scalability of Azure. If you deploy in AWS, it uses the scalability of AWS. If you deploy in a virtual private environment, then it depends on where you deployed the system. At the same time, it depends on being compatible with all these different hyper-scalers. For the most part, it goes pretty well with the different platforms.

We are deploying the solution in different countries. Currently, we have close to 10,000 users working in SAP. Yearly, we do the deployment in multiple countries. In two months, we deploy in one more country. There will be another 200, 300 more users will be coming. By the end of this year, there will be 2,000 more users. Currently, around 10,000 users are using this application.

The SAP S/4HANA technical support is mainly with the service provider. When you deploy SAP, you have different support teams. Most of the time, you will have a service provider or a supplier that you would be associating with. You will have a kind of application management or infrastructure management support with that vendor. For example, IBM, Capgemini, Accenture, DXC. They are the different vendors. However, then you get the OEM support via the SAP Support Portal for product-related issues. That support has got different priority levels based on the importance. Generally, we know how the SAP support works and it's acceptable. We're satisfied with the level of support provided overall.

The initial setup isn't too difficult. It's pretty straightforward for the most part. SAP has got some good documentation and there are different migration scenarios and implementation scenarios you can work with. With the help of documentation, things are pretty straightforward. 

Most of the time, you do the SAP deployment or the migration with a partner. SAP has got certified partners to help with the implementation.

SAP has got different license mechanisms. It depends on how many SAP products you run and then how do you negotiate with the SAP teams and what kind of offer you get. At the same time, generally, everyone says SAP products are a bit costly. 

Some of the SAP systems are licensed based on the number of CPUs that are being deployed, and some of the SAP products are licensed based on the number of primary users, and some of the SAP systems are based on the database footprint. Different SAP products have different license mechanisms, so there should be a person who is knowledgeable about SAP that can understand and then review the licensing agreement and get the right SAP product - and perhaps help negotiate the price.

We are customers and end-users.

We have around 25 different SAP products. We are using SAP S/4HANA in our company.

The production and the test systems are deployed in the virtual private cloud on-premise, and we have sandbox development and quality systems are deployed in the Azure public cloud.

I'd rate the solution at an eight out of ten.

I use this solution because it provides immediate insights into financial affairs without waiting for month-end reports.

The ability to access real-time data analytics is crucial, as it supports events or calls that require immediate attention and decision-making. Utilizing Virtual NGINX has been quite effective for this purpose.

The user interface is less friendly than that of View ID, however, it is more robust overall. I can perform a lot of data manipulation directly on SAP using S-One, without having to resort to Excel, unlike with View ID.

I have used the solution for another SAP for a total of three years.

During my time with Angleton, we relied on a private cloud, and accessibility became literally impossible whenever the cloud service provider experienced downtime.

I highly recommend this solution. It is very easy to scale within businesses, especially when a new business falls within the range.

I absolutely would recommend the customer service.

Positive

This was my first encounter with ERP, and I have not used any other ERP solutions.

I joined the company when the migration was completed, so I am not aware of any setup challenges.

This was my first encounter with ERP, and I have not used any other ERP solutions.

Previously, using a private cloud meant that management could not always access data due to possible downtimes from the cloud service provider. It is crucial that management does not simply have to wait for month-end averages to understand the financial affairs of the business. Real-time data analytics with Virtual NGINX has been very helpful, and scaling within businesses when there is a new business under the range is also straightforward. 

I would rate the overall solution nine out of ten.