SAP system copy Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox) - SAP Corner

Direkt zum Seiteninhalt
Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox)
The Refresh
Advantage of the system copy: Users receive one hundred percent consistent test data. A disadvantage, however, is the high storage space requirement of such a test system, which corresponds to that of the productive system. In addition, an authorization concept for the system copy is required to protect the authentic data it contains. Otherwise, company secrets are at risk, and there is a violation of regulations such as the Federal Data Protection Act and the Sarbanes-Oxley Act.

There are now a number of tools that simplify refresh activities of non-production SAP systems. The tools are imported into SAP systems via transports and enable the data to be copied to be written in. The more precise the selection, the greater the potential savings in storage space and extraction time compared to client copy. As with the latter, the configuration is retained and ongoing development and test processes remain undisturbed.
Before shutting down the target system
The different types of SAP environments must meet different requirements. Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system. Companies can simulate real-life situations for testing purposes on the basis of consistent and realistic data alone. Users should also test their own developments and modifications with consistent data that is close to production. A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades. In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.

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.

There is a useful product for SAP system copy - "Shortcut for SAP Systems".

In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system.

On you will also find useful information about SAP basis.

Production system downtime depends primarily on the method you use to create the image of the production data to be used in the target system.
SAP Corner
Zurück zum Seiteninhalt