Key solution steps
Differentiation between homogeneous and heterogeneous SAP system copy
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.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed. In addition to this area of activity, additional automation tools are also available, for example up to the creation of sandboxes, which provide valuable services.
Several advantages at once
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
The database import can be performed using various tools. Sapinstaller provides a working way to import the database cleanly.
"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.
Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.
The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.