Hybrid: for example, the source systems on-premises and the target systems on cloud
What is System Copy as a Service?
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
Copy only specific data
Third-party tools sometimes have a different focus than TDMS. The tools each offer a more or less generally understandable user guidance and are thus "out-of-the-box" products that do not require external consulting on implementation or application.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
Incremental Migration (IMIG): - OS- and DB- independent - for homogeneous and heterogeneous system copies - for Unicode conversions - for ABAP systems as of 4.0B.
For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy.