Scenario with system copies for updating
Key solution steps
Partial copies from SAP systems with the help of tools open up potential savings and in many cases make system copies and complete client copies superfluous. The ability to anonymize data reduces the effort required to comply with data protection regulations in training systems, for example. In addition, up-to-date, consistent test data improves the flexibility and quality of development and test environments. Users save money through reduced resource requirements.
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users. Cross-user developments are processed in one package, ensuring consistency. The entire process consists of three areas.
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.
Easy integration also in the system copy of systems of older releases possible!
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.
In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.
"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists.
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.
For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.