Technical system copy for the upgrade
Tools for SAP test systems
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like. The use of a comprehensive dashboard will then also be included.
Key solution steps
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market. It is not unusual for them to have to introduce new processes and projects particularly quickly and securely for the benefit of their own competitiveness. At the same time, their system landscapes are becoming increasingly complex due to mergers and acquisitions and the use of new technologies.
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
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.