Running System Copy GT on a new system

When you are about to use System Copy GT on a system where it has not been run before you should take yourself back through the process.

• Ensure that you have a license key and the correct transports installed if you need to request a license key remember to supply the 10 digit SAP installation number to support so the key can be generated

• Double check the prerequisites are all in place as the new system may have a different setup

• As per the other systems you have worked with check the 5 largest tables in the system (by size in rows) along with any other tables you are aware of presenting challenges in that system. Check if these tables require conversion, do they have a logical system name to be converted, if they do have are there actual entries to be converted? If no entries need to be converted these tables should be excluded via the SAP standard table BDLSEXZ using SM30 and add an entry with class ‘T Excluded Table’ and object name of the table to exclude (further details are found in OSS note 932032)

• Check if multiple logical system name updates are required, if so you will need to consider these on the selection screen and you may wish to exclude large tables from some logical system names

• Consider the current duration of conversion run under standard BDLS for this system as it may be longer than your other systems

After considering all of the details above ideally, run a test run on a recent copy of the system, this gives you details to tune the run, details on that are here.