Automation of homogeneous SAP system copies
Heterogeneous system copy: As the name suggests, the operating system and/or database on the source and target systems are different. One takes thus in the context of the copy a platform change. This procedure is currently gaining in relevance, as it is required for the migration from SAP ERP to S/4HANA. If the current system runs on Windows Server and SQL Server or Oracle, the target system must now run on Linux and SAP 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.
Differentiation between homogeneous and heterogeneous SAP system copy
This means that the time required to create an SAP system copy - be it for providing a system copy for training purposes, be it for testing purposes or whatever - is drastically minimized. Instead of several days, only hours are required for system copying.
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
Of course, time savings also mean money savings.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
Additional backup: server profiles, RFC connection passwords.