Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Reliable and fast rework after SAP® system copies
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
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.
With the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.
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!
Because of the time required, some QA systems turn out to be outdated and thus even ticking time bombs.
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export.