We take over your SAP system copies as a service
Copying needs to be done skillfully
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.
The professional handling of test data is also important with regard to applicable data protection and compliance guidelines. Global companies in particular are required to take measures to protect sensitive data. They need to ensure compliance and reduce risks from data breaches, even in non-productive environments. Innovative test data management can protect data from internal and external misuse through encryption, among other things. Sensitive personal data is secured in accordance with current data protection requirements, while at the same time high test quality is achieved through realistic data.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
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.
One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
Cleanup of target system database contents - removal of source system specific database contents to allow the target system to boot without disrupting production processes.
Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects.