Performing SAP system copies automatically
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
Landscape copies refer to the update of not only one but a whole group of systems. This is the case when dependencies of the source systems are also to be mapped in the target environments. Similar to the simple system copy, the landscape copy also offers potential for automation, but this cannot be implemented by every tool on the market.
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.
Update more efficiently
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.
SAP offers its own solution for this: With the Test Data Migration Server (TDMS), individual tables can be selected and written indirectly, via a third SAP system, from the source to the target system via Remote Function Call (RFC). However, the selection of business objects is not possible in the standard system. The tables to be copied can only be determined on the basis of the date. The content restriction applies from a certain point in time. At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client copy.
From now on, this will be easier. "Shortcut for SAP Systems" contributes to a time-optimized execution of this complex process, no matter when and at what frequency, and while maintaining a high degree of flexibility even in changing environments.
Unsorted unloading: - By default, R3load sorts table data by primary key before export.
Whereby the use of a single point of management and control has also proven its worth.