It can be difficult keeping SAP landscapes consistent. For example, as Quality Assurance environments are refreshed, over time systems can begin to get out of sync. The number of DEV system transports existing only in the development system, unlikely to ever be moved to Production, grows.
Many SAP IT teams have stories of inadvertently migrating historical unwanted changes to Production, sometimes costing thousands or even millions. These unwanted DEV system transports become hazardous and potentially quite dangerous.
Quarantining unwanted transports
A good technique for preventing unwanted transports progressing into Production, is to remove the transports data file from the transport data directory. For Rev-Trac customers, utilization of inbuilt reporting can help to determine exactly which transports should be quarantined.
The „Transports only on deleted Rev-Trac’s“ report is available to assist in management of unwanted change. This can be used to ensure that all of the transports not going to Production have been quarantined.
The „Rev-Trac Comparison“ report can be used to identify transports that exist within the Development system, but do not exist in QA. This list can be used to identify transports, which should be maintained or quarantined.
The Quarantine facility also acts as an important tool in keeping Rev-Trac’s OOPS (Overtake Overwrite Protection System), relevant and free of false positives.
Specifically when an object change does not go to production, and subsequent versions of the objects are written, which are suitable for production, OOPS will provide an Overtake report. By Quarantining transports, Rev-Trac will remove the quarantined transports from appearing in OOPS reports. This ensures that the technical team responsible for delivering change are seeing relevant safety checks during the migration steps.
For more information about transport quarantine strategy and keeping OOPS clean and tidy, feel free to reach out to me and my team at [email protected]