SAP system deployment scenarios
SAP system copies and the DSGVO
After restarting the target system The SAP target instance has been started with a database that has been updated with content copied from the production database using fast and scalable disk array replication. The status of the target system now allows it to run without severe internal errors and disruption to the SAP landscape. However, the system does not have the same identity in the SAP landscape as it had before the update. That's why post-processing is required. UC4 Automated System Copy can handle most of the post-processing by restoring specific database content customizations (such as security settings, RFC targets, and operating modes) that were downloaded before the upgrade. Another goal in post-processing is to change the production system's logical system names to those used by the target system. Since these names usually need to be passed to numerous tables in a given system that have not yet been customized, SAP has the BDLS transaction that can be used to safely analyze and change logical system names. UC4 Automated System Copy can automate and accelerate this transaction by analyzing the underlying processes and executing them in parallel. It can also automate tasks such as reorganizing spools and instructing transport managers to process the delta transport list.
Over 30 productive systems at more than 9 customers successfully copied using IMIG. For the Unicode conversion of a 4.5 TB system (2.7 TB data) a downtime of 16 hours was achieved (including the follow-up work such as reconfiguration, updating DB statistics, generating reports, creating backups, testing the system).
On-premises: all involved source/target systems in the company's own data centers
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
SAP software plays a central role in the IT landscape of Rehau, a provider of polymer-based solutions for construction, automotive and industry. Currently, the IT department provides over 120 SAP systems centrally in the sense of "shared service hosting". The IT team must regularly copy the SAP productive environment in order to be able to carry out testing and development work on the "real" system without manipulating the productive systems. Rehau recently opted for the 'Automated System Copy for SAP' solution. The tool from Automic, a specialist in business automation, allows SAP system copies to be created almost fully automatically.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
However, the selection of business objects is not possible in the standard system.