Skip to Content

Preparation for System Copy

About this Document

This document provides us information about steps for technical preparation for a System Copy. System Copy (Homogenous & Heterogeneous) is a very interesting and vast topic to be covered when we consider several techniques, tools, databases and platforms,etc. We will look into all details in deep with time. For making it simple we will follow the funnel strategy and will get into deeper knowledge in further documents on this topic.

Preparation for System Copy:

1. Document all the details of the system.

2. Check the kernel patch level of the SAP system. It should be as per SAP recommendation. Kernel patch N-1 should be

applied, where N stands for the latest patch level.

3. Check that JAVA_HOME environment points to a valid JDK version.

4. Check that there are no canceled or pending update requests in the system. You can check this in SM13 transaction code.

Also confirm that VBDATA table does not contain any entries. VBDATA contains the entries of canceled/pending updates.

5. Change the status of all the Released background jobs to Scheduled. This can be done in transaction code SM37. This also

needs to be done for periodical background jobs(refer to SAP Note 16083).

6. Operation modes should be adapted to make sure that no operation mode switching takes place at the time of system copy.

This can be done by transaction SM63.

7. Write down the logical system names of all clients:
Scenario 1-
If the source and target systems will both exist after the system copy), make sure you write down the logical system names of

all clients in the system that will be overwritten (transaction SCC4).
As the logical system names will be overwritten, in the event of differences you must change them back to their original

names (as they existed in the system that is overwritten) in the follow-on actions after the system copy.
Scenario 2-
If you create a new system with a system copy (that is, create an upgrade test system), make sure that the logical naming

strategy for this new system is consistent with your existing logical system naming convention. If you are still planning

your BI (formerly BW) system landscape, refer to SAP Note 184447.
Scenario 3-
If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system

(that is, source system for the copy is the same as the copy target), no changes to logical system names are required.

8. In transaction code SE14, choose Extras –>Invalid temp table. All QCM tables which can be deleted will be displayed. These

tables should be deleted before starting system copy.
Before deleting you must always check
That the tables are consistent – no restart log or conversion procedure termination must be displayed
That the data of the original table can be read
If application programs that use the affected original table do not run correctly, do not delete the QCM table yet.

9. If it is a Heterogeneous system copy (OS/DB Migration) Table TATGPC & TATGPCA are normally empty. But, if these tables

contain any data these should be emptied before starting the export.

10. SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not

found, SAPinst also checks JAVA_HOME. Values of these variables should be set to valid JDK version.

You must be Logged on to comment or reply to a post.
  • Hi Sankar,

    Even though I don't see anything wrong with your suggestions, A blog should be a passage of your own experience on a specific topic. As it stands this in not a blog but a simple checklist. Don't be afraid to put your own touch into it, describe your experiences and opinion in a relaxed way.

    Regards, Juan

    • Hi Juan,

         Thanks for your valuable suggession. I will surely become more familiar to SCN and will start sharing experiences and learnings soon.