Automatic determination of delta states after SAP system copy/recovery
Planning Guide for the Connector for SAP Landscape Management
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
The different types of SAP environments must meet different requirements. Training courses, for example, can only be held expediently if the working conditions largely correspond to those on the production system. Companies can simulate real-life situations for testing purposes on the basis of consistent and realistic data alone. Users should also test their own developments and modifications with consistent data that is close to production. A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades. In development and training systems in particular, it is fundamentally important to anonymize sensitive data in order to comply with data protection rules.
Pre- and post-processing
The professional handling of test data is also important with regard to applicable data protection and compliance guidelines. Global companies in particular are required to take measures to protect sensitive data. They need to ensure compliance and reduce risks from data breaches, even in non-productive environments. Innovative test data management can protect data from internal and external misuse through encryption, among other things. Sensitive personal data is secured in accordance with current data protection requirements, while at the same time high test quality is achieved through realistic data.
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.
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.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!
However, updating the databases of non-production SAP systems for testing, quality assurance and development with new production data is usually a time-consuming and error-prone process that involves lengthy interruptions to the SAP software lifecycle.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
An SAP system copy is a process in which an exact copy of an existing SAP system is created.