Refresh Test Systems

To refresh a test system, you make a system copy of the production system to the test system.

You can use the Refresh Test System scenario to do the following:

Save your current developments before you execute a system copy of the production system to the test system.
Append the saved transports to the import queue of the refreshed test system after the system copy.

By executing a system copy of the production system (source system) to the test system (target system), you bring the test system into a system status that represents the current status of the production system. To avoid losing all current developments that have been imported into the test system but not yet into the production system (newer versions of Workbench objects and Customizing settings), you can use the Refresh Test System scenario to save the current developments before executing the system copy.

You use the Refresh Test System scenario to perform a delta calculation: All imported transport requests are compared between the two systems. The system calculates which transport requests were imported into the test system, but not yet into the production system (or another source system you specified). The delta calculation is then saved at operating system level.

In the next step, you perform the system copy by using the known AS ABAP functions (not included in the Refresh Test System scenario).

After a successful system copy, you execute the Re-apply Transports function in the Refresh Test System scenario to append the saved delta calculation of the transports to the import queue of the refreshed test system.

For more information about the prerequisites and configuration for the Refresh Test Systems function, see the Configuration Guide for Focused Build for SAP Solution Manager.