DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.
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.
SAP SYSTEM COPY - in a nutshell
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.
Unicode conversion: During the copy, the system is converted from non-Unicode to Unicode. This happens in the context of a homogeneous or heterogeneous system copy. In connection with Unicode must be differentiated between the system copy of a Unicode system and the Unicode conversion.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!
That's why you should avoid upgrade downtime in both the production source system and the non-production target system.
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market.