During the project, the team struggled to identify critical areas impacted by the changes to the system. This created the need to retest the entire system after each code introduction, which dramatically impacted the project delivery time and budget. With a project scope of this size, consistently retesting the entire system with each change was not an option OMV could afford.
It was at this point the team decided to leverage an impact analysis tool to guide their testing activities and make their SAP testing more efficient. The team chose Tricentis LiveCompare because its AI-powered impact analysis exposes the risks to critical business functionality posed by any standard or custom object change. By pinpointing the most at-risk areas to be tested, the team would be able to reduce testing timelines while still ensuring 100% risk coverage to their SAP environment. When paired with Tosca, LiveCompare would provide even more value to the team by automatically creating the optimal test plan for any SAP update, identifying the best test cases to run in Tosca as well as any tests that need to be created. This meant the OMV teams could leverage their existing automation suite in Tosca to ensure future changes to their S/4HANA systems could go live faster and with less risk to the business.
“Before we send a transport live, we run an impact analysis and execute coordinating test cases in Tosca. Defects from the results are created in our solution manager to be worked on and re-integrated back into the transport management system again,” says Gahler. “This process allows us to verify upfront before we release something that could affect our live systems negatively.” LiveCompare has significantly reduced the testing time required for each major release in OMV’s three installations of S/4HANA. Instead of taking up to six weeks to test each instance, the team now needs only two weeks per instance. This not only increases the pace at which OMV can release updates, it allows domain experts to spend more time planning future releases instead of testing the current one.
Pivotal decisions on SAP S/4HANA upgrades
There was an unexpected decision for OMV to make during the project phase that could have potentially impacted the timeline for go-live. SAP had released a newer version of S/4HANA. The team had to decide to either move to the newer version now or finish their implementation of the older S/4 system and upgrade afterwards. With the help of LiveCompare, the team made the decision to upgrade during the current project phase. Gahler explains, “LiveCompare told us which objects, which new functionality, and which custom code was affected by the new program. We could easily identify where we needed to re-test and where we needed to concentrate our efforts to guarantee this upgrade would not impact our timelines.”