SAP S/4HANA Reviews

SAP S/4HANA is used for business applications. At our company, we have implemented the solution across nine modules which include CO, SD, MM, HCM, PM and more. 

In the past few years, there have been drastic changes in application environments; the SAP Fiori apps with numerous dashboards and KPIs provided by the solution help our organization adapt to the industry transformations. The SAP Fiori apps of SAP S/4HANA assist in decision-making processes. 

The SAP Fiori apps can provide an excellent and comfortable user experience. The aforementioned SAP S/4HANA apps can be integrated easily with almost any portable device so that POs and business documents can be approved on the go.

The classic interface of the solution and the configuration at the back-end or at the consultant's end needs improvement. 

I am a user of SAP S/4HANA. 

I would rate the stability an eight out of ten. SAP S/4HANA offers impressive stability and functions well without any errors. 

I would rate the scalability of the solution a seven out of ten. The product is majorly for enterprise-level customers and offers great scalability. The classic application feature of the solution needs drastic improvement, but the SAP Fiori app already provides all the advanced features. There are more than 100 users of the solution in our organization. Our company uses SAP S/4HANA, majorly for large enterprises. 

As part of our company, we engage with technical support as consultants and a response is obtained in three to four hours. The response time of technical support should be improved by the solution provider. Whenever certain business operations cease in our organization, we seek immediate support from SAP, but it's not available presently. I would rate technical support a six out of ten. 

Neutral

At our company, the previous legacy software was not supporting us with reporting features and did not facilitate business operations. The software was developed using old technologies, and our company management division was expecting a top-tier solution with dashboards, analytics, and KPIs to rebuild the business operations; this was the reason why our organization shifted to SAP S/4HANA. 

The initial setup of SAP S/4HANA is difficult as, for every module, a dedicated consultant is required. For instance, if you need to implement nine modules, nine individual consultants are required to configure the product. In addition to the aforementioned team, a technical professional will also be needed. I would rate the initial setup a four out of ten. 

Our company had the target to deploy the solution in ten months, but it took sixteen months. For the deployment process in our organization, we used the ASAP methodology for implementation, and it was completed in five phases. The phases include preparation, BTP, business grouping, realization, final preparation, going live, and lastly, the after-implementation phase.

It's quite an expensive solution because multiple hardware resources are needed. A large investment must be made in hardware and software applications to use SAP S/4HANA. I would rate the pricing an eight out of ten. Small and medium businesses usually won't be able to afford SAP S/4HANA. I believe the standard licensing price remains fixed for the solution without additional costs. 

The implementation process of SAP S/4HANA needs to be well-planned in advance and all the required professionals need to be aligned. The expertise of the deployment professionals, consultants and deployment partner is a major factor in SAP S/4HANA deployment as the process often involves transformation from a legacy system to a top-tier solution. I would overall rate the solution an eight 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.

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 am a system integrator. We recently implemented it for a customer, and they are finding it easy to use.

We implemented the remote version of S/4HANA on Azure, and it is working well for the customer.

My customers use it for all functions, including finance, sales, and Oracle. 

They are using it for all six core functions: 

• Source to pay
• Record to report
• Order to cash
• Procure to pay
• Plan to produce
• Core finance. 

They also use it for other pharma operations.

The cloud-based feature of Microsoft Azure has been very valuable. It is easy to implement and use, saving the customer a lot of effort on infrastructure. The product is also very stable, and the customer is comfortable with it.

The customer has worked with previous products, and this one has brought a lot of comfort in terms of infrastructure handling. The infrastructure is managed by a different team, and the users are also comfortable with the interface. So far, they are happy with the product.

The product is user-friendly. The user interface, now called Fiori, is very stable. The product also has a lot of interfaces available to interact with cloud products, and it supports all kinds of integrations, so the amount of customizations needed from customers is greatly reduced.

The infrastructure resources are also effectively used. It is very optimized; used in a very optimized manner. The maintenance and handling of the infrastructure are very well taken care of with S/4HANA on Azure.

The interface could be improved with more Fiori applications. There are still a few applications in SAP GUI. I think SAP is working on this, but it will take time. 

Additionally, the admin interface could be improved. Since the admin is not directly an end-user, it may not be in focus, but if the customer's team is managing it, it would be helpful. 

Bringing all the admin applications into one place would be very helpful for customers to lock this down and use it internally for management.

In future releases, I would like to see a centralized admin interface. A lot of admin activities need to be done at different places. Apart from that, the pain development and change management for developments could be improved. 

Some features are not yet available in the new interface, so bringing those in would make it easier for customers to manage from the admin side.

I've been working with this solution for the last five to seven years. I work with the 2022 feature pack zero.

Since SAP brings new versions, I would rate the stability nine out of ten as of now.

So far, the performance is fine. No major hiccups or conversations have been reported that would cause the product to fall into any category of material issues. 

All stability and performance-related aspects have been taken care of. We have positive feedback from the customer side in terms of performance and stability.

I would rate the scalability an eight out of ten. Scalability is quite flexible. With the solution on Azure or other cloud products, scalability options are very flexible. The backend hardware technologies have improved on the cloud side, so many options are available now.

In my last five years of experience, all the customers I've seen are on S/4HANA. I've hardly seen anyone use older versions. New customers are all getting on S/4HANA.  

Our customers are mostly enterprise-level businesses. 

The technical support from SAP is quite mature. It's been five to seven years, so the product is now getting into the maturity phase. The product support team is quite capable of solving issues on time.

Positive

For me, the initial setup is very straightforward. It may not be easy for the customer, but for the integrator, it is.

So, I would rate my experience with the initial setup an eight out of ten, with ten being easy. 

There were some generic issues in development, but the support from SAP was good, and they were resolved. All products will have some issues. The product support is good enough to resolve them on time.

Deployment time:

Implementing it for all the functionalities within the given scope took around one year, including various phases like development, quality assurance, and production. It depends on the scope, but with the current scope, including all planned interfaces and project management, it will be manageable.

We (my company) are system integrators. 

Deployment process:

We start with development, where all customizations are performed. It's then moved to the testing system for various tests like regression, unit, user acceptance, performance, and integration testing. 

Once approved and verified by the customer, it's taken to production for deployment. Then, there's minimal functional and engineering testing, followed by live production testing done by the end users. If everything is clear, we go live.

Since customers are adopting it and finding it valuable, in comparison to others, I can give the pricing a five out of ten, with ten being expensive and one being cheap. It's not too expensive and not too cheap.

Additional costs to the licensing fees include maintenance or integration costs, depending on who manages it for the customer. Maintenance and support costs are general support costs for all products.

The product is mature and implemented in various industries. It's a very well-renowned and established product. They can go ahead and implement it. It depends on how they choose the integrator and the support for this product. 

The product is very stable, and finding integrators and support will not be difficult.

Overall, I would rate the solution an eight 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.

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.

Our organization is into the technology stack. Our customers are big companies from around the globe that all use SAP, either hosting it on public cloud, private cloud or on-premise. Personally, I have 22 years of experience. I deal with the operating systems, databases and the installation of the applications.

S/4HANA is an ERP package that runs on HANA database and LINUX operating systems. Most big companies are running their ERP on SAP. 

S/4HANA is an end-to-end solution. It seamlessly integrates with all the SAP Business Suite products such as IoT, AI, Analytics and all other SaaS solutions. The product is very robust and comprehensive.

Small businesses that have a small user base find this solution too expensive. I would like to see the price come down.

I have been working with SAP and ERP solutions for 22 years. The package is very mature.

S/4HANA is very stable. All of the big companies are running SAP, for example, British Airways, and UK Babcock are both using it. The solution is reliable. 

The solution is scalable. We have customers that have a 500 user system with 500 clients, and we have customers with 50,000 users and 50,000 clients. S/4HANA is absolutely scalable.

SAP's technical support is one of the best.

The initial setup is very straightforward. However, we required very specialized expertise to implement S/4HANA as it requires customization for the customer. It takes anywhere from six months to twenty-four months to implement, depending on the landscape of the customer.

SAP S/4HANA is affordable for big companies, but is very expensive for small companies. The implementation costs of SAP are substantial.

For large companies, this is a good solution. I understand that CIOs need to walk a tight rope between time to implement and the budget. SAP as a product requires, to a large extent, business process reengineering. It is important that anyone considering this solution understands the mapping of their business processes and how it will run in SAP. You also need to ensure you have all stakeholders buying into the process.

I have seen many companies buy the product thinking that they will implement it within five months only to discover that after five months, nothing has happened and the stakeholders are not aligned. Further, if you adapt the solution independent to your own needs, it will become difficult to maintain and manage. 

It is important to have a core team that understands SAP, and not only rely on an external consultant.

With the right project plan, execution, blueprint, and fully committed stakeholders, the solution will be successful.

I would rate this product a 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.