SAP system copy Scope of the SAP system copy - SAP Basis

Direkt zum Seiteninhalt
Scope of the SAP system copy
Job logic instead of customizing
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.

With the entry into force of the GDPR, the topic of system copies has been expanded to include the aspect of anonymization: In many cases, personal or other sensitive data is operated on non-productive systems that usually have lower security levels and also allow access for those persons who are not normally allowed to work with GDPR-relevant data (eg developers or external consultants). For this reason, when defining the processes around system copy and, if necessary, also when selecting tools for automation, care must be taken to ensure that these also map data anonymization in accordance with the GDPR.
Planning Guide for the Connector for SAP Landscape Management
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system. However, many settings in the test system must be retained, because a test system should not act like a production system and, for example, send documents to customers and suppliers or trigger something in production.

Table splitting reduces the risk of losing a lot of time during export in case of an error. When restarting, the complete table does not have to be exported again, but only a subset. Simultaneous processing of a table by several R3load processes can reduce the total runtime for this table.

With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.

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

On www.sap-corner.de you will also find useful information about SAP basis.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.

If necessary, you can add additional steps without losing testing capabilities.
SAP BASIS
Zurück zum Seiteninhalt