This is why companies need professional test data management
Scenario with system copies for updating
There are various ways to tame this time robber and reduce run times. For example, through parallelization or the automatic generation of secondary indices.
As a rule, the SAP basis has to fulfill: to provide SAP system copies as quickly as possible for the increased usage purposes. The performance of modern tools has developed rapidly. An assessment of the current situation.
What is System Copy as a Service?
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
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.
With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.
These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes.
There are now a number of tools that simplify refresh activities of non-production SAP systems.