SAP system deployment scenarios
Ways of SAP system copy: export / import
Provide your QA, test and training systems with current production data at the push of a button. Including all preparatory and finishing work - Without interfering with or changing your SAP environment - Without time-consuming pre-planning - With minimum lead time - With consistent copy quality.
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.
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.
Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup. These tools allow you to create a complete copy of the database as well as a copy of the file system. However, it is important to note that special knowledge is required when using these tools to ensure that the backup is created correctly.
"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.
The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.
This can usually be accomplished by passing a system copy of the production system, created for updates, to the QA system.