SAP system copy Test and training system: data anomyization, migration of master data, migration of user data / passwords - SAP Basis

Direkt zum Seiteninhalt
Test and training system: data anomyization, migration of master data, migration of user data / passwords
SAP system copy and the cloud
While homogeneous SAP system copy expects identical combinations of operating/database systems on the source and target systems, there is also a requirement for different combinations of operating/database systems on the source and target systems in the project environment (eg, during migrations). This is referred to as a "heterogeneous SAP system copy". Technically, it is quite possible to build up a degree of automation here as well, but officially certified consultants ("migration consultants") are required to perform the heterogeneous system copy.

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.
Automation tool reduces time required to create test environments
SAP production system copies are created for a variety of reasons, including: - Generating a new non-production system for short- or long-term use - Updating an existing non-production system An SAP system copy is called homogeneous if the source and target operating and database systems are identical. If this is not the case, the system copy is considered heterogeneous. Heterogeneous system copies or platform migrations are not supported by the HP StorageWorks System Copy software for SAP and are therefore not discussed further in this document. In addition, this document deals exclusively with system copies for non-production target systems. Overview of a homogeneous system copy Figure 1 shows copies of an SAP production system that are created for non-production systems. Some copies are short-term (ad hoc) in nature, while others are intended for long-term use. Note that when a long-term system is created from a system copy, a system copy may be needed for updates later in the system's life cycle. This adds the latest transactional data from the original production system. Given their particular importance, this document focuses on scenarios with system copies created for updates. Figure 1: Overview of scenarios with homogeneous SAP system copies Scenario with system copies for updates In order to meet constantly 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 production system with the appropriate updates as SAP transports.

Increasingly, ad hoc requests are coming from IT or SAP Basis to provide an SAP system copy as quickly as possible, for example of an SAP ERP, BW or HCM system. This often leads to special challenges due to a lack of resources or capacities.

Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and, in addition to time and cost savings, demonstrably also make it possible, for example, to increase the process quality in system copying or to maintain it at a consistently high level. In effect, they free up SAP Basis. With "Shortcut for SAP Systems", you can sustainably relieve your administrators of the time-consuming routine activities of an SAP system copy.

Development and test work then takes place on a QA system that does not correspond to the production system.

The test environment will then be missing audit documents, among other things, but the development objects will remain untouched.
Zurück zum Seiteninhalt