Types of SAP system copy
Key solution steps
Post system copy rework - The collected information from the system copy prework is evaluated and the corresponding transport requests are reimported. The development status before the system copy is thus restored. In addition, this package includes a tool that, when individual transports are released, checks whether there are any overlaps on the target system with transports that are still open there. This prevents a transport from unintentionally "overtaking" an earlier released one with the same objects.
The tools we use can be easily operated either in the cloud or on premise. For this, the SAP systems to be copied must allow access at operating system level. The typical cloud infrastructures, such as AWS or Azure, are not a hurdle for this service.
Ways of SAP system copy: export / import
System copy of a Unicode system: Source and target system are Unicode systems. The same procedures can be used for the copy, as with the copy of non-Unicode systems.
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
On www.sap-corner.de you will also find useful information about SAP basis.
In practice, customers have either built their own tools to make the appropriate configurations, or there are extensive lists of steps to be processed manually.
Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc.