SAP system copy Possibility of manual intervention in case of delta import - SAP Basis

Direkt zum Seiteninhalt
Possibility of manual intervention in case of delta import
SAP system copies and the DSGVO
The solution described in this document can be summarized as follows: The goal is to create a homogeneous copy of an SAP system. The source of the system copy is a production system. The target of the system copy is an existing non-production system. The focus is on a specific use case, a system copy created for updates. Backup and restore are performed at the SAN device level and supported by HP System Copy software. Pre- and post-processing is automated using the UC4 Automated System Copy for SAP solution. Thus, the proposed solution allows you to optimize the automation and acceleration of SAP system copies generated for upgrades and reduce IT administration costs. Automated, fast and powerful upgrade capabilities enable shorter and more flexible SAP software lifecycles, enabling more agile business processes.

Landscape copies refer to the update of not only one but a whole group of systems. This is the case when dependencies of the source systems are also to be mapped in the target environments. Similar to the simple system copy, the landscape copy also offers potential for automation, but this cannot be implemented by every tool on the market.
Automation tool reduces time required to create test environments
Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!

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.

The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.

Primarily for security reasons, no changes to SAP source systems are enabled.

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.
SAP BASIS
Zurück zum Seiteninhalt