Performing SAP system copies automatically
Homogeneous system copy: In this type of copy, the operating system and database on the target system are the same as on the source system. So Windows remains Windows and Linux remains Linux. And if the SAPHana database is running on the source system, it will also be used on the target system.
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.
Types of SAP system copy
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Transaction IMIG comes with extensive online documentation. It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users.
Users should also test their own developments and modifications with consistent data that is close to production.