SAP system copy TM-TMS (Transport Manager)

Direkt zum Seiteninhalt
TM-TMS (Transport Manager)
SAP system deployment scenarios
Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.

The process of creating system copies for updates can be broken down into different activities, as shown in Table 1. For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy. All these activity groups are described individually below.
Planning Guide for the Connector for SAP Landscape Management
Unicode conversion: During the copy, the system is converted from non-Unicode to Unicode. This happens in the context of a homogeneous or heterogeneous system copy. In connection with Unicode must be differentiated between the system copy of a Unicode system and the Unicode conversion.

Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.

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

In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.

Costs and effort increase with the size of the system and the requirements for availability and data protection.
SAP Corner
Zurück zum Seiteninhalt