SAP system copy Test and training system: data anomyization, migration of master data, migration of user data / passwords - SAP Stuff

Direkt zum Seiteninhalt
Test and training system: data anomyization, migration of master data, migration of user data / passwords
Update more efficiently
Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.

By using the automation solution, errors that typically occur with manual process steps - just like additional costs due to repetition - can be avoided. To date, the IT team has created 88 SAP system copies. "If we had wanted to do this with SAP board resources, we would not have been able to pay for it as a medium-sized company," Rudi Scharf knows.
Possibility of manual intervention in case of delta import
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 "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.


For example, when it comes to creating system copies of a production environment on the test and quality assurance (QA) system.

SAP Stuff
Zurück zum Seiteninhalt