SAP system copy This is why companies need professional test data management - SAP Basis

Direkt zum Seiteninhalt
This is why companies need professional test data management
Update more efficiently
Companies with backup systems can use these for a client copy and thus save on the computing power of the productive system. However, the burden of copying falls on the SAN. Because the reliability is limited by the misuse of the backup system and the storage network is additionally burdened, users should keep the runtime of this refresh variant as short as possible.

Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example. This means that you have all production data available on your test system in a short time.
Planning Guide for the Connector for SAP Landscape Management
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.

If the data stocks become obsolete, they can be updated by another system copy. From a technical point of view, such a refresh corresponds to the initial setup, including the associated costs as well as the load on the productive systems and manual rework. In addition, a refresh also interrupts all processes on the target system. If it is a development system, all newer development objects must be saved and transported back in after the copy. The version history is lost in the process.

Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.

But it can be even more comfortable.

The groups are defined in the same file where the order of the packages is defined.
SAP BASIS
Zurück zum Seiteninhalt