Solution infrastructure
Efficient options for SAP system copies
In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually. This approach is time-consuming and error-prone.
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.
Challenges with SAP system copies
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.
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.
You should also create a delta list for all transports that have not yet reached the production system. Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects. That's why you should take a close look at delta transport lists before proceeding with the upgrade. UC4 Automated System Copy allows you to automate the above steps. If necessary, you can add additional steps without losing testing capabilities.
"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.
Some copies are short-term (ad hoc) in nature, while others are intended for long-term use.
The website www.sap-corner.de offers many useful information about SAP basis.
Installation continues until the 'Load Data' phase.