SAP S/4HANA Reviews

We are mainly implementing it for finance, sales, and purchasing.

The most valuable feature is probably the full integration with the finance system. Everything I do automatically creates final or accounting documents, and the capability to make reports on different axes or the latest access is very useful.

The process for the auto administration of the system needs improvement. When I implement a new system, there's a lot to do on the technical side to make it work correctly. 

There are many checks on another SAP application server, and some implementations need a lot of recommendations. Activating the Fiori access is improved, however, it should be easier to activate a new process. 

Today, I have to find the right role, activate all the services, hope everything is correctly activated, and test it. Sometimes, it's a bit complicated to activate new features. 

Additionally, maybe the customization of the screens should allow users to add or change the layout easily. Also, there are a lot of business functions available but not activated by default. I never activate additional business functions since I am unaware they exist, so I might propose or ask to activate some of the exclusions. 

Maybe the performance of the SAP interface could be improved. When using the interface, it's not as good as the SAP GUI, for example, which is not the same type of access, but they try to sell something that should be very reactive. In fact, every time I connect, it's very slow.

I have used the solution for eight years.

It's as stable as the previous version of SAP ERP. The only thing that might need reviewing is when the system has no more space for the transaction load. The SAP HANA system is not very easy to unlock, and it's something strange as, compared to other databases, when transaction logs are full, you stop the system, run the transaction log backups, and then restart. 

When it's full in HANA, I cannot do it that way. I must make some space to let the system process the finance transaction log because it needs some additional space for the transaction logs' backup. That's not very convenient.

I am not dealing with very big customers. The biggest customer I have is mainly in the retail industry, with about 30,000 sales tickets sent back to SAP every morning. That's when the system works the most. Otherwise, I don't see any performance problems.

I sometimes open tickets to SAP. However, I usually find many answers in the SAP notes, which makes that part okay.

There's a technical setup during implementation.

In projects, we usually use around eight people.

There is an ROI, otherwise I would not buy it. However, something annoying is the huge difference between the public price and the final price for customers. It makes a good prediction for the customer, however, there's a lot of commercial communication. Speaking about product pricing, it starts to be very expensive. There is a lot of reduction when I start discussions with my customers.

Something could be improved in pricing. There's a lot of difference between casual users and expert users. There should be some categories to make pricing simpler, such as limited users and expert users as it was before. Trying to figure out precisely what they should execute according to the license is not easy. 

On the cloud side, they've changed the license price. It's not easy to have a clear understanding of the price and the value, especially if I talk about the business transaction platform. 

The BTP platform has many services, and I don't know which ones could be used or needed according to different scenarios I want to deploy. That's not very easy to understand now on the price.

The overall product rating is nine out of ten.

I am working with this system for Aalam, CAEPO, and QD. I have some experience regarding these companies. We are currently using S/4HANA for financial management, human resources, and integration with third parties. It's not just about protection, as we manage many online services like Tasee and others.

I am really happy to use HANA since it is highly syndicated with public office systems. They have integrated cloud systems and GP, sorted with security and other features connected with S/4HANA. Analytics are also integrated for reports and designations. The client is very happy to use S/4HANA.

The features from 2021 have a good database use, including PDF views. Most of the tables were reduced in S/4HANA compared to EZ. Overall, the system's indexing of tables and views is good. I have recently focused on BGP. 

I have been working with it for about five years. I am familiar with HANA.

There is no issue with the system's capability. The system is very stable.

The customer tool is very responsive. The support desk phone service is effective and meets expectations.

Positive

The customization and configuration are comprehensive. Many were satisfied before with the Python tenant CEO and MMC. Many consultants are pleased to integrate this technology because configuration is very easy, and our team is happy to use it.

The cost is quite expensive, and some people notice this compared to other solutions. 

I recommend HANA. It is an excellent enterprise system, offering many solutions with integrations to third parties and data on cloud and premises. The system's performance and backup capabilities are impressive. 

Reporting is well-supported, allowing connectivity with any system for report creation, along with mobile integration and notifications. SAP provides numerous services, especially when compared to Microsoft and Oracle solutions. While the cost for consultants and licensing is high, the benefit in terms of data and business communication is significant. 

Most businesses prefer SAP systems for company-wide communication, especially multinational enterprises using S/4HANA. 

The product rating is ten out of ten.

We have several different application scenarios that we are implementing, including procurement, sales, and finance.

SAP S/4HANA is an integrated application, which is its greatest strength. It enables the posting of transactions and allows us to see the impact across various application scenarios, providing significant benefits for business. It's a comprehensive solution that excels in everything it does.

The cost of their support services could be more affordable. It's currently an expensive proposition.

In my career, I've been using SAP S/4HANA since its inception in 2018. 

I have not seen any instability. There is no flagging, crashing, or downtime.

SAP S/4HANA scales exceptionally well. It's awesome.

The quality of customer service is excellent, and the speed is commendable. I would rate their support as a seven on a scale of one to ten.

Neutral

Once an SAP customer, always an SAP customer. I have used no other options.

The initial deployment was easy. It took nine months to fully deploy it to a working condition.

I used some sort of integrator or consultant during the deployment. This involved a significant number of team members, approximately one hundred plus.

I am not authorized to give out information about the pricing. However, the cost of support services could be made more affordable.

I would recommend SAP S/4HANA for anyone looking for an integrated application. It’s the best. I rate the overall solution a nine out of ten.

I work in the stack, and I'm on the technical side. My customers span about 20 different industries, including public sector federal government, manufacturing, service vehicles, agriculture, and mining. I don't really have a specific area. In terms of the use case of the product, HCC is now legacy, and S/4HANA is the future product for those customers running ECC, whether they want to run it on-premises, in the cloud, or in the public cloud. There are obviously a few differences there. I don't get involved in the sales side since I'm on the technical side.

It's replacing the ECC due to all the finance modules, such as ST, MM, PP. I deal with all the modules at the stack level, so I don't really focus much on the functional side. S/4HANA is integrated with the SAP interface products, like SaaS, products in the cloud, software as a service, and things like SuccessFactors. SAP sells these products, and they are integrated in the cloud, offering flexibility and scalability. The use of a memory-based database makes it more efficient. You might not think it's revolutionary, however, it's adopting new technologies and infrastructures.

Comparatively, this is a bit of a subjective question. The models are very different in the cloud, where it's all about monthly subscriptions, similar to Netflix. The pros and cons of software in the cloud are standard. Previously, models involved buying software to run on infrastructure with licensing and perpetual maintenance. Now the license model has shifted to subscriptions, with customers paying a monthly fee. This reflects the detailed terms of what products are used, their usage, and pricing. Although this transformation is not necessarily cheaper, it brings changes. Organizations face challenges like adapting to new technologies rapidly, and whether customers are early or late adopters influences their experience.

I have used the solution for 30 years or so.

The solution is very complex, and stability is based on maturity. Newer versions and features tend to be less stable. Overall, the products serve well. I don't judge businesses that run the world.

Support is a challenge. The effectiveness of the SAP support paradigm depends on particular skills. I wouldn't comment positively or negatively on the support itself. It has been a cloud scale.

Positive

It depends on the cartridges, the size of the cost, and whether it's a brownsfield or greenfield implementation. It is certainly in the millions of dollars. Training and resource support are essential.

Hacking SAP is favorable for me instead of nine and ten. It is very good for the time. Pearce rates it as a ten. At C-suite level, decision-makers, such as CFOs and CIOs, need to have an open mind and change their mindset. Prioritizing the right team is essential. 

The overall product rating is ten out of ten.

There is a feature in SAP S/4HANA that is used by reconstruction companies. This feature allows the creation of different cost objects within the ERP. Instead of assigning costs to a single cost center or costing object, you can distribute costs across various aspects such as projects, work breakdown structures, activities, networks, and problem management. This flexibility enables the ERP to handle different cost elements within the organization.

It provides a 360-degree perspective of cost segmentation and tracking all cost elements within the organization. This includes materials, projects, human resources, and equipment. The integration with the public cloud and SuccessFactors is a new and intriguing development, making it possible to manage different aspects of the organization seamlessly as if they were part of a single product.

In SAP S/4HANA, an interesting feature is the quality inspection and delivery process within the ERP system. For instance, if there is a delivery for a project part that requires quality inspection and receives feedback from the customer, this can be recorded through the mobile application. The responsible person can visit the site, open the system using the mobile app, and add remarks and notes directly into the system without the need for paper or extensive communication.

Everything is automated and all information is collected and reflected in the system, providing a complete history of any project. This comprehensive approach ensures that SAP S/4HANA effectively meets the requirements of any construction contract, demonstrating SAP's excellence in this industry.

SAP S/4HANA offers two deployment options: the private cloud and the public cloud. The private cloud is a comprehensive solution. While it does require numerous approvals, it is a highly reliable product. However, when it comes to continuous improvement, the public cloud excels. My previous explanation focused on the private cloud. Medium-sized companies that cannot afford the private cloud often opt for the public cloud. However, the public cloud does not include all the modules available in the private cloud. Therefore, it is essential to enhance the module offerings in the public cloud.

For example, in the construction industry, companies needing advanced project systems often have no choice but to make a significant investment in the private cloud. SAP should invest more in expanding the features available in the S/4HANA public cloud. One area for enhancement is predictive analysis. SAP has developed solutions on the Business Technology Platform, including AI and machine learning products. However, there is still no packaged ERP solution that automatically delivers these features to customers.

It should provide better integration of AI products through the Business Technology Platform, providing storage and examples of best practices for various industries. Many customers are interested in AI but are unsure how to implement it within SAP applications. SAP, a reputable company, already has best practices, but it should expand its library to include more examples of AI applications. 

The solution is scalable. We have two companies, one have 150 users and the other habe 50 users using this solution.

Partners provide support and their cloud support is excellent. They respond immediately to requests. They have an integration process without delays and a customer interaction center. If we have any case requiring immediate support, we can call them directly and receive support promptly. You can schedule meetings with experts and easily make appointments. Additional chat support is available as well. The support challenge is already addressed and accessible, allowing for quick resolution of issues.

The initial setup of SAP S/4HANA is moderately complex, but there are not many use cases, especially in the Middle East. 

For the cloud solution of SAP S/4HANA, maintenance is not required. However, this is not the case for the on-premises solution, which does require technical support.

When you are using SAP S/4HANA for the construction industry, it is crucial to understand the specific needs and processes of construction companies, which are often based on the number of projects they handle. To effectively utilize SAP S/4HANA in this context, it's essential to explain how the system can support and streamline business operations.

In the construction industry, projects typically begin with a tendering process where companies look for construction services. In terms of presales, a system like SAP S/4HANA is invaluable for planning opportunities by incorporating initial construction rounds and cost estimates to determine pricing. These processes can be efficiently managed through an ERP system.

Once a project is secured, a new project is created in SAP S/4HANA, and WBS is established. Integrating the ERP with CAD solutions that contain the project drawings is crucial for reviewing cost elements and budgets. Based on the budget, POs can be issued to vendors for materials, automating the procurement process.

Cost objects related to the WBS or network are tracked using fund management within the ERP system. Integration with SAP SuccessFactors is also important to hire and assign employees to specific projects, ensuring accurate tracking of progress and costs.

The system enables tracking project progress, completion percentages, and project costs. Reports comparing planned versus actual costs can be generated at any time. Project invoicing and planning are based on completion percentages and material consumption, as construction projects do not have regular invoicing. Instead, settlements are based on the completion percentage and material usage, allowing for accurate customer invoicing and cash collection.

Integration with service sheets ensures that customers can approve completed work. Once the work is confirmed, the system can automatically generate invoices and initiate the collection process. Additionally, the integration with tools like AutoCAD enhances the visibility and visualization of project completion within the ERP system, eliminating the need for external systems to track progress.

By leveraging SAP S/4HANA, construction companies can manage their projects more effectively, ensuring seamless integration of processes, accurate tracking, and improved financial management.

I recommend S/4HANA for various industries, except one. I cannot recommend it for that industry due to affordability concerns. However, for manufacturing, utilities, public sector, construction, and real estate, S/4HANA is the number one choice. But when it comes to the automotive industry, my recommendation is to go for Maxwell Dynamics.

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

I use the solution in my company to pay for procurement, finance, and asset management, and we use all its modules across the board for everything.

I think the tool is very good for large organizations, and to handle large volumes of data that is used while being user-friendly. The documentation and storage procedures and other things are clearly defined for end users.

There is a need to improve the migration process.

I think that clearer guidelines on implementation for faster data migration need to be improved a little bit, as transforming the legacies to SAP S/4HANA is complex. When there are business requirements, the business needs to work closely and understand that data migration and cutover activities need to be improved to meet the production goal.

I have been using SAP S/4HANA for more than five years.

Sometimes we have issues with the performance and other things, especially when you don't do proper testing and other things, or when you basically miss some of the cutover guidelines or steps in implementation and deployment, but we get good support from SAP.

It is a scalable solution.

I think if you go for public cloud, the solution's technical support is not great and I would rate it as a five out of ten. If you have a private cloud, I would rate the solution's technical support as a seven or eight out of ten.

Neutral

The product's initial setup phase's complexity or easiness is something that depends on many factors. If you have a very good SI and, you don't need to look at the setup process. With ClamSAP and SAP Cloud ALM, things are a lot easier now. Compared to old days when we used to use SAP Solution Manager 7.2, things have become a lot easier now with SAP S/4HANA and every year it is being improved.

Deployment is like a thorough cutover activity that needs to be studied. Data migration, configuration, code, and everything need to be cross-checked or double-checked, and some kind of production verification or technical verification needs to be done at every stage before moving to the next one, making it fairly complex and there are a lot of people involved in it. The aforementioned areas can be considered as the downsides of the tool when compared to Salesforce and other applications. SAP S/4HANA handles large volumes of data when compared to other applications.

The solution is deployed on private cloud, public cloud, and on-premises.

With ClamSAP and fast-track implementation guides, you can implement the tool in three months.

The tool's ROI is pretty good, but it takes a long time to see any returns on the investment. SAP systems are implemented to last, like, maybe twenty, thirty years. The ROI will come back, but you won't see any benefits in the near future after its purchase. It is a long-term solution that you implement and move forward for twenty or thirty years, and I think the return on investment is good. If you're going into SAP S/4HANA, it is not like there is a need to bring in the whole suite for your whole business and more on to SAP S/4HANA. The ROI is good.

It is an expensive solution. The tool's price can be reasonable for large organizations, but it might not be suitable for small organizations with a small number of users.

In supply chain management, my company looks into MRP, forecasting, stock forecasting, and everything, and then the management, specifically invoice management, for processing payments.

In the finance and accounting aspect, the tool does end-to-end accounting, budget planning, and forecasting. The tool also does postings, Cl. balance, reconciliation, and all that sort of stuff.

The tool has improved the efficiency of the business processes, and I think it provides the best in-built practices as a solution, readily available, and it can be easily customized to suit your business. Everything, like the end-to-end processes, are all predefined, and the best practice for the solution is available in the product during the setup, which is really useful.

With the tool, you have real-time data and time reports. It is not like it was in the past when it was in-memory, as it used to take longer to generate the reports. Now, it provides reports in real-time, so it is really good.

Real-time insights have impacted the decision-making processes since, I think, we will know when customer orders are coming in, and we can see the demand go up pretty quickly. In real-time, the management can make decisions about reordering, manufacturing, and production planning, which is a lot on a dashboard where it is tightly integrated and helpful in many areas.

For the migration process, there is a learning curve. The end users may have to be trained. The migration process has a lot of paperwork and manual activity that has become redundant, which is good and bad since the learning curve is now a bit high. People who are near to the system need to be trained, which is a bit of a downside, but in the long run, it is okay.

I suggest the tool to large organizations, complex businesses, multiple companies, or entities with hundreds and thousands of users and employees, as it would be good in such environments. In small organizations, I wouldn't suggest SAP S/4HANA.

As maintaining and changing the tool is very costly, I rate the solution a seven out of ten.

There are some main use cases for SAP S/4HANA because mainly we work with manufacturing customers.

I have mostly manufacturing customers.

The most useful features in this product are the real-time reporting and the complete integration between various functions.

The in-app integration works across all functions.

Since it's real-time, the reporting is fully integrated, and the people taking the reports don't need to reconcile between different functions because it is real-time with mission and completely integrated; that is the main reason why people go for SAP S/4HANA.

SAP S/4HANA is real-time and fully integrated, and SAP is always proactive in providing solutions for new scenarios or new business processes. It's scalable, so if an organization is small today and is working in one industry, tomorrow it can move to multiple geographies or industries and the size grows; it's completely scalable to a very large extent.

The cost is definitely high, so SAP does have a growth solution, which is slightly cheaper compared to other offerings with SAP.

A lot more customers would adopt it if they reduced the price by around twenty to twenty-five percent.

I'm working with a partner, and I've been working with SAP S/4HANA for the last eight to nine years.

I have faced no issues with stability or upgrades.

SAP S/4HANA is easy to scale in my opinion.

I would rate the scalability a ten.

The support that SAP provides is very good.

I would rate the support a ten because there are a lot of knowledge-based articles published, and most of them are available online.

Positive

I don't have much experience with SAP Business One solution or SAP Sales Cloud, only SAP S/4HANA.

It is easy to set up SAP S/4HANA now.

I would rate the setup a nine.

I'm expected to leave this for her, so I don't have expertise in any other tools such as data mining solutions, business intelligence, or other ERP tools. I would rate SAP S/4HANA a fit in.

SAP S/4HANA provides a standard setup process. Several third-party tools are available to integrate with the SAP ecosystem. Some customers of our organization find SAP S/4HANA very easy to use, and some are adopting the solution due to prior familiarity with the SAP ecosystem. The licensing changes implemented in Oracle JD Edwards have also made a few customers of our organization adopt SAP S/4HANA. 

The Order-to-Cash feature is indispensable and irreplaceable in SAP S/4HANA. Almost every customer I have worked with in my organization finds the Order-to-Cash feature extremely valuable. 

For Order-to-Cash using SAP S/4HANA, a company needs to consider the local regulations at one point. SAP can help with all such local regulations. I wouldn't recommend SAP S/4HANA for a small or medium-sized company.

The integration capabilities of SAP S/4HANA are as good as those of its competitor products. A reliable middleware product will be needed in SAP S/4HANA especially if discrete ERP, MES and CRM are present in the project. The integration of SAP S/4HANA will also be dependent on the strategies and vision laid out by the enterprise architect. Integrations for the solution can be done in both ELT and ETL, and both has its pros and cons.

The analytics part of SAP S/4HANA needs to be improved. The analytics feature provides decent warehousing and reporting capability, but the AI/ML components of analytics need improvement. Almost all current versions of different SAP family products either lack AI capabilities or are rudimentary. A plethora of third-party tools exist that can bring AI/ML capabilities to SAP S/4HANA, but such capabilities should be natively provided in the product. 

I have been using SAP S/4HANA for two years. 

The stability of SAP S/4HANA is better understood by considering the whole SAP ecosystem. For instance, if I carry out a brownfield implementation, there can be a situation where a customer doesn't identify any improvements in their business process after deploying the solution; in such cases, they might prefer to revert back to the older process, such changes will be inherent to almost every system, so the stability of SAP S/4HANA varies from customer to customer and the complexity around the product. 

The solution is highly scalable. Our organization was catering SAP S/4HANA across 47 countries, with an average of 60 to 70 users per country. A severely large team of at least 50 to 60 professionals is required for the deployment and maintenance of SAP S/4HANA. A company usually adopts SAP S/4HANA when there is a dire need for such a solution and not when competitors have been identified to make a transition. 

At our company, we are satisfied with the tech support. I believe service providers like SAP are always willing to help anyone out with product issues. If users are able to articulate the problem well enough, it becomes easier for the tech team to comprehend the situation and provide an ideal solution.

If a user is unable to articulate the product's issues, then there is too much back and forth through tickets, and it takes a lot of time to resolve the issues. A good enough articulation of the problem in a conversation with the vendor's support team will resolve the issues 90% of the time. 

The deployment time depends upon the complexity of the environment in which the solution is being used, the business environment, the number of divisions in the company, and harmonization needs. Theoretically, a greenfield implementation of SAP S/4HANA can be carried out in four months, especially if SAP RISE is used. 

The deployment process of SAP S/4HANA involves business processing, data architecture, fit-gaps, and the selection between on-prem/cloud and one model rollout at a time. The aforementioned deployment process is the most relevant one because it reduces business risk.  The models or business entities are rolled out one at a time due to the risk conceptions of customers, so either the finance, manufacturing, or another division is shifted to the new system one at a time. 

SAP S/4HANA is definitely a valuable product. For the majority of the customer implementation of the product through our organization, I have rarely used the greenfield path. Our company once took the greenfield approach for a customer who was using multiple ERP solutions, including JD Edwards, PeopleSoft and EBS.

The aforementioned company had the requirement to harmonize and that's why a greenfield approach was followed for SAP S/4HANA implementation. Any company using SAP S/4HANA won't find trouble in gaining value from the product.

A company will only struggle with ROI or obtaining value from the solution when SAP S/4HANA is not a good fit for them. For instance, if a small company with a single location presence and around 1000 users adopts SAP S/4HANA, it's very likely that they won't find a suitable ROI. 

I don't think any company would find the product expensive. For a cloud version, there is always the factor of how much data transfer is required, and the cost will escalate very quickly as for each data transfer the hyperscaler will charge it. The size of the company, the complexity of data transfer, and the sensitivity of the operational run rate are factors that will influence the cost of SAP S/4HANA. 

Most of the customers of our organization who are adopting SAP S/4HANA already have an SAP product in their ecosystem and SAP S/4HANA provides an upgradation path to them. The majority of companies who implement such aforementioned upgrades don't always use a brownfield implementation, which translates the whole business process into the new system. Implementors are choosing a feedback and target process utilization path for SAP S/4HANA, a bluefield process.

There is also another greenfield approach for SAP S/4HANA implementation that involves beginning the implementation process from scratch. I have used all the aforementioned field processes, but mostly the brownfield path because most of our organization's customers prefer it for migrating from older processes. 

One of our customer's SAP S/4HANA migration process began in 2017 and it's still ongoing. For the aforementioned customer, the SAP S/4HANA deployment process will take six or seven years because of the geographies the customer operates in and their own unique business processes. I would rate the solution a seven out of ten. 

I wouldn't advise businesses without a multi-geographical presence to adopt the solution. One of the prime advantages of SAP solutions is the wide knowledge of diverse geographies over several years. SAP has been successful in building numerous out-of-the-box business processes over the years. Customers looking for a solution like SAP S/4HANA always have a choice if they want to use the out-of-the-box process or if they want to build their own, but SAP is able to provide a unique process for each country, whether it's China, India, or Germany.  

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. 

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.