Types of SAP system copy
Create SAP HANA system replication levels
Transaction IMIG comes with extensive online documentation. It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
For companies, however, professional test data management is not only interesting for optimizing existing systems and processes particularly securely and quickly. With such a solution, they are also able to simulate the effects of serious changes even before the actual transformation. This can be extremely profitable, for example, for the conversion of existing ERP systems to the new SAP Business Suite S/4HANA. Decision-makers are thus able to successfully circumvent any transformation risks and define a roadmap for a smooth process.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
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.
Of course, time savings also mean money savings. In addition, these processes for system copying can be planned, standardized and always run at a high level of process quality using automation tools of this kind. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers). With "Shortcut for SAP Systems", a number of activities in the context of system copies can be carried out and automated. Your SAP Basis administration is thus significantly relieved. Automation also means that SAP Basis Administrators no longer have to work unreasonable hours. The product can be integrated into almost any automation software.
The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.