Efficient options for SAP system copies
Scenario with system copies for updating
A major risk to the availability of the entire SAP environment arises when system copies are not transferred to the QA system for reasons of time and resources. Development and test work then takes place on a QA system that does not correspond to the production system. The disruption of the production system - sooner or later - is then already pre-programmed.
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
Several advantages at once
Users do not have to deal with individual tables, but can access a database of business entities. This means that they do not select tables, but business objects such as employees or documents. To do this, however, the tools must contain the object dependencies for SAP's complex data model. Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset. In addition, users can define objects themselves to accommodate customizing and in-house developments.
Also of increasing relevance to companies is the rapid provision of test data or systems in different data centers or in the cloud. A modern test data solution can implement these requirements in a largely automated manner, reducing manual effort, lowering the susceptibility to errors, and saving time and money.
With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!
S/4HANA migration: The migration to S/4HANA is always done via an SAP system copy, if one does not start anew on a "greenfield".
Some useful tips about SAP basis can be found on www.sap-corner.de.
This guide does not provide instructions for installing, configuring, or operating SAP Landscape Management.