Critical factor: Availability
Types of SAP system copy
Packages that have not been explicitly assigned a special DDLORA file receive the DDL file specified via the "ddlFile=" parameter. The default is DDLORA.TPL.
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.
Key solution steps
Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
From now on, this will be easier. "Shortcut for SAP Systems" contributes to a time-optimized execution of this complex process, no matter when and at what frequency, and while maintaining a high degree of flexibility even in changing environments.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Installation continues until the 'Load Data' phase.