The Rev-Trac Release Management Workbench allows for an organization to recognize and separately control SAP Changes which are not assigned to an SAP Release. This can be used to benefit an organization in a few ways and can be used differently depending on the type of Change.
In this article I will discuss some of the benefits for the Unassigned Change feature in both an SAP project and an SAP support environment.
Using a variant in the Release Management Workbench, it is possible to make views very specific to the desired controls. As Release Management is set up to use a common Rev-Trac-Project, it is likely that an organization’s various SAP Support Tracks and SAP Project Tracks will be distinguishable by the Rev-Trac-Project field. So it is important to set up variants specific to the SAP Releases that the organization would like to control. To further control the Release Management Workbench, the variants should filter undesired requests from the view usually these are complete or deleted Rev-Trac requests.
In an SAP support environment, it is possible to have the individual SAP Changes work quite separately without ever interacting with a Release until they have been fully tested, code reviewed and are ready for production. In an ideal environment, the Change Advisory Board (CAB) will log into the Release Management Workbench during their production go-live meeting and will have a list of SAP Changes in the Unassigned Changes column, which are at various statuses. Further control of the variant will allow for the CAB to filter the Unassigned Changes to those in a status of Ready for Production. All SAP Changes which are marked Ready for Production are in a state which will allow for them to be added to an SAP Support Release and approved for migration to production at a Release level. The CAB will have full control of which Changes can be added to the Support Release for that period through dragging and dropping the Changes from the Unassigned Changes, or across Releases.
Due to the nature of SAP project work, it is often clear which SAP Release a Change should be part of early in the life of the SAP Change. As such, when the CAB gets ready to approve a Project Release either to Pre-Production or Production (at the Release level), the Release will already have been built, and will include a proposed list of SAP Changes for migration to the next environment (Pre-Production or Production depending on the landscape setup). The CAB will likely find Changes which are not yet ready for Production and may risk delaying the Release. At this time, the CAB or Release Manager can drag the pre-mature Changes out of the Release, either into the next scheduled Release, or into the Unassigned Changes column. At this time the CAB can also review the Unassigned Changes, to see if any are suitable to be included in the current Release (perhaps relegated from a previous Release due to issues in development, delayed testing, object collisions or dependencies).
The Unassigned Changes can be used as a powerful feature of the Release Management Workbench to improve quality, transparency and agility during a Release go-live.
Over the next few months I will be providing some more insights into the abilities and recommended approaches to managing SAP Releases with the use of the new Release Management Workbench.