Automation tool reduces time required to create test environments
Ways of SAP system copy: export / import
With the entry into force of the GDPR, the topic of system copies has been expanded to include the aspect of anonymization: In many cases, personal or other sensitive data is operated on non-productive systems that usually have lower security levels and also allow access for those persons who are not normally allowed to work with GDPR-relevant data (eg developers or external consultants). For this reason, when defining the processes around system copy and, if necessary, also when selecting tools for automation, care must be taken to ensure that these also map data anonymization in accordance with the GDPR.
Installation continues until the 'Load Data' phase. Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.
Reliable and fast rework after SAP® system copies
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
"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.
In addition to the BDLS statistics, the GUI in the summary log provides a whole range of statistical information about the respective system copy and is also the starting point for more in-depth analyses should an error occur in the copy.
You should also create a delta list for all transports that have not yet reached the production system.