The target system
Possibility of manual intervention in case of delta import
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system. However, many settings in the test system must be retained, because a test system should not act like a production system and, for example, send documents to customers and suppliers or trigger something in production.
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.
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
System copy of a Unicode system: Source and target system are Unicode systems. The same procedures can be used for the copy, as with the copy of non-Unicode systems.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the appropriate updates to the production system as SAP transports.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
Tests are already worthwhile for the introduction of SAP solutions in the company and also for release upgrades and migration projects, the import of patches, customizing, modifications and in-house developments.
The existing installation was expanded to include the module for creating SAP system copies.