Scope of the SAP system copy
Automatic determination of delta states after SAP system copy/recovery
Especially in complex environments, SAP system copies regularly represent a critical challenge in terms of time and expertise and thus become a real cost factor in the long run. This is because system copies must be scheduled at an early stage, are complex, time-consuming and resource-intensive, require specific knowledge, tie up important employee capacities due to the large number of manual interventions, and are error-prone.
The suite idea has established itself here as well as in many other software areas. And for good reasons. In addition, such automation tools are moving even more strongly in the direction of the IT topic of system management.
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems. This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy). Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.
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!
The status of the target system now allows it to run without severe internal errors and disruption to the SAP landscape.
If the data stocks become obsolete, they can be updated by another system copy.