SAP S/4HANA Reviews

It has supported our client's digital transformation initiatives. There are two versions of S/4HANA: on-premise and on-cloud. We haven't seen many client use cases for the cloud version yet, mostly pilots and proof of concepts (POCs) on Azure. We sometimes convince clients to go for the cloud version for analytics purposes. 

However, 80-90% of the time, clients use the on-premise version. Clients run their entire enterprise on it, requiring customizations, which we help them with.

S/4HANA is an ERP system that connects to all other systems, even non-SAP ones. For example, S/4HANA talks with SuccessFactors, Salesforce, or Ariba. This integration allows it to serve as a single source of truth.

The finance module is the best thing. It integrates well with other modules, which makes it the best ERP available. This advantage comes from ECC, although new licenses are no longer being sold. Currently, S/4HANA is the one in use.

Views on real-time analytics in S/4 HANA:

It is a limited part. Real-time analytics is available to a certain extent, and the visualization is very good.

S/4HANA offers additional features like fuzzy search and duplicate detection. It even provides a percentage of how likely it is a duplicate based on defined parameters. These out-of-the-box features are helpful for users.

Customization capabilities: 

On-premise is completely customizable, but the cloud version has limitations. There are certain limitations of the cloud version for customization.

On-premise provides more flexibility. You can create custom code or change the entire process. For example, one of India based Oil & Gas major has built everything custom, even their configuration page is a custom SAP GUI. They have their own custom SPRO.

Similarly, every client needs some customization because:

• Terminology and processes differ slightly. You definitely need customizations for these two things. 
• Additionally, there might be extra requirements. Let's say you want someone to be notified when a purchase order is released. This also requires customization.

On-premise offers full flexibility for this, while cloud deployments have set limitations. These limitations are documented, and we have no choice but to comply. This can be a blocker for users who feel they have to accept what's offered, not what they need. This is a major concern for users considering the cloud version.

There are certain limitations of the cloud version for customization. The cloud version offers various deployment options. If it's managed by SAP, no changes are allowed. If the customer manages it, they can make some changes, but not drastically. There are limitations on the extent of these changes.

For the on-premise version, it's mostly there. However, there are certain things like the strict adherence to LOBs (Lines of Business). They don't always operate in isolation, and S/4HANA may not always be a perfect solution.

For example, material creation and vendor management are separate LOBs. But procuring materials happens from vendors, and those vendors also become entities in your system. Ideally, there should be a way to intermix these LOBs.

Currently, you have to use different T-codes for each, which makes sense, but there should be ways to integrate or cross-utilize them.

I have been using SAP S/4HANA since its inception; I have worked with almost all versions except the latest one released in 2023. 

It is quite stable, with no concerns. It offers flexibility and robust reporting out of the box.

On-premise scaling is excellent, but cloud scaling is intentionally restricted. If the same solution is accessed with different tenants, they can't change SPRO, and you're also expected to use SPRO. That's the model. 

However, the on-premise version is highly scalable, as demonstrated by India based Oil & Gas major, who has changed almost everything. This shows that it's scalable down to the code level, if needed.

For S/4HANA, I'd rate it an eight, slightly higher than the seven for ECC.

There are no close competitors to S/4HANA. Other ERPs exist, but they aren't at the same level. They are often considered "poor man's ERPs." So, no other tools currently compete with SAP S/4HANA.

Deployment refers to the cloud, while installation refers to on-premise. Both are straightforward, with numerous documents available and a supportive team that provides quick assistance when needed (if at all we need the support). It's easy.

For maintenance, there are two answers: on-premise is easy to maintain, while cloud is tough.

Cloud maintenance difficulties:

Even with managed services, even to make allowed changes involves SLAs (Service Level Agreements). Moving a transport, containing all changes, even a single comma, can take three days. It never happens within an hour. You have to wait one to two days to see changes reflected in your system. This is a major drawback, especially since moving a transport could be automated, considering SAP's flexibility.

SAP's licensing and pricing model is quite flexible. They offer both a floating license model and an agent model, focusing more on the latter. It depends on the number of licenses and users.

In some cases, they also offer seat-based pricing. For example, 50 seats can be used by either Kumar or Michael, or one seat can be shared by Kumar and Michael across shifts. They have a flexible model and the price is also flexible.

For instance, if it's 10 or 20 licenses, there might be a lump sum, but for 100 licenses, they offer a better price. They are flexible in that sense.

Overall, I would rate the solution a nine out of ten. S/4HANA could gain a larger market share if they extend their SAP model pricing to smaller companies. Currently,  S/4HANA focuses on an agent-based model for larger companies. If they were willing to offer an SAP model, they could secure more deals.

Smaller companies often have a rotating workforce, so allowing the same license to be used by different people at the same desk would be more appealing. This flexibility could attract more users to opt for S/4HANA.

The tool has improved our company's financial processes as it gives us a systematic way to look at data. Based on the analytics offered by the tool, users can judge if they want to spend money on something or not. Based on data or analytical data from ERP, you can easily make judgments, like whether you want to purchase something commercially or not. With the tool, we can see the transactions and everything in one place.

SAP offers very good ERP software. As ECC is into SAP HANA, SAP has already improved it, and now SAP is in the process of going with RISE with SAP. Everything has already been captured in the tool, and everything is as per the worldwide industry standard process, and the ERP solution is something that is based on it.

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

I have experience with SAP S/4HANA.

It is a stable solution. Stability-wise, I rate the solution a ten out of ten.

It is a scalable solution.

Around 200 to 500 people use the tool.

If you divide the workload between the projects and clients, then it can definitely be very costly. If your organization is not more than 10,00,00,00,000, I would say it is not okay to go with SAP S4/HANA.

For technical support, we are dependent on the consultants only.

I cannot say whether the product's deployment process is complex or straightforward, as it depends on the company where it is being deployed.

The solution is deployed on the cloud.

A minimum of ten to fifteen people are needed to deploy and maintain the tool.

The solution can be deployed in five to six months.

A company's resources can't deploy the tool. You need specific people to deploy the tool. It's not a person but a team you require to deploy the tool. Consultants are needed to help one deploy the tool.

The ROI part cannot be judged, and it is something that is based on how much a person uses the tool. If your company is small, but when it comes to process orientation, the ROI is always good. ROI is not dependent upon the size of a company.

The tool is expensive.

SAP S/4HANA is a very decent product for our main business. My company is into mining and production. The tool is a process-oriented product. If you train people, then the product is very likely to be used, and it is defined as a tool that offers a systematic industry standard process.

Speaking of whether the tool has significantly increased our company's operational efficiency, I would say that it would be an injustice in areas like manufacturing, material movement, HR, production planning or quality assurance since each and every part is connected with each other.

The real-time analytics capability impacts our decision-making process and can be very quick if you have the right data. With just a few clicks, you can get everything.

The tool's Fiori UX has improved user suggestions, productivity, processes, and real-time data in our company.

I recommend the product to those companies that have a capital of 10,00,00,00,000.

SAP S/4HANA is a good product, provided it is used in a proper and realistic manner. Training is also required for the tool's users. You may go for SAP S/4HANA, but you need to decide if, as per your company's costs, you don't mind spending too much money or if you are capable of spending some money. You can take any ERP solution since there are many solutions available nowadays. SAP is very expensive, I feel.

To those who want to buy the product, I would say that they need to prepare a plan and should ensure that they have the right people to deploy the tool and create a strategic planning process, after which the process of choosing the right consultants should be carried out. The right consultants are the people who feed with the fact that the deployment processes carried out are done for life long. It is not possible to stop anything midway.

I rate the tool 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.

It has been used across various verticals, including billing, sales, business, and pharmaceuticals. It has been implemented in different business verticals.

Apart from the core business processes, the performance has been drastically improved. The speed of executing reports has increased significantly. We no longer need day-minus-one business processing.

In the past, we had to extract, transform, and load data (ETL cycle), and only then would we get critical dashboards and reports the next day. Now, it's available in real-time data, within the same instance, on a single click. This is a major improvement.

Everything is available in S/4HANA. It's really good. There might be some restrictions in the public cloud, but in the private cloud, anything you can think of can be made available. That is the best part of S/4HANA.

S/4HANA stands for high-performance analytic appliance. 90% of activity is done on the hardware side, as it supports fast memory executions.

Initially, it was SAP ECC 6.0, but then they introduced faster execution processes and best practices for different verticals. It gives an advantage on top of what is being used across different businesses. They have introduced best processes altogether.

The implementation time has also been reduced drastically. We start by showing the customer the best practices and configurations. This is a major difference from before when we used to understand their "as-is" process and then design the "to-be" process.

Now, we get acceptance on the best practices early on and only do customizations where necessary. Most customers prefer this approach because they are changing their business to match best practices rather than us changing the software to match their business.

Additionally, there are public and private editions of the product. The private cloud is owned by the customer, giving them full control over customizations. The public cloud is controlled by SAP, which offers only best practices that customers accept, knowing they align with industry standards.

One disadvantage is the introduction of multiple products. In older versions, everything was in a single package. Now, we need separate licenses for different functionalities: S/4HANA Cloud for human capital management, SuccessFactors for talent management, and Ariba for procurement. For advanced components, we need S/4HANA for enterprise portfolio and project management. 

Additionally, if we purchase SuccessFactors, we also need to add integration tools like SAP Cloud Platform Integration. So, it's like buying a basic bundle (starting from 65 or 25 FPUs) and then adding more components and integrations later, each with its own license fees. Essentially, they have changed the model to introduce multiple products with new license fees.

Everything is available and works well in S/4HANA. There might be some restrictions in the public cloud, but in the private cloud, you can make anything available.  

I am a consultant; we don't use it in-house. We work with SAP. It has been almost nine to ten years since we started with S/4HANA side.

The private cloud is 100% stable. The public cloud still needs some time; it's 90% stable, but 10% still needs enhancement.

Private cloud is ten out of ten, and public cloud is nine out of ten.

It is a very scalable solution. 

The customer service and support are good. 

Positive

S/4HANA deployment is easier than previous versions.

Deployment time:

The deployment time depends on the complexity of the business. 

For a public cloud implementation with standard business processes, it takes three to four months, with the fifth month for support. 

For a private cloud implementation, it may take five months or more, depending on the customizations and configurations needed. The number of consultants and the complexity of the business processes are the most important factors.

Moreover, the maintenance is easier now.

Integration into existing infrastructure: 

 There are multiple options for integration depending on the products. For SuccessFactors, you can either use SAP Cloud Platform Integration (CPI) or the SuccessFactors Integration Suite. 

In the Middle East, where I work, there's a government-mandated e-invoicing system that requires integration with S/4HANA. 

Like Ariba, that also needs to be integrated. In this version, integration options have been expanded. Previously, it was only SAP Process Orchestration (PO) that handled integration, but now there are more options available.

For a private cloud implementation, a team of eight or nine people: six consultants for the core modules, one basis consultant, one technical consultant, and one project manager. 

For a public cloud implementation, the number of consultants is reduced to six.

ROI has multiple aspects. In the initial days with ECC, costly hardware with depreciation cycles was necessary. Moving to the cloud reduces those expenses. Within three to five years, ROI is very good. 

Additionally, the need for data centers, DR sites, and skilled maintenance teams is eliminated, drastically reducing costs within five years compared to SAP ECC.

It's expensive when opting for a private cloud but cheaper on a public cloud.

For private clouds, the price could have room for improvement. It is a bit on the higher end. 

The license is subscription-based. The users can lock in licenses for three, five, or even seven years. The agreed-upon pricing on day one applies yearly for the chosen duration. This is available for all SAP products.

Clients don't have to pay extra for support, maintenance, or other things. So, the subscription includes everything.

For S/4HANA, my recommendation is that finance is very strong. They have improved. SD (Sales and Distribution) in finance has been strong since day one, but now they have also improved the purchase cycle significantly. They have introduced multiple products like IBP (Integrated Business Planning), which has improved their planning for production and the entire manufacturing process. 

Considering this, I would recommend S/4HANA Private Cloud as of now. SAP is working very hard on S/4HANA Public Cloud as well, so in one or two years, the public cloud might be the best option.

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

All our warehouses are manufactured. We are using it quite extensively. We are on a program that we are doing within the company.

I find the easy transformation and the good app to be very valuable. The computing capabilities are nice, and the analytics are good. The insights given help us make strategic decisions. 

It's been more than three or four years that HANA has started to enable us and has helped make our system more efficient, faster than the traditional ECC that we had, exceeding Cisco.

We are already in touch with SAP, excluding them as inputs. 

I have used the solution for more than three or four years.

SAP has been handling stability. We are doing an upgrade as well.

Scalability is somewhat of an issue.

Technical support is good.

We have used many different solutions.

It is efficient and has been a transformational journey. It's a long journey and a mindset change. 

I would rate the overall product as eight out of ten.

Nowadays, I have been implementing SAP S/4HANA and I have managed areas like analysis and blue print. I have lately started off with the configuration of the system. I have made some SAP Fiori training programs for people with a few reports, but I must say that I am not a reporting specialist.

It is expensive to implement SAP in companies, making it an area of concern where improvements are required.

I have worked with SAP S/4HANA for a year, but with SAP, I have eleven years of eleven years.

Only big companies use the tool.

I will be using SAP Signavio and SAP Process Manager soon, but I don't have experience with them since my company will be starting to use the product today.

The product's initial setup phase is almost the same as the previous ERP system my company had. I don't see a lot of changes in the configuration, especially from my point of view after I look at all the modules. I see that there are a lot of changes in the modules offered by SAP S/4HANA, especially when compared to SAP ECC.

As per the plan for the project where I work, I had to deploy the span of two years for four companies, but it had to be postponed to three years. I don't know about the background and finances associated with the product. I think it takes a very long time to deploy the product. I don't see any technical problems with the solution. I believe that the long time the product is in use is because of the finances attached to the product.

Each company using SAP S/4HANA can save some money because everything can be done in one system. If a company already has an old ERP system and wants to implement a new one, I don't think it will be able to save some money because it will have to spend a few million Euros to implement the new system. If it is a green field, then such a company can implement its first SAP tool and save 100 percent of money since everything can be done in just one system. Companies can have different systems for finances, production, and logistics, and everything needs to be connected, which is a very difficult process. With SAP S/4HANA, you can have everything under a single roof, you can see the connections across all departments, and you can find everything in my system. You can create one report, and you have got everything from all departments, including the life cycle of all the products that can be seen in one system, so it is helpful.

Everyone says that it is expensive to implement SAP in companies. I have heard others saying that SAP is only for big companies that have money. If you want to sell your company and you say that you have got SAP in your company, the price can be quoted high. It is exclusive to have SAP in your company. It is the best system in the world.

I use the solution in my company, and I feel SAP Fiori is very nice since it is modern. There are better functions in SAP systems and the configuration, but not in SAP Fiori. In SAP Fiori, everything looks better, but it is not user-friendly for me because you are not able to find a lot of things in it. You have to scroll a lot and it is not better, but some users say that it is a good tool since the reporting is much better in SAP Fiori. I feel SAP S/4HANA is better than SAP Fiori.

The data processing speed is the area in SAP S/4HANA that has the most improvement in comparison with the old SAP system because it now works in a different type of database, which is very fast.

I rate the solution a ten out of ten.

SAP S/4HANA is the predominant solution from SAP, replacing the earlier SAP ECC. It's widely used for overall enterprise resource planning, including running banking operations and other enterprise functions.

My client's organization uses SAP S/4HANA for real-time analytics and decision-making by leveraging embedded analytics that are part of S/4HANA. Some organizations integrate specialized BW layers or their own data house layers for analytics, using SCC or BI for visualization. Others extract data from SAP S/4HANA to other hyperscalers or providers to create visualizations.

SAP S/4HANA supports my client's business processes in finance, procurement, and supply chain management through end-to-end management. This is often done with other IT specialists or independently for smaller customers using SAP S/4HANA.

SAP S/4HANA has been an excellent integrated solution for my clients, technically much easier to manage than the ECC solution. The embedded AI layer helps adopt intelligent AI directly within business scenarios, which has been very beneficial. These features enhance operations and efficiency for my clients.

Extensions to SAP S/4HANA have room for improvement, especially in integration with low-code/no-code platforms. Creating these extensions through Fiori transactions is more tedious than customers would like. Although the SAP build process has become more linear, further improvements could provide a huge benefit.

I have been using SAP S/4HANA since 2013.

It's a very stable system overall, but with new attacks targeting customers' SAP landscapes, the latest patches and versions must be applied. I would rate the stability an eight. 

The scalability of SAP S/4HANA is high, around nine. Typically, my clients are medium or enterprise businesses.

They are not excellent, but they are not bad either.

Positive

I would rate the initial setup of SAP S/4HANA as one because it is challenging. Implementing SAP S/4HANA involves integrating an organisation's processes, including different departments, geographical locations, and compliance requirements. Given the scale of these businesses, such as operations in multiple countries, it's complex and not meant to be simple.The physical deployment of SAP S/4HANA is not a challenge.

The deployment itself might happen within a day or even a few hours, given the accessible hardware. The time-consuming part is identifying the needed components, areas, services, and software. The actual deployment process is simple, but adjusting the software to meet your needs is complex. It's not the physical deployment of the application that is the problem.

SAP S/4HANA is usually deployed on the cloud through its own SAP
mechanism. This allows for deployment on both public and private cloud options.

Regarding pricing, I don't regularly deal with the financial aspects, but it is not a cheap solution.

When migrating to SAP S/4HANA, productivity initially dipped as organizations adjusted to the previous system. This is due to the need for change management and adapting to the new software. However, once the transition is complete, productivity significantly improves due to faster response times, a more mobile-centric approach, and better data handling. Overall, SAP S/4HANA helps users perform their tasks more efficiently.

SAP S/4HANA might not be able to address all business challenges directly, but other products can be integrated to fill these gaps. For example, difficulties like sustainability or energy rating do not have a direct solution within SAP S/4HANA. Similarly, areas like contact centre or customer call centre management are not directly part of SAP S/4HANA, but partner solutions are available to address these needs. 

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

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. 

Most of our customers have their applications hosted on SAP. Therefore, they have stored the data on SAP S/4HANA database.

SAP S/4HANA is the preferred database because of its scalability, faster accessibility, compatibility, and other well-suited features for large data sets.

The product’s pricing could be improved. It needs a high CPU and memory to analyze and compute that data. Thus, it should be natively supported from the cloud platform. We should get the bundled image so installation and configurations are not done manually. All those should come as a bundle learning package. A virtual machine could exist to make everything available on a single deployment. That will save some time for any project timelines.

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

The product is stable.

SAP S/4HANA is scalable. We have enterprise-level clients.

The initial setup is fine since we have good documentation for reference. The deployment requires four hours to complete.

The product is not that cheap, not that expensive. It is costly in computing because these VMs have a huge CPU and utilization. We have a monthly billing, and there are extra costs for the license.

As for the interface, it always depends on the individual. However, there are some recommendations. Ultimately, it is up to the developer to decide how to implement the interface in the back end.

SAP S/4HANA is a good product, but anyone who plans to use it for their application should have the core skills required. It is not something that ordinary people can do, as it requires some expertise. When hosting it on the cloud, such as Azure, Amazon, or Google, it is important to take care of security policies, government regulations, and disaster recovery strategies. You need to plan your design and architecture accordingly.

Overall, I rate it a nine out of ten.

We use the solution to import master data. We use classic resolution to collect local US company material masters and align HQ material masters' numbers. We import FI/CO/MM/PP/SD IMG and opening posting accounts and stock. 

We use it to import transactional data. We collect purchase orders and sales orders into S4H 

We also use it to import security. We collect user roles and permission objects.

We provide training requirements for logistic modules for sales orders to intercompany purchase orders and make production orders for goods issued and goods received. Finally, we run production order confirmations for cost variants. 

We removed gaps for MRP planning, forecast data, and PIR purchase orders. We integrated overall sales commission collections and sales profits management. 

It's helped with business aspects and improved material planning and RMA processes.

It's helped with service aspects and improved customer service and spare parts management.

It's good for HQ FICO aspects. We consolidated P/L statements, cash flows, and income statements.

For supply chain aspects, we integrated the last puzzle piece for material control.

We found the solution integrated with HQ and local material number for batch orders to split several partial orders. 

For customer service and RMA views, material alignment or aggregate is evolving. The US can assign sales forecasts to distribute Asia-built finished parts. This business model can accumulate mass stocks for replacing parts and labor maintenance services. If sales order to shipment can align with the ERP platform, the materials to order can support visibility across Asia/the US/the EU. The integration not only speeds up order processes but also controls solid stocks and costs.

During parallel preparation of go-live processes, SAP B1 and S4H transactional data alignment can be difficult to track. The approach is to have the same sales order amount and quantity to compare the correctness so both sides are matched, according to FI concerns. For project purposes, we need to figure out if there is any solution or approach when considering data migration for sales orders and purchase order imports. THe validation is also the key to review bothe side data of correctness.  Any resolution for an add-on program to validate reports can be useful. 

I spent six months in a S4H project implementation, including SAP business - one migrated into an S4H 1809.

.

.

.

Positive

.

.

.

.

.

.

.