SAP Landscape Copies
Automation of homogeneous SAP system copies
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.
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.
Applicability of Systemcopy as a Service
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.
There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
Unsorted unloading: - By default, R3load sorts table data by primary key before export.
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system.