Hybrid: for example, the source systems on-premises and the target systems on cloud
Performing SAP system copies automatically
You can manage your SAP system landscape in Google Cloud with SAP Landscape Management, Enterprise Edition (SAP Landscape Management) by installing the Google Cloud Connector for SAP Landscape Management (Connector for LaMa). Google Cloud provides the Connector for LaMa free of charge. You must purchase all required licenses for SAP Landscape Management from SAP.
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.
Purpose of the SAP system copy
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed. In addition to this area of activity, additional automation tools are also available, for example up to the creation of sandboxes, which provide valuable services.
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level. Costs and effort increase with the size of the system and the requirements for availability and data protection. In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.
"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.
In addition, this package includes a tool that, when individual transports are released, checks whether there are any overlaps on the target system with transports that are still open there.
Logical system names must also be converted (using the BDLS trasaction code).