TM-TMS (Transport Manager)
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
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. This approach is time-consuming and error-prone.
SAP system copy and the cloud
Table splitting requires 2 tools: R3ta, which determines the WHERE conditions used to access subsets of a table. TableSplitter, which splits the WHERE-conditions determined by R3ta into packages with one or more subsets.
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
And last, but not least, such tools must allow for extensibility or enable customer-specific extensions/requirements, such as integration into a scheduler or consideration of SAP double-stack systems.
Open transport requests that should survive the system copy (maintain development status).