Reliable and fast rework after SAP® system copies
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
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.
Hybrid: for example, the source systems on-premises and the target systems on cloud
The suite idea has established itself here as well as in many other software areas. And for good reasons. In addition, such automation tools are moving even more strongly in the direction of the IT topic of system management.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Without interrupting operations, we copy your systems using established methods and products. We guarantee consistent quality and reliable reproducibility through standardized processes and a high degree of automation. Due to the SAP system copy, the test and development systems are up to date and tests can be performed reliably and trustworthily on the non-production systems.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
Users do not have to deal with individual tables, but can access a database of business entities.
Since these names usually need to be passed to numerous tables in a given system that have not yet been customized, SAP has the BDLS transaction that can be used to safely analyze and change logical system names.