SAP system copy Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy - SAP Basis

Direkt zum Seiteninhalt
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
Differentiation between homogeneous and heterogeneous SAP system copy
Table splitting requires 2 tools: R3ta, which determines the WHERE conditions used to access subsets of a table. TableSplitter, which splits the WHERE-conditions determined by R3ta into packages with one or more subsets.

The different types of SAP environments must meet different requirements. Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system. Companies can simulate real-life situations for testing purposes on the basis of consistent and realistic data alone. Users should also test their own developments and modifications with consistent data that is close to production. A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades. In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.
Several advantages at once
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.

With the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.

With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.

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.

Unicode conversion: A Unicode target system is built from a non-Unicode source system.
Zurück zum Seiteninhalt