We take over your SAP system copies as a service
SAP SYSTEM COPY - in a nutshell
The term "system copy" describes the process of creating a copy of an SAP system on a new server. There are two types to be distinguished: homogeneous and heterogeneous system copy and one can get to the system copy in different ways.
SAP recommends that you always update enterprise software in your production system using the SAP transport system and never make changes directly in the production system. In addition, SAP suggests that you validate change transports through a QA system that is approximately identical to the production system and has up-to-date transaction data. Outdated data can affect the validity of change transport tests, which can lead to errors and failures in the production system. However, end-user transaction data is received only from the production system. Such data must therefore be passed regularly throughout the SAP transport chain to ensure that your non-production systems have up-to-date and valid transaction data. This can usually be accomplished by passing a system copy of the production system, created for updates, to the QA system. To reduce the number of test cycles, it is also advisable to update your development system occasionally.
Performing SAP system copies automatically
With the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
The Migration Monitor stores the state of the export or import process in the {ex|im}port_state.properties file.