Solution Description
We take over your SAP system copies as a service
Installation continues until the 'Load Data' phase. Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.
Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments. A three-tier SAP landscape typically consists of development, test and production systems. In addition, there are often training systems.
Types of SAP system copy
Different DDLORA* files can be assigned to the R3load packages. The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.
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.
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!
Acceleration/table export: up to 4 times faster.
However, updating the databases of non-production SAP systems for testing, quality assurance and development with new production data is usually a time-consuming and error-prone process that involves lengthy interruptions to the SAP software lifecycle.