SAP system/instance move
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
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.
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 target system
Against the background of constantly changing business processes, the SAP production systems that serve as the basis for these processes must also be continuously adapted and further developed. To ensure that these processes run smoothly at all times, adaptations and further developments must be comprehensively tested in a non-production SAP system using current production data. Only then can changes be incorporated into the production system. However, updating the databases of non-production SAP systems for testing, quality assurance and development with new production data is usually a time-consuming and error-prone process that involves lengthy interruptions to the SAP software lifecycle. By automating and accelerating SAP data, the workload of IT administrators can be significantly reduced and interruptions to the SAP software lifecycle can be kept to a minimum. This white paper presents a solution that helps shorten SAP refresh cycles based on UC4 process automation integration with HP infrastructure software. This solution can reduce the total cost of ownership (TCO) and the length of the SAP software lifecycle. As a result, business processes can be made more agile, risks can be reduced, and the workload of IT administrators can be reduced. Target audience: SAP technical consultants and IT decision makers who are familiar with commonly used procedures for homogeneous SAP system copies.
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
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.
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level.
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape.