Solution infrastructure
Scenario with system copies for updating
Provide your QA, test and training systems with current production data at the push of a button. Including all preparatory and finishing work - Without interfering with or changing your SAP environment - Without time-consuming pre-planning - With minimum lead time - With consistent copy quality.
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
SAP system copies and the DSGVO
The process of creating system copies for updates can be broken down into different activities, as shown in Table 1. For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy. All these activity groups are described individually below.
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.
With "Shortcut for SAP Systems", a mature and yet very cost-effective product is available that offers useful functions for system copies. For example, SAP system users can be backed up and restored. Likewise, system-specific tables can be backed up before the system copy and restored after the system copy. And all this can also be automated.
Otherwise, company secrets are at risk, and there is a violation of regulations such as the Federal Data Protection Act and the Sarbanes-Oxley Act.
The IMIG system copy (Incremental Migration) is an alternative if: - The system is very large or is large and contains a few very large tables and many smaller tables - An acceptable downtime cannot be achieved using conventional methods.