Ways of SAP system copy: export / import
SAP system startup and shutdown, including virtual hosts
The demands on your business are constantly changing. For this reason, there is also a need to adapt processes and functionalities. This cannot be done directly in the production system, but must first be extensively tested, which in turn requires data that is as realistic as possible. The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential. We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies. We are also happy to support you with any data anonymization that may become necessary after such a copy.
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.
The Refresh
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.
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems. This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy). Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
Scenario: We assume that a new training system will be created from the productive system.
In addition, testing is complicated by the growing complexity of applications and IT architecture.