TM-TMS (Transport Manager)
Technical system copy for the upgrade
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
SAP system copies and the DSGVO
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.
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
With "Shortcut for SAP Systems", a mature and yet very cost-effective product is available that offers useful functions for system copies. For example, SAP system users can be backed up and restored. Likewise, system-specific tables can be backed up before the system copy and restored after the system copy. And all this can also be automated.
Ideally, a tool for creating SAP system copies should take the following core copy processes into account: Check and pre-processing, restore, actual execution, and post-processing.
In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.