I’ve worked specifically in SAP change management for more years than I care to mention, and one thing I’ve heard repeatedly is the need for a reliable method of checking inter-object dependencies between transports.
Those of us fortunate enough to leverage a world-class change management solution like Rev-Trac have a distinct advantage. Certainly over those who are still having to manage their changes manually. Revelation Software Concepts (RSC) goes to great lengths to provide Rev-Trac users with a complete suite of tools to facilitate the detailed analysis of ‘in progress’ transports, ensuring we don’t inadvertently shoot ourselves in the foot.
Rev-Trac Extended Locking
Rev-Trac’s Extended Locking functionality immediately informs users if another user is working with the same object or key-level configuration, even after that change and its subsequent locks have been released in the development system. The subsequent In-Flight Parallel Development Reporting functionality will help users track this parallel development as it moves through the landscape.
Don’t forget the all-important Rev-Trac OOPS functionality. Rev-Trac OOPS facilitates the moving of parallel changes in the proper order to avoid any possible Overtake and Overwrite situations.
The recently introduction Rev-Trac Peripheral Object Dependency System (PODS) checking functionality is in a class by itself. Being able to look ahead to make sure all the pieces are in place before the actual migration is performed, is invaluable! Think of all the RC=8 you could avoid if you could look ahead to make sure that the table your program needs is already present in the target system.
This is the piece that has been missing all of these years, and now it’s available to everyone. You can look ahead for your specific Rev-Trac requests and the potentially many transports they contain. Similarly, you can check your Release Management Workbench requests that contain many Rev-Trac requests and their even more transports.