SAP system deployment scenarios
SAP system copy and the cloud
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
Purpose of the SAP system copy
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
For a heterogeneous system copy and for homogeneous system copies for which there is no special way for the database used, the source system must be exported. This is done with SAP tools (SUM). The export files are copied to the prepared target system and imported again during the SAP installation with SUM. A relatively comfortable way. But it can be even more comfortable.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
In addition, these processes for system copying using such automation tools can be planned, standardized and always run at a high level of process quality.
Larger productive systems, on the other hand, are not so easy to virtualize.