SAP system copy Shutting Down the Target System - NW Admin

Direkt zum Seiteninhalt
Shutting Down the Target System
SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
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.

Until now, there has been no functional tool for System i to automate and optimize this task. The enormous resource requirements that arise during a refresh of the SAP QA system really cry out for an optimizing software tool. System Copy from Libelle (LSC) reduces the effort required for these work steps. Although a one-time effort is still required, the system landscape is examined so well that the system copy and any subsequent ones are performed literally at the push of a button. The work that is automated by LSC is in the preparation and post-processing of the files as well as the actual system copy.
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc.

The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.


Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.

SAP system copy is made much easier by the "Shortcut for SAP Systems" application.

The content restriction applies from a certain point in time.

The website www.sap-corner.de offers many useful information about SAP basis.

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.
NW BASIS
Zurück zum Seiteninhalt