SAP system copy Job logic instead of customizing - SAP Corner

Direkt zum Seiteninhalt
Job logic instead of customizing
Copy only specific data
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.

Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array. Regardless of the storage size, this process takes only a few seconds.
TM-TMS (Transport Manager)
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.

An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.

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.

In this context, a focus on a problem called BDLS (conversion of logical system names): When using the Empirius tool, BDLS is only executed for tables that have not been saved (these have already been converted and would produce a warning message).

If you want to get more information about SAP basis, visit the website

By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.
SAP Corner
Zurück zum Seiteninhalt