SAP system copy and the cloud
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
You should also create a delta list for all transports that have not yet reached the production system. Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects. That's why you should take a close look at delta transport lists before proceeding with the upgrade. UC4 Automated System Copy allows you to automate the above steps. If necessary, you can add additional steps without losing testing capabilities.
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.
Possibility of manual intervention in case of delta import
The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
Set up ATM jobs: SE38 (000 client, delete transport setup), redistribute STMS configuration (domain controller).
For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.