A lot of people would say the pricing. SAP is seen as quite expensive even now. It doesn't work for smaller or medium optimizations. 

The licensing and pricing could be looked at. In Brownfield migration, the trade-off between greenfield and brownfield means you either keep it clean or match the business requirements. Sometimes, it's not possible to do both. 

While ValixAPI provides significant support in making those decisions and the SAP consultant is very useful, we are still dependent on past history and how it was originally set up. I wouldn't call that a real disadvantage, yet more accessible consulting would be beneficial. 

Incorporating all other cloud products, like APO or IPP, into the S/4 house might also help.

The user experience could improve. In recent years, SAP has acquired different third-party applications and integrated them into SAP S/4HANA, which was a good opportunity for users. However, as a consultant and super user, I believe SAP S/4HANA is a good tool, but the user experience takes time to learn. They have tried to improve this, but I think it can be made more user-friendly for users than it is today.

SAP S/4HANA has room for improvement because we are still exploring functionality, and while most modules are implemented or supported by the partner, we are still in the process of exploring. Right now, everything we require is already in the SAP SAC module.

In the traditional ECC Oracle systems, when the size is enhanced, it doesn't impact much on the cost, but for SAP S/4HANA, the sizing needs to be checked very frequently as the data grows every year.

The TCO impact is quite high for SAP S/4HANA; for instance, if today I am using a 64GB CPU and 512GB server, in another year, I will probably need to upscale to a 1 TB machine. SAP S/4HANA needs to bring a feature that allows a great quantity of data compression. 

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. 

With the public cloud, now everything is being pushed into BTP. This has created challenges, as it requires us to redo our coding and development. This presents a significant learning curve for our technical team and impacts overall deployment strategy. 

We need about six months to get accustomed to it before offering it to our customers. Establishing the right channels was also a challenge, as BTP was quite new. Even the SAP team was uncertain about the costs for different users. Communicating this to customers was difficult, especially considering they'll need multiple licenses. In terms of costs, it has been reviewed a couple of times, but it remains a challenge. 

Initially, BTP was new for everyone, including our SAP contacts. Now, with outside consultants, we have received help. SAP has released some courses, but we still have a long way to go. We use two products: SAP Business One and its support. Working in a different industry, understanding our specific use case requires effort. Feedback on bugs or issues sometimes takes time, indicating scope for improvement.

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

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.

We are consulting in Turkey, where there are a lot of regulations in finance that should be implemented in S/4HANA. SAP has packages in countries like Poland, Spain, and Italy for these regulations, such as e-invoicing. However, we are missing these standard packages here in Turkey. 

Every customer has to build their own solutions for regulatory needs, such as sending invoices to the authority. This should normally be included in S/4HANA.

SAP invests a lot of money in R&D. Every three months, I receive a patch, which is an upgrade within the SAP systems. SAP is good, however, SAP users should have the knowledge to tackle SAP effectively. I recommend training from a systematic approach.

There are areas for improvement. SAP needs to consider both global and regional requirements. For example, India has unique tax implications and regulations. They shouldn't have to rely on extensive customization for basic things because the standard features don't align with India's needs. 

More standardized features tailored to India or Indian customers and partners would be helpful, especially concerning tax regulations.

For example, India has different income tax rules [GST], but many things are not standardized in SAP. SAP broadly focuses on the global requirements of the top ten countries and may not prioritize India's specific rules and regulations. If they consider these and include them as standard features, it would be easier for customers in India to implement SAP quickly.

So SAP should consider tax parameters for India.

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.

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. 

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.

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.

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.

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. 

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 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.

It could be improved by focusing on user-related challenges, as end users might face certain difficulties.

SAP S/4HANA is an expensive solution.

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. 

The disadvantages of this product include the lack of integration with platforms like LinkedIn. 

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

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

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

There are products equivalent to SAP S/4HANA available in the cloud, but simplification is a part that I feel is very important. The product needs to be simplified. SAP S/4HANA is like a monster, while Salesforce is easy to implement and is like a SaaS product. SAP comes in a SaaS model with S/4HANA cloud.

Consultants need to always remain updated with the latest technology and features from SAP S/4HANA. The licensing of SAP S/4HANA needs to be improved. 

The solution users of a company should focus on the data warehouse or data retention management; otherwise, SAP S/4HANA can incur huge costs.

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.

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

S/4HANA is like a ready-made suit, but it could be improved by adding more customization options, such as different colors and attractive themes in Fiori. From a functionality standpoint, there's always a workaround solution, and we've been working on SAP for the last 18 years.

I expect more functionalities related to cloud applications and integrations with third-party applications in the next release. Given the complex architecture and data storage in the SAP database, simpler plug-and-play integration methods would be beneficial. While SAP S/4HANA currently ranks second in cloud comparison integration models, easier integration methods would be a valuable improvement.

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.  

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

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

The platform could improve by simplifying the analytics processes, which currently require significant preparatory work outside the platform. This aspect can be cumbersome and detract from the otherwise streamlined experience.

I would like to see the inclusion of more integrated tools that allow for direct analytics and calculations within the platform itself. This would reduce the need for extensive data preprocessing, which is currently a necessity.

I think that the cost is a big area of concern, considering what users get out of the tool. I believe there are some tools and even some cloud-based kind of data modeling tools, which once you start putting applications to the cloud and sharing search services in databases, I think that can kind of buy you what SAP used to put together years ago to sell, and it can be helpful for the power of what you are trying to do with it. In our company, I don't think we are building models constantly, like the real-time decision-making AI models right now with the current tool. In our company, I don't think we will ever be able to get to the aforementioned point with the use of the tool.

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 think the user interface still needs improvement. While efforts are being made to enhance and make it more user-friendly, there are still shortcomings. Fiori is a great step forward, but work must be done. So, I believe SAP S/4HANA should focus more on improving GUI access. We also had a difficult time migrating the fixed assets. 

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.

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.

More integration is necessary. Some struggles remain, especially regarding SAP's integration with other SAP modules. For example, integration between S/4HANA and Business for Logistics needs improvement. These issues exist within the integration space and present challenges during implementation.

The initial setup was difficult.

SAP S/4HANA is a robust front-end solution compared to other web technologies available. However, screen design in SAP EFI might not be as extensive.

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.

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.

It would be beneficial if the pricing structure could be made more flexible and adaptable to suit the needs of different organizations. Besides this, the scalability also needs improvement.

I believe support could be improved by providing more specific and detailed answers rather than generic responses.

Oracle has its own data center, hardware, virtualization layer, and database. They offer a complete solution, which SAP currently can't match. This is a weak point in SAP's proposition.

The tool could improve development, particularly during upgrades or conversions from ERP systems to the solution. Adapting the code to the new standards can be challenging, especially when customers try to keep their old ERP developments.

The ERP market is competitive, and other solutions may have advantages over S/4HANA in some industries. I work in fintech, and central finance is essential to all industries. S/4HANA provides all the features there, but when you talk about ranking the industries, manufacturing would be No. 1.

Initially, S/4HANA was getting bested by PeopleSoft in the HR sector. Now, they are catching up. In particular, SAP wasn't strong in expense management, but they acquired a company last year and Ariba several years back. Their SRM was not hit. 

I would like to see improvements in the graphical user interface and core modules in SAP S/4HANA. Even after 20 years, there haven't been developments in these areas. The purchase order, sales order, and core modules like CRM have remained unchanged. The financial data and modules have also stayed the same. Fiori is available but hasn't brought many changes to the core modules.

I'd like to see more features in the core ERP module to make it affordable and manageable for small and medium-sized companies. Big companies can handle additional modules like CRM, but smaller businesses struggle to afford and maintain these.

The solution's implementation cost is high.

The product should improve its cost. 

We don't face any problems with the modules, but we have a problem with the web solution. The web access sometimes has difficulties with logging in.

The support should be improved. Every time we submit tickets to SAP, the process takes a long time.

Also, improved performance, reliability, and stability would be beneficial.

The user interface should be much more convenient and user-friendly. 

In future releases, there could be more use of AI.

The solution is complex technically because both an old and a new path exist. Some more development work is needed for Fiori before a complete switchover can happen. Right now, they are enhancing and developing Fiori. In two to five years, things may change because Fiori will be finished and in the market. 

There's lots of improvement to be made on the user experience level and digital work. Since SAP is a transactional software, you can't use it like Salesforce. It's not easy to create automated reports.

For the user experience, they can try to get out of the strictly industrial point of view because it's an IT solution. It's not always the most fun application the use. It's pretty complicated and if you're not fully trained for it, it isn't easy to understand how it works.

It would be very good to merge the SuccessFactors or other solutions with S/4HANA to make it one suite. They could have a single dashboard for all types of products. I have many embedded solutions. 

The solution’s pricing could be reduced and made more cost effective.

The solution’s pricing could be reduced.

Items that impact the TCO should be improved because the solution is very complex to integrate and keep running. 

Integration with a portal or front end is needed. For example, the online collaboration part of SAP with vendors lacks functionality. Integrating with sales or service processes with a CRM or cloud for customers uses three different SAP systems. Customers typically choose Salesforce instead because the SAP system is not good.

There is a very large learning curve for different domains from an end user perspective. Some things are easy to understand and other things are complex. Users receive cryptic error messages when they do things that they do not fully understand. 

SAP offers a lot of products now and all the capabilities are available from one service provider. However, the knowledge needed for the implementation of these capabilities isn't widely shared and so product knowledge in the market isn't comprehensive. This makes it challenging to fully take advantage of all the capabilities. We would like to have access to tutorials. 

The integration could be made a little simpler in terms of design and implementation. SAP should integrate easier with other third party systems. Industry specific retail or FMCG related industries can't directly rely on SAP with respect to the POS integration or the eCommerce integration. 

The migration to SAP S/4HANA is hard.

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

SAP S4HANA could improve by having a more seamless easier integration, faster integration. The overall implementation timelines can be reduced by leveraging Agile methodology

There could be a bit more competitiveness in their licensing and pricing.

I think anything related to manufacturing public clouds could be improved.

We found that the implementing partners themselves are struggling with S4HANA's features. It's not an exact translation of the older ECC, so SAP has taken a new route to do things with S4HANA. Maybe it's a good product, but the implementing partners also like to have an in-depth understanding of the full feature set the product offers. There are areas where even the implementer has to go back to set, which takes time, so that's one of our major concerns.

The older implementations were cloud-based, but one is happening now in one of the larger utilities, which sells services to around 4 million consumers. That's an ongoing project that hasn't gone live yet. This will be the real test. In a year, we'll know, and we can give more feedback.

Another complaint I have is that the screen source is disjointed. When I say this, I'm speaking from a user experience perspective. I don't know the S4HANA database, so I can't say if it's good or bad. I am sure that S4HANA would have certain limitations compared to Oracle, which is the gold standard for databases. Maybe there are some challenges in the backend, but I don't dwell on those because I'm not a technician. But the graphical interface requires improvement, and its flow should be very smooth. 

Also, the Fiori app is very basic. They need to become richer because people tend to use Fiori to access the S4HANA application to save on license costs. Fiori gives you access because it's a web client, and they market it as an app. It's not really a full-fledged app, but the roadmap has to be cleared from SAP. And when its capabilities improve, it gives a native app experience when people use Fiori.

SAP S4HANA is not suitable for all-size companies. If you have a small company there are better fit solutions for your needs.

Thi solution can improve the Bill of Materials (BOM) and production planning.

In an upcoming release, the Product Lifecycle Management (PLM) in SAP is very simple, and SAP should extend PLM in the ERP system. Additionally, SAP S4HANA should add more advanced features for monitoring in the database, such as in the Oracle solution.

The initial setup could be simplified. It needs improvement.

I would like to see the AI included to help from a data standpoint.

The solution’s stability could be improved.

Nothing was noticed, but maybe SAP Support Systems for system bug issues should be added. :) 

The support and price of the solution need to be improved. The solution should incorporate some new innovations.

The scalability could be better.

The Capex and Opex could be improved. It would be nice if they cut back on the cost. Otherwise, it's a very good product.

The migration form previous versions to SAP S/4HANA is a challenge both for customers and clients. 

there should be simpler ways to incorporate the new tools into a process framework. Many customers are still using the same tools but running in SAP S/4HANA

The solution could have a better user experience. However, they are working a lot on the user experience and they have come up with various applications, such as mobile applications. This was lacking over the last two years.

If I can highlight one point that could be improved, when we talk about other ERPs, like Oracle, nowadays these ERPs provide free integration with other ERPs. For example, there is an API for banks integrated into every tool and every product form requires that bank integration in order to give real time data into the ERP. But SAP is charging a lot for that particular bank integration scenario and I think it should be free because other ERPs are providing this feature built in to the ERP. People always ask us about the integration and how much it will cost to go with that solution, so people are thinking about this.

The procure-to-pay solution in the Contract Management angle could be better. If you look at it on Ariba, the Contract Management Life Cycle for Ariba is more robust. You can create documentation, SLAs, and NDAs. Apart from the procurement aspect of the contract, you have the legal side, but Ariba cannot do that.

From what I've seen, the features of the procure-to-pay model in S/4HANA and their Contract Life Cycle Management side primarily focus on the procurement side. I believe it would be good if this solution could handle a part of the legal side.

They will incorporate Extended Warehouse Management and Transportation Management into the S/4HANA cloud. Most big companies that use a solution like S/4HANA have a legal department within the organization. Suppose they can incorporate that to be in S/4HANA suites; I think it'll be good. It will be just like what we have with Transportation Management and Extended Warehouse Management.

The user interface could be better. They have too much information on the interface, and our customers still keep complaining that it looks complex. Even though many things have changed, they still complain that the interface or the screen they see is a bit complex. It's only when they see the Fiori interface that their mind becomes a bit calm.

The solution could improve by making customization easier. The on-premise version is a lot more flexible.

It should have more support. Documentation and support for mobile apps can be improved.

It's been just one year that we started using this product, due to the fact that we need to have different integrations as well to other systems. With S/4HANA, when SAP started, everything worked in a single SAP system. Slowly then it's been delegated or divided into multiple SAP systems. That's why we have around 25 different SAP products running in our landscape. Yet, at the same time, S/4HANA is the core. It's the core component.

Going forward, I believe more systems could be consolidated into S/4HANA. We need to reduce the number of SAP systems running in our landscape. S/4HANA has the capacity to host many other SAP products, therefore we can discontinue some of the SAP products. Currently, we have now the Global Services, the Governance, Risk, and Compliance, and Enterprise Portal, BW, Supply Chain Management, Warehouse Management, et cetera. If SAP could consolidate many of the systems so that we can reduce the number of systems, that would be ideal.

The solution can be a bit expensive.

We would like to see more DevOps capabilities in the future.

The solution would benefit from offering more serverless features in the sense that when you deploy SAP, it's a pretty big deployment and you have a lot of dependencies or you are closely tied up or you have a dependency with the hardware vendor and the hardware providers and the certified hardware and items like that. At the same time, all these deployed components and these files are possible to deploy without a server as well. Slowly SAP is providing some of the features so that you can deploy this in containers and so you don't have any dependency on the running hardware. That way, you can restart the systems without any downtime or the end-users will not feel the difference. Aspects like that need to be improved. 

We do have here monthly maintenance due to the fact that sometimes we need to recharge the system and we have seen from the end-users there will be certain downtime as well. If there is no dependency with the hardware and if it goes serverless, then we can have zero-downtime maintenance.

SAP improves the tool every quarter. I received a certification for cloud products from SAP. My company is also trying to improve the tool's knowledge base. The tool needs to improve its interface and functionalities.

The tool should be more well-integrated or inclined towards AI or AI developments like chatbots or ChatGPT.

The product could be improved in several key areas, particularly in API granularity and ease of configuration. It is typical for new technology to initially lack the full functionality of older systems, as seen in every development cycle. In the Business Technology Platform (BTP) context, certain granular configurations available in S/4HANA, such as output determination, are not as easily replicable through current APIs. Previously, configuring outputs for delivery at a detailed level was straightforward. For example, one could easily specify output settings for regular deliveries. However, replicating this process in an API-driven workflow is currently more complex and less intuitive for business users. Additionally, there is no simple way in the new technology to verify if an output was successfully created and sent to a partner.

Considering it's not a small product, improving pricing would be helpful.

So, there is room for improvement in pricing. HANA is not a simple product; it's quite complex by design.

The solution is quite expensive.

SAP S/4HANA could improve by making the interface easier to use.

I cannot recall coming across any areas that were lacking. 

Starting out on the solution can be a bit complex and difficult. I'd like to see them simplify the process of integration. It's very complex, even with the new solutions within SAP.

If S4HANA has more AI and machine learning, it will be better and easier for reporting and dashboarding.

Its pricing could be better.

This product would be improved by adding more reports. In the next release, I would like UDF or UDO to be added.

In an upcoming release of SAP S4HANA, chain management should be easier.

These days, most clients ask about mass upload. It's not possible to do that with SAP so there is an opportunity for them. Mass uploads have become a necessity for industry. SAP does have ways to do this but it's not user-friendly. I'd also like to have an easier option for hosting. Currently, I know that S4HANA can be ported on cloud versions, and they have started giving out ready-to-use kits but there are some hiccups and basic things are a struggle. I've worked with a few different teams that have had problems with that.

I'm not a big fan of SAP S/4HANA because it needs a lot of hardware. It is really fast, but it needs a lot of hardware. The hardware for S/4HANA is too expensive.

S/4HANA could be improved with better integration. At the moment, a main issue I see is that there's so much growth in the functionality, complementary modules, and cloud solutions which were acquired by SAP and which extend the functionality of the SAP ERP suite. It looks to me that they tend to acquire more and more functionality from acquisitions, but they don't invest enough effort into making them integrated with S/4HANA or ERP. I would say that the functionality is great, but integration is something which still needs more attention. Instead of focusing on acquisitions, they should invest, integrate, and better the existing portfolio of products in SAP. It would help us, as implementors, to have a more complex or compact solution. 

In a feature release, they could improve by adding budgetary features.

Maybe its user interface and reporting can be improved across the board, but it is manageable.

The solution could be more user-friendly for regular users and developers.

The documentation for this solution can definitely be improved and I'd also like to see more support, more numbers of Android or iPhone apps.

The initial setup could be better. They can make the process a little easier. The functions that we require will be available in the next release. We specifically need a new model, and I think we have some versions to implement. I already read on the SAP website that some functionalities we are waiting for are available in this new version.

From our point of view, we are just a technology consultant. We look at the interfaces in terms of the functional modules we have. It's hard to really see what would be missing in terms of a feature. 

For clients, the most painful part of the solution is the implementation guides of the business or process applications. Okay. The business scenario, the graphic user interface, shown on the system can be a challenge. 

Maybe the commercial model for some other products developed for HANA could be adjusted to make it less complex and more affordable. The commercial laws that SAP has it's very complex. The customer has to acquire a very high license on the product and then they have to buy infrastructure on top of that.

Technical support has been declining. They aren't as responsive as they used to be.

The product could use some other integrations with leaders of the products with public clouds - especially if they are doing with another staff like ILP or on other applications. There could be more legal applications that could be integrated more easily with SAP than they're doing. Right now, we have to develop all the integrations. It would be so much better if this was already done. 

SAP often launches new solutions without first providing the proper documentation. We end up figuring it out, however, it would be nice to have that documentation up front.

The two things that need to be improved are price and customization. These are two dynamic changes that every customer will want.

When it comes to the delivery of features, I would like it presented in a more user-friendly way. Every year, when a new version is released, it comes with a very thick booklet of 300 or 400 pages and it is a little difficult to comprehend. This is something that should be simplified. A simple comparison between the older and newer version would be very helpful for customers and consultants.

The default UI has been the same for a long time and in my last few projects, I've found that it wasn't fast enough. 

This is an integrated system so it is very complex. It is not like Windows or like Microsoft products where you can use Word or you use Excel and it is familiar and easy to use. The interface is something that is very confusing from my point of view. It can and should be simplified. It needs some work on the front end to be more user-friendly and customizable to the user's needs.  

It is not a very good product from the perspective of ease-of-use. Trying to implement it is like you want to prepare some food. You have raw materials like spices in a pile but there is no recipe as to how to mix them. It is a recipe missing the proportion to mix the spices in.  

In the case of S/4HANA, that recipe depends on how the organization requires it to operate. A better result depends upon the implementation partner's decisions in handling the wide range of choices offered by the product. If these decisions are not good, once the product is already developed, you may come to know after years of using it that it was not implemented optimally. Then you end up making customizations and work-arounds because of this initial implementation. That is bad practice. Customization and work-arounds will only lead to more complexity. It is a very big product that can not be understood in a short span of time and implemented quickly. Meticulous planning is ultimately important.  

A lot depends on the implementation partner and if they understand your needs. An implementation partner who rushes in too quickly with a solution can get it wrong and that can cause major problems in the long run.  

Every business has some unique requirements which can mean customizations are required. What I'd really like to see is the development of an industry specific solution for the food industry, in particular the supply and demand side that's very critical to us, given that there are issues with products that have a shorter shelf life.

This is a very costly solution.

We are always looking for a better user experience. We would like to see more consolidation in SAP S4HANA because of all the financial compliance and regulatory changes.

The resource usage could be improved - it's memory-hungry, so mid-range servers struggle to run it.

An area for improvement would be integration with different kinds of legacies. In the next release, I would like the product to be prepared for blockchain technology and the best way to communicate with social networking.

While the solution contemplates a competitively priced model, its pricing could be cheaper. 

In an upcoming release, it would be beneficial to have more practical intelligence in the system, such as protective maintenance, or artificial intelligence. This would not be too complicated to provide nowadays. If you have a mission learning or artificial intelligence, you have to have it in the cloud and have cooperation between the ERP and the cloud. It is not as good as it could be.

This solution works with the configuration, if the prerequisites are very clear and can be configured it works perfectly. If you need to simulate something, as a predictive tool this kind of simulation is not very accurate and it has limitations. This is something that could improve.

In an upcoming release, the allocation process should be revised and improved.

The theory-side of the solution needs to be improved. They need to come up with a simple way to explain to their customers how to properly use it and perform analysis and move on from there.

In the next release, I would like to see more integration scenarios with the cloud, straight out of the box.

The solution isn't lacking any features per se. Clients aren't coming to us and saying "we need this or that."

The cost of the solution is quite high. It needs to be adjusted.

The integration could be better. They have many different kinds of house platforms, and then it becomes complicated to have integration within all of these different systems.

The common issues being raised right now by the end-users are mostly related to the usability. Especially on the Fiori interface. I think they're a manufacturing company and they're implementing lean manufacturing. They are actually counting the number of clicks and screens that are being used by their end-users so they can have a more efficient and intuitive approach on the Fiori apps.

In terms of what features should be included in the next release, there would be too many to mention. I would probably say right now, as part of the planning session, they're going to go through the entire gamut of features where they can improve and where we're lacking in some parts. We're planning to implement a trial for support and warehouse management. But it's a big list right now and I can't think of anything specific. 

In terms of what could be improved, I would say the usability aspect of it for the users. Additionally, from the corporate perspective, some of the more stringent integrations across modules and also allowing integrations from third-party applications.

• S/4HANA 1610: We found very less Fiori apps — a few apps not working.
• All module Fiori apps need to be tuned.

MRP repost area should be improved. The production information report also needs to be improved. 

Planned Order List needs a change of screen.

There should be a place where I can get the best available applications in one place. Currently, Fiori applications are available in different tiles on the dashboards. If anyone wants to check the financial, sales, and inventory reporting in one place, it is not possible in Fiori. We would have to develop a custom Fiori application. If that feature can be incorporated into the standard Fiori, it will be helpful for us.

You will not see convenient user experiences with SAP S4HANA's website or application. It is not mobile-friendly either. 

Introducing better functions to our customers with the Fiori app is not easy for consultants. There are too many apps, and it takes time to understand their functions. You cannot know all the functions when you implement them, which is a big challenge. The solution should include a comprehensive migration tool for implementation.