SAP S/4HANA Cloud Review
Updated November 30, 2024
SAP S/4HANA Cloud Review
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with SAP S/4HANA Cloud
We have implemented SAP S/4HANA Cloud for one of our subsidiaries. It is mainly used by the financial department. They had an ECC system, but they wanted to be prepared for new business and SAP S/4HANA Cloud fits this goal.
Pros
- 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/4HANA Cloud 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.
Cons
- We have been using SAP S/4HANA Cloud 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.
- Infrastructure cost increase. The fact of implementing SAP S/4HANA Cloud increases the cost of the infrastructure by a significant amount.
- Reduced user time due to a more usable and friendly interface (Fiori). Users don't need to navigate several screens to find or complete information.
- Also, due to SAP S/4HANA Cloud improved performance, users can get reports quickly so they improve their productivity by being able to respond more quickly to the business.
No others compared. I had an ECC system with Oracle Database before I migrated to SAP S/4HANA Cloud. With Oracle I had performance problems, especially in batch processes with a large amount of data to manage or with massive processes. With HANA all this has improved substantially without practically having to touch code. Also users wanted a better interface (Fiori), and SAP S/4HANA Cloud was the right product.
SAP S/4HANA Cloud Feature Ratings
SAP Adoption
- Third-party professional services
We use SAP Services as a company to implement SAP S/4 HANA Cloud, because we want the support of the owner of the software and be sure that we are following the best practices of SAP. We have a large SAP landscape with several products, some of them need migration to S/4, and other only lift and shift migration.
First of all we took a knowledge training of the new system (basic actions), and after that a specifically training for each set of key users. These key users helped us to expand this knowledge to theirs colleagues in the department. Also we had a support team for the first weeks of adoption in order to answer and help users.
Change management was minimal - We really didn't have organizational change, the departments were already with a correct internal organization, the process were ready to be migrated to the new implementation. We tried to impact as minimal as we could.
As I said before, we impacted minimally to the processes because we didn't want to change the user routine. We did it to reduce the rejection of the users. So we showed the mandatory changes due to this new system, without include process changes. Probably, once the users will be used to the new system, we will introduce changes to make the processes more efficient.
As I said before, we trained all the users in two phases. First, we trained to the new look and feel of the system (change to the Fiori interface), so they knew how to move. After, we trained to the specific functional knowledge, with no changes related to their processes. We thought there were enough changes for the users.
We followed two paths. One technical and other user adoption. When we were working on the more functional part with the users, we were showing them how they would look in the new system. This meant that when we got to the training part, they already knew the system (even if it was only at a visual level) and this phase was easier.
I think the approach we took of not adding more changes than necessary was the right one. Users focused on learning how to navigate the new system with processes they already knew without having to learn new ones. There was no resistance to change.
One issue that we will have to think about in the future is the different learning speed that users may have: there are some that learn very quickly and others do not, and need more support or training.
One issue that we will have to think about in the future is the different learning speed that users may have: there are some that learn very quickly and others do not, and need more support or training.
Comments
Please log in to join the conversation