Ways of SAP system copy: export / import
Scope of the 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.
An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.
Challenges with SAP system copies
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
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 respective owners of the transports have the possibility to discard an obsolete development.
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.