Keeping S/4 Hana Clean Is Easier Said Than Done

As of now, SAP only offers customers a somewhat adequate solution for the S/4 Hana dilemma—the SAP Cloud Platform. As impractical as it may sound, it could work—if SAP itself became a little more flexible and met its customers halfway.

Hoping it will keep the S/4 Hana core clean, the ERP company advertises the platform’s in-app development capabilities. However, it’s no secret that these are not up to par yet; otherwise, customers wouldn’t need to develop their own customized solutions for S/4 Hana.

Hoping it will keep the S/4 Hana core clean, the ERP company advertises the platform’s in-app development capabilities. However, it’s no secret that these are not up to par yet; otherwise, customers wouldn’t need to develop their own customized solutions for S/4 Hana.

Customization can bring decisive competitive advantages – no wonder no SAP customer would willingly give that up.

It’s clear what’s happening: more S/4 functionalities mean more difficult integrations mean many more customized products. The solution? Collaborating with SAP!

It’s clear what’s happening: more S/4 functionalities mean more difficult integrations mean many more customized products. The solution? Collaborating with SAP!

As counterintuitive as this might seem at first, collaborating with the ERP giant is a viable long-term strategy for customers.

Users can actively demand the creation or development of new features, for example through user groups. If three or more customers demand similar innovations, there’s a good chance that SAP will listen.

Many customized solutions are only created to avoid having to buy expensive add-ons. Customers don’t use add-ons like the treasury module, the commodity pricing engine or the master data management module and just develop their own solutions instead.

No additional licenses for S/4 Hana functionalities

This shows that most customers don’t need the full functional scopes of these add-ons and instead develop their own easier solutions to match their requirements. Maybe SAP should sell less and listen more.

Customers want to use some processes and functionalities without immediately having to pay for additional licenses. Subsequent licensing fees impede collaboration between SAP and customer. Discounts discredit SAP’s pricing and product policy.

Theoretically, SAP knows all of this – but practically, it hasn’t done nearly enough to combat these developments.

For example, SAP support has gotten significantly better over the past few years. In the long term, it’s more viable to work with SAP directly to fix problems.

However, there’s still a lot of effort involved on the customer’s part, which is why many users try to fix the problem themselves. This approach might seem quicker and less cumbersome, but it will actually lead to more problems down the road.