SAP system copy Scope of the SAP system copy - SAP Stuff

Direkt zum Seiteninhalt
Scope of the SAP system copy
Automation of homogeneous SAP system copies
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. This is done with SAP tools (SUM). The export files are copied to the prepared target system and imported again during the SAP installation with SUM. A relatively comfortable way. But it can be even more comfortable.

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.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.

With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.


Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects.

SAP Stuff
Zurück zum Seiteninhalt