SAP system copy Challenges with SAP system copies

Direkt zum Seiteninhalt
Challenges with SAP system copies
SAP system deployment scenarios
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).

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 SYSTEM COPY - A BEFORE AND AFTER GUIDE
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.

The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.

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.

The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.

What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.

Some examples of selectable settings of the target system that can be copied automatically: RFC connections and certificates, report variants of the target system, logical paths of the target system, setup of the transport system, ABAP version management, system profiles and operation modes, background jobs, users and roles, settings of SAPConnect, ALE settings, texts of the login screen, developer and object keys, takeover of spool servers, logical systems, other settings, as well as a re-import of transports into the target system, are possible after consultation.
SAP Corner
Zurück zum Seiteninhalt