Conclusion
Efficient options for SAP system copies
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
Post system copy rework - The collected information from the system copy prework is evaluated and the corresponding transport requests are reimported. The development status before the system copy is thus restored. In addition, this package includes a tool that, when individual transports are released, checks whether there are any overlaps on the target system with transports that are still open there. This prevents a transport from unintentionally "overtaking" an earlier released one with the same objects.
Reliable and fast rework after SAP® system copies
As mentioned above, an SAP system copy created for updates is a special use case of homogeneous system copy. Here, a production system represents the source and a non-production system with a specific long-term task in the SAP system landscape represents the target. The most common update scenario involves updating a QA system in the SAP transport system.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.
A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.
This solution can reduce the total cost of ownership (TCO) and the length of the SAP software lifecycle.
On www.sap-corner.de you will also find useful information about SAP basis.
At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client copy.