How we handled update-related issues
“SAP wants every customer to run the same software version of SAP S/4HANA,” explains Tom Vandewinckele, delaware’s solution lead for cloud enablement & operations. “This makes it a lot easier to deal with security threats and other issues. To make this happen, SAP pushes forced updates to all of its clients every quarter to make sure that every user benefits from the latest functionalities and patches.”
As delaware would soon discover, there is a major downside to this practice as well. “SAP always tests the updates on the most common functionalities,” Tom continues. “However, there are a myriad of ways to use these applications, and it’s impossible for SAP to test them all, especially when there’s a lot of custom development next to the standard business app. So every three months, we were confronted with errors and aspects of the system that simply stopped working altogether.”
To prevent this from happening, SAP provides users with a three-week testing period before upgrading the production environment. During this time, key users can report issues back to SAP. In practice, this approach often failed. Tom: “Key users simply didn’t have enough time to run tests on top of their daily tasks. When issues were detected, it was often too late to do anything about them before the update.”