SAP system copy Pre- and post-processing - SAP Basis

Direkt zum Seiteninhalt
Pre- and post-processing
The system copy
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).

SAP upgrade: Before a very extensive SAP upgrade, you may want to test the run and analyze any errors that occur, especially if the development and test systems are not allowed to be down for too long. In that case, it's best to do this on a system copy.
Automatic determination of delta states after SAP system copy/recovery
If the data stocks become obsolete, they can be updated by another system copy. From a technical point of view, such a refresh corresponds to the initial setup, including the associated costs as well as the load on the productive systems and manual rework. In addition, a refresh also interrupts all processes on the target system. If it is a development system, all newer development objects must be saved and transported back in after the copy. The version history is lost in the process.

In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.

The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.

R3ldctl: New R3ldctl creates two templates: DDLORA.TPL for sorted unloading and DDLORA_LRG.TPL for unsorted unloading.

VMware is suitable for running multiple training, development and test environments on one physical system.
SAP BASIS
Zurück zum Seiteninhalt