Scenario with system copies for updating
Solution Description
There are various ways to tame this time robber and reduce run times. For example, through parallelization or the automatic generation of secondary indices.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
SAP system copy and the cloud
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.
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.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
This can be extremely profitable, for example, for the conversion of existing ERP systems to the new SAP Business Suite S/4HANA.
The most common update scenario involves updating a QA system in the SAP transport system.