Automate SAP system copies
SAP system/instance move
The third-party providers have adapted their tools to various special areas. For example, the "Clone & Test" tool from Pecaso, which is now part of Accenture, specializes in transferring data from SAP's HR module. In addition to HR data, the "Data Sync Manager" from the provider Epi-Use makes it possible to select additional objects from the areas of accounting and logistics. As with TDMS, "Infoshuttle" from Gamma Enterprise Technologies gives users the option of selecting any data from the SAP system. For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data. SNP's "Data Distillery" can either write extracted data directly into the tables of the target system via RFC or generate an export file that can be imported into target systems multiple times. In the source system, users can select by objects, processes and transactions. Further selection options, for example by organizational units or fiscal year, allow a percentage of the data to be filtered out of the system as consistent test data.
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.
Pre- and post-processing
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
SAP environments can quickly become time-consuming. For example, when it comes to creating system copies of a production environment on the test and quality assurance (QA) system. Because of the time required, some QA systems turn out to be outdated and thus even ticking time bombs. A software tool from Libelle now makes it easier to update QA systems in SAP architectures on System i as well.
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!
In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Target system installation can start after 'Prepare Export' has run.