fbpx
Chris Drake

Managing the sequencing of high volume transport migration with Rev-Trac’s Release Management Workbench

Chris Drake | May 3, 2016

Did you know that Rev-Trac’s Release Management Workbench allows for an organization to group together many changes, synchronize transports from changes to their release, and deploy in mass using minimal approvals, without compromising good governance?

Typically when an organization deploys a large volume of changes to production there are many concerns around the sequencing/conflict of transports. These sequencing/conflict concerns can be divided into two major categories:

  1. Sequencing of transports within a release
  2. Impact of excluded transports on a release

When using the Release Management Workbench, organizations no longer need to fear either of these concerns, as they are automatically managed by Rev-Trac.

  1. Sequencing of transports within a release

When transports are synchronized between the many changes and their release request, Rev-Trac uses its dynamic sequencing logic to determine the sequence for which the transports should be queued and migrated within the release. The dynamic sequencing logic is as follows:

  1. Adjust sequence of transports containing conflicting objects by release date and time
  2. Honor the change request sequence (which allows developers to specify a unique sequence within the same change ticket e.g. send data dictionary objects before program)
  3. Honor the transport dependencies (which allows developers to specify a desired sequence across different change requests)

This logic ensures that the transports contained within a release are migrated in the correct sequence once approved for production.

When using the Release Management Workbench, organizations no longer need to fear either of these concerns, as they are automatically managed by Rev-Trac.

  1. Impact of excluded transports on a release

Object sequencing issues and dependencies can occur when changes are included in a release, but their dependent changes are accidentally omitted.

The Release Management Workbench provides a pre-emptive “Overtake and Overwrite” check, as well as a dependency check, which can be performed against the release.

The Overtake and Overwrite check will identify any out of sequence migrations that might occur as a result of introducing the wrong changes, or accidentally omitting changes from a release. It becomes clear to a release manager which changes should be added or removed from a release in order to ensure the stability of the production environment.

In the same manner the dependency check will ensure that developer set dependencies are honored when the release is triggered for migration. The dependent change can be included or the dependee change can be removed from a request.

In additon to the pre-emptive checks, Rev-Trac will automatically trigger an Overtake and Overwrite check and a dependency check as the release is approved for any target system such as pre-production or production.

What will work for you?

There are many methods for managing releases in Rev-Trac. Feel free to reach out to our team at [email protected] to find out what the best approach to release management is for your organization.

Chris Drake

Chris first joined the company in 2007 on the front line in customer support. In the role, he gained a comprehensive knowledge of the concerns and priorities customers have from both a user and strategic decision-maker standpoints. Working in the field as an implementation consultant, Chris has a deep understanding of SAP and change management and the impact manual processes have on SAP systems stability.
See all articles by Chris Drake