Purpose of the SAP system copy
Downtime
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 the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
Technical system copy for the upgrade
Users do not have to deal with individual tables, but can access a database of business entities. This means that they do not select tables, but business objects such as employees or documents. To do this, however, the tools must contain the object dependencies for SAP's complex data model. Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset. In addition, users can define objects themselves to accommodate customizing and in-house developments.
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.
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.
They need to ensure compliance and reduce risks from data breaches, even in non-productive environments.
Some useful tips about SAP basis can be found on www.sap-corner.de.
After the above requirements are met, the target SAP and database instances can be shut down to create the technical system copy for the upgrade.