SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
Critical factor: Availability
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users. Cross-user developments are processed in one package, ensuring consistency. The entire process consists of three areas.
SAP system/instance move
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.
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying.
That's why you should take a close look at delta transport lists before proceeding with the upgrade.