Reviews (1-25 of 73)
The powers of S/4 HANA extend beyond that too, as I found it very impactful in providing template roles and functionalities for the supply chain specifically. Although Fiori and the groups/catalogs remain new information to me, our team was able to leverage this base functionality and extend it for our biotech client, who now uses the supply chain and warehouse management sections in a productive environment. Also, we found that the migration from EHP8 was made quite painless by the SAP team, as all we needed to fix up at the client was the Business Partners (there is a fair amount of manual work there), as well as some of the finance tables. Otherwise, the migration went smoothly and the client has been happy with their environment since. If you're not on S/4HANA yet, look at getting it started, as official support ends in 2025 I believe!
- The upgrade path from SAP ERP EHP8 is well documented and easy to follow.
- Fiori provides a much smoother experience than jumping in/out of transactions.
- The templated applications which are pre-built, offer very useful functionalities.
- There is a "Best Practice" package with documents, processes, transactions and the like that you can download using Solution Manager 7.2 into your landscape. Then you can re-engineer this later to add value to your clients' lives.
- It's not necessarily clear to me how HANA itself makes transaction speeds faster, as I have used S4 ontop of ASE and it seems about the same.
- The business partner reconfiguration for the upgrade path S/4HANA is a little bit unwieldy.
- Development using the Eclipse tools is more difficult to set up and learn versus the traditional SE80 design.
Existing reports, dynpros, and FPM need to be modified and changed.
- Fiori interface. There is no comparison between the old SAP GUI interface and the new Fiori.
- They came from an Oracle database environment, so with SAP S/4 HANA they found a better performance in their batch processes. They had problems finishing batch processes before 8 a.m., with no real data. Now they have real data (data comes from outside systems) when users start his work.
- For IT people, the simple database structure helps to understand and resolve incidents.
- We have been using S/4 HANA for only one month and we do have much experience with, but we can say that the migration process (Brownfield) is not an easy process. SAP has announced new tools that we will test in our future migrations.
- The use of Fiori apps has helped a lot to provide a quick overview of main indicators to users and also management to have a quick overview on the most updated figures.
- New MDG version within S/4HANA has included some new functions missing in previous versions that were missed from the very beginning (e.g., mass update).
- More user friendly interface to user. More interactive and graphic.
- The idea was to extend S/4HANA for SD transactions regarding sales order processing, billing and warehousing. It seems that at the moment not all functionalities available in ECC are available in S/4HANA.
- Collections Tool or Dispute Management modules have not been updated and functionalities currently customised in the system we are using are still not available as part of out-of-the-box versions.
- MDG forms and help messages can be further improved. No links to missing fields exists.
- SAP S/4HANA helps you the analyze the data in real time.
- It helps you to extract reports, purchasing and selling much faster.
- With SAP Fiori, reports are really interactive.
- You can interact from on-premise and cloud.
- With the coming version, I could expect lot of additional features as an end user where it can be collaborated with other 3rd-party tools.
- I would expect SAP to develop more reports on taxes.
2. It provided Interactive UI Portal.
- Reducing time, as it gives results on the fly.
- Improving performance, due to its database being extremely fast and also due to code push-down techniques.
- Robust in nature.
- Could be more flexible and agile.
- SQL/coding side.
- Much faster than ECC. In-memory processing definitely speeds up transaction processing.
- Embedded BW & analytics capabilities easily enable a lot of functionality that in the R3 version would have taken massive development time and resources.
- Fiori has a lot of potential to revolutionize the user experience (UX).
- S/4HANA is relatively new and it seems that the body of knowledge to effectively deploy with all of the new features is somewhat limited. SAP does seem very dedicated to rapidly grow the skills and body of knowledge with training and support.
- Early versions of Fiori are somewhat limited.
- Upgrading from version to version (on-prem versions) can be challenging Upgrading to the newest version 1909 takes a lot of time, planning, and resources to execute for us.
Avtomotive d.o.o., Strip's d.o.o., Lumenia d.o.o. and Post of Slovenia d.o.. So SAP S/4HANA addresses many different type of businesses, from automotive to productions and logistics.
- SAP HANA uses analyses to predict the buyers’ behaviour and the success of products in real time.
- SAP HANA links up with your existing systems and does the finances, sales, purchases, logistics, product development and manufacturing for you in order to tackle your specific challenges in the industry.
- A unique approach to commerce enables you to work with just one accurate source of information and plan and make decisions in real time.
- Printing from S/4 HANA could be designed in more user friendly way. Sometimes it's hard for beginners to start using SAP as is.
- S/4 HANA new GUI could have some more colors and different icons. So design has very big room for improvement.
- More S/4 HANA web courses.
Less appropriate: Upgrade from SAP ERP to SAP S/4 HANA in companies which have many integrations with other non-SAP systems by IDOCs or XML-s could be a real pain and hardship.
- The platform is based on the HANA Database which is ideal to use OLAP and OLTP on one common platform.
- S/4HANA Central Finance is a great module for big organizations planning to move their legacy systems into S/4HANA in a phased manner.
- Some modules, such as QM and PM are perhaps not as matured as ECC.
- There is room for improvement for more Fiori Apps to move away from the SAP GUI.
- Much better organized database (comparing to Oracle or DB2, etc.) and simplification of storing and processing of data. Fewer tables that are easier to customize in some aspects. Faster, native integration via SLT. Embedded solutions (EWM). Group reporting.
- Code adaption (especially with "heavy" transactions)
- Not just to announce new simplifications and/or features but also test them good before release.
EDI storage locations/warehouses needs more flexibility when we need to manually cancel deliveries.
- The entire solution we are using is Fiori app-based, displaying tiles/apps that are assigned to each user.
- Even though we only have 6 months worth of live data now, most of the standard SAP transactions run quickly to report on that entire period of data.
- New functionality is released every 3 months.
- The quarterly upgrades are great for new functionality but they do put us in a position of dealing with freeze periods and testing on a quarterly basis.
- Some standard EDI transactions were not ready to implement with the long term SOAP technology so we had to use the old IDOC technology to get things in place of Go-Live.
- It is not easy to identify simple data or configuration issues because we do not have the ability to run debug or use the data dictionary directly anymore.
- SAP Fiori for Mobile Application.
- A data hub for getting data from other sources and analyzing.
- Optimizing the data and cleaning the data to produce quality.
- Automated Data Management, so that we are not using everything in memory.
- More reach in the marketplace for apps, applets, plug-ins, and interfaces.
- Migration tools are seamless, live, and asynchronous.
It's less appropriate for extreme custom codes (z) as a legacy of the organization. There are liabilities in terms of huge contract and dependencies, and regulations and compliance. In addition, it has third party tools and application dependencies.
- In-memory database.
- Backup and restore are very easy and take less time.
- Can manage multiple DB's from HANA Cockpit.
- Easy to manage.
- DB Implementation and maintenance is better than other DBs.
- Very frequent DB patch releases from SAP compared to other DB’s like Oracle.
- Seamless failover is not happening in Primary DB and DR.
- We don’t have the correct procedure to find the DB growth history and DB size from Studio or from HANA cockpit. We raised an incident for this, but they told us they don't have this procedure.
- Not able to maintain 2 hours gap between Primary DB to DR which is available with Oracle.
- Frequently, resident memory is going high and we raised multiple incidents and got replay as using more and more resident memory is good for your DB (we don’t think it will be like that).
- BW HANA recovery time is huge (HANA 1.0).
- Log trace decoder is not available.
- We have a ton of queries and confusions in DR failover and failback.
- Backup and Restore
- DB implementation and Maintenance
- Can manage multiple DB's from one administrative console like HANA Cockpit
- Definitely faster.
- Reduced DB size.
- Analytical Fiori applications are plenty and give much more real-time flexibility.
- Role-based process design. App focused on a role rather than a complicated TCode (e.g. MIGO replaced by focused inventory apps).
- Screens can definitely be improved further to the likes of SuccessFactors.
- The delta features that come with every release are quite difficult to interpret. Needs simplification.
- On the P2P layer features of Ariba could be embedded.
- S/4HANA provides better database space and performance because it only runs on HANA DB.
- Very powerful.
- Customer friendly.
- User experience.
- Custom code adaptation.
- Next releases should not be released so frequently. Once implemented and functional we are getting next release.
SAP S/4HANA Scorecard Summary
Feature Scorecard Summary
About SAP S/4HANA
SAP S/4HANA stands for SAP
Suite 4 HANA. According to the vendor, it is a next-generation integrated enterprise resource planning
(ERP) software that is designed for businesses of all sizes, in all industries,
that require deep and broad functionality combined with a high degree of
flexibility. SAP S/4HANA was launched in 2015 and been adopted by more than
3,200 customers over a period of sixteen months. The vendor says SAP S/4HANA is materially
different from anything SAP has done before and represents the company’s
biggest innovation since SAP R/3.
SAP S/4HANA is intended to provide a digital core for an organization. It is fully architected for the most advanced in-memory platform, SAP HANA, and is designed on the most modern design principles with the SAP Fiori user experience to create a personalized and simple feel on users’ device of choice (tablet, laptop, mobile). SAP S/4HANA aims to simplify an organizations’ system landscape and reduce total cost of ownership by shrinking the data footprint while at the same time improving productivity levels in the form of higher throughput.
S/4HANA can be deployed either on premise, in the cloud, or in a hybrid combination for quick time-to-value.
SAP S/4HANA Screenshots
SAP S/4HANA Video
SAP S/4HANA Downloadables
SAP S/4HANA Competitors
SAP S/4HANA Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
SAP S/4HANA Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux, Mac|
|Mobile Application:||Apple iOS, Android, Windows Phone|
|Supported Languages:||Most languages|