Challenges reduced!
Purpose of the SAP system copy
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
Different DDLORA* files can be assigned to the R3load packages. The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.
Critical factor: Availability
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final copy.
System copy of a Unicode system: Source and target system are Unicode systems. The same procedures can be used for the copy, as with the copy of non-Unicode systems.
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.
The important thing is to think about the target system before building it.
Test and development system: After a new productive system has been set up, at least one identical development system or even one test system is still needed.