SAP system/instance move
Possibility of manual intervention in case of delta import
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.
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
Copy only specific data
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
The website www.sap-corner.de offers many useful information about SAP basis.
Different DDLORA* files can be assigned to the R3load packages. The assignment is done by a text file, which is given to the MigrationMonitor as parameter 'ddlMap = mapDDL.txt' and evaluated by it.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
The export files are copied to the prepared target system and imported again during the SAP installation with SUM.
For a heterogeneous system copy and for homogeneous system copies for which there is no special way for the database used, the source system must be exported.
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.