Automation as a Driver of Innovation: With DevOps into the SAP Future
When it comes to digitization efforts in their companies, CIOs are more skeptical than they were a year ago. Although, according to the DSAG Investment Report 2019, a large number of respondents are planning to convert their Business Suite to S/4 Hana, in practice this step is not proceeding as quickly as expected - completed projects are not yet to be found in large numbers.
But why is that? Why are so many companies hesitant? It's not as if SAP customers don't recognize the benefits - lean end-to-end processes, faster innovation.
On the contrary: according to a survey of DSAG members, five percent would like to tackle the S/4 Hana migration this year, just under 40 percent in the next three years, and another 30 percent after that.
All other companies have not yet made a decision. According to that survey, the rate of realized projects is stagnating at only three percent, which could be due to implementation projects that have begun taking longer than originally planned, companies having misjudged the effort involved, or opting for brownfield implementations that require a longer changeover period due to their complexity.
In fact, current studies show that brownfield migration is more widespread than "greenfield" implementation. The latter is recommended by SAP; in the future, the release frequency is to be significantly increased for S/4 Hana as an "innovation system".
Regardless of which migration path companies choose: In the event that they need to run ECC and S/4 Hana in parallel, dual maintenance support is necessary.
In order to cope with the increasing complexity, especially in the case of a two-track migration, as well as ever shorter innovation cycles, companies must first build up know-how, according to DSAG technology board member Steffen Pietsch.
You need to be able to quickly implement changes to existing systems and processes, as well as automate change deployment across the board.
This in turn makes security checks and dependency checks at configuration and code level as well as extensive monitoring essential. A need that is already reflected in practice today.
This was one of the central wishes of SAP users at the DSAG Technology Days in the spring: more automation and integration.
Automation in change and release management not only makes it possible to increase quality, it also speeds up deployment processes and eliminates many technical problems before the actual quality assurance stage - which threatens to become a bottleneck due to the complexity of SAP environments with their countless dependencies.
This calls for complementary measures such as support by automated regression tests, which cover practically the entire productive environment and therefore deliver realistic results.
In addition, wherever possible, it is recommended to automate progressive testing of new code to ensure that potential bugs can be identified and fixed at the earliest possible stage.
The more complex an SAP landscape, the more difficult it is to adequately address this complexity. In order to achieve the fastest possible software delivery and to ensure "stable conditions" in the environments, automation and complete integration of transport and content as well as functional tests are keys to efficiency.
Consistent use of Continuous Integration (CI) and Continuous Delivery (CD) during development and delivery allows changes to be continuously integrated into new software versions.
Ideally, the frequency of innovation in the S/4 Hana context then turns out to be problem-free - and this even in the brownfield approach.
