In speaking with SAP IT teams who are successfully pivoting to agile SAP development, one theme continues to stand out. Control of the SAP change and release process needs to move from a single, centralized point of control to multiple, decentralized points of control.
One of the primary benefits of your support plan is to receive the latest Rev-Trac version developed by RSC – and you can always download and read about the latest new features and enhancements made to Rev-Trac and the Mobile Web GUI from the Support Portal under downloads. One new feature I found is the Parallel Development Workbench provided in v7 SPS02. I’ll provide you a high-level overview of this new feature in today’s blog.
When SAP introduced ChaRM into the SAP Solution Manager ALM suite, a method of testing changes using a Transport of Copies (TOC) instead of the original development transport was also introduced. This did simplify things because essentially only a single transport would be sent to each production system for each change ticket. In addition, once the TOC is created the development system will continue to hold a lock on the original objects whilst the TOC is promoted through QAS to PRD. Thus, minimizing potential for parallel development to occur. On the surface both benefits seem reasonable along with the TOC method to achieve them.
Today, it’s quite common to see SAP environments consisting of three or four SAP applications running a two or three track system architecture (N, N+1, N+2) with additional integration testing and preproduction systems included. However, over recent months there has been a growing question among SAP IT organizations around the multi-tier strategy and looking at ways to go back to a single-track, flat architecture. Perhaps this is due to the high costs of standing up additional SAP instances, retrofit and system synchronization challenges or simply a reaction to the overwhelming complexity.