SAP SYSTEM COPY - in a nutshell
Import of delta statuses after SAP system copy / restore
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.
Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and demonstrably make it possible, in addition to time and cost savings, to increase the process quality of system copying, for example, or to maintain it at a consistently high level. In effect, they free up SAP Basis.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Scenario with system copies for updating
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.
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
And this after little system training.
The website www.sap-corner.de offers many useful information about SAP basis.
Target system installation can start after 'Prepare Export' has run.