SAP system copy SAP system update and database update - SAP Basis

Direkt zum Seiteninhalt
SAP system update and database update
Pre- and post-processing
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.

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.
Challenges reduced!
An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.

Such system copies, with their enormous manual effort and SAP checklists that are often hundreds of items long, must be performed before every refresh. Usually, three to four days have to be planned for this, during which the QA system - which in two-tier SAP environments is also the development system - is not available for the actual work. The delay is actually only caused by the meticulous matching of trivial things, such as directory names. Because such SAP system copies have to be created for each SAP application on the QA system and can thus quickly require dozens of system copies, they tie up a lot of resources and staff.

Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.

For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.

It can also be used to export certain data from the database and import it into another system.
SAP BASIS
Zurück zum Seiteninhalt