Efficient options for SAP system copies
SAP system deployment scenarios
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the appropriate updates to the production system as SAP transports.
Hybrid: for example, the source systems on-premises and the target systems on cloud
SAP SE is a software company that uses the proprietary programming language ABAP. SAP® landscapes include not only production but also Quality Assurance (QA) systems as well as test and other staging systems. For appropriate and consistent testing and acceptance of changes in programs and processes, SAP recommends the "homogeneous system copy" approach to provide non-production systems with up-to-date data.
With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!
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.