Shutting Down the Target System
Job logic instead of customizing
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
What is System Copy as a Service?
The number of R3load processes to be started in parallel is specified in the {ex|im}port_monitor_cmd.properties configuration file. The Migration Monitor stores the state of the export or import process in the {ex|im}port_state.properties file. For each package being processed, there is a = line.
There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
Some useful tips about SAP basis can be found on www.sap-corner.de.
An important first step is to integrate the BDLS run into the system copy.
For companies, however, professional test data management is not only interesting for optimizing existing systems and processes particularly securely and quickly.