Detailed checks for critical order contents
Pre- and post-processing
Unicode conversion: During the copy, the system is converted from non-Unicode to Unicode. This happens in the context of a homogeneous or heterogeneous system copy. In connection with Unicode must be differentiated between the system copy of a Unicode system and the Unicode conversion.
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.
Shutting Down the Target System
Of course, time savings also mean money savings. In addition, these processes for system copying using such automation tools can be planned, standardized and always run at a high level of process quality. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers).
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
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.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
There are two types to be distinguished: homogeneous and heterogeneous system copy and one can get to the system copy in different ways.
One of these acts as a backup system.