System copy prerequisite

Procedure
1. Before you s tart a system copy, check the minimum kernel patch level required
by the support package level
of the source system.
It might be necessary to replace the SAP kernel delivered with the installation kit
and installed during the
installation of the target system by a newer kernel patch level before s tarting the
target system. If you have to
replace the delivered SAP kernel, you can do this after the installation of the primary
application server instance.
For more information about release and roadmap information around the kernel
versions and their relationship
to SAP NetWeaver s upport packages including important notes on downward
compatibility and releas e dates ,
2. Check if canceled or pending update requests exist in the system. If canceled or
pending updates exist, you
must update these again or delete them from all clients. Proceed as follows:
1. Call trans action SM13.
2. Delete the default values for the client, user, and time.
3. Choose all update requests .
4. Check if table VBDATA contains any entries. If there are entries, update or delete
the corresponding update
reques ts.
5. To check whether this action was succes s ful, call transaction SE16 for table
VBDATA.
3. Set all released jobs from Releas ed to Scheduled us ing transaction SM37.
You a ls o need to do this for jobs that mus t run periodically. For m ore information,
s ee SAP Not e 16 0 83.
To s elect all jobs (include start after event), choose Job Released Scheduled
4. Adapt the operation mode timetable to make sure that no switching of operating
modes takes place while a
system is being copied (transaction SM63).
5. Write down the logical s ys tem names of all clients :
If you plan to overwrite an existing system with a system copy, make sure you
write down the logical system
names of all clients in the s ys tem that will be overwritten (trans action SCC4).
Since the logical s ys tem names will be overwritten, in the event of differences ,
you m us t change them back
to their original names (as they existed in the system that is overwritten) in the
follow-on actions after the
sys tem copy.
If you create a new system with a system copy (for example, create an upgrade
test system), make sure
that the logica l naming s trategy for this new sys tem is cons is tent with your exis
ting logical s ys tem naming
convention.
SAP Bus ines s Warehous e (BW) only: If you a re s till in the proces s of planning
your BW sys tem landscape,

see SAP Note 184447 for information about how to set up your system landscape,
especially for information
about s ys tem naming.
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.
6. Before you run the export and after you have performed several checks , delete
QCM tables on the source system.
Proceed as follows:
1. Before you delete the QCM tables, ensure the following:
The tables are consistent no restart log or conversion procedure termination
must be displayed.
The data of the original table can be read.
Application programs that use the affected original table run correctly.
2. Call trans action SE14.
3. Choose Extras Invalid temp. table
All QCM tables that can be deleted are displayed.
4. Mark the tables and delete them.
7. To avoid s topping the database due to a log directory being full, m ake sure that
the log backup is enabled during
the import.
8. Apply SAP Note 13456 0 0 .
SAP Sys tems Based on the Application Server ABAP of SAP NetWeaver on UNIX

Product -Specific Preparations

Procedure
FI Customers
You can perform an additional consistency check by running the job
SAPF190 before copying the source system,
as well as after copying the target system, and then compare the results.
Make sure that no customer data is
changed in the meantime. You can do this as follows:
In trans action SAPF190, for classic FI, choose Accounting Financial
Accounting General ledger Periodic
Processing Closing Check/ count Reconciliation .
For a new general ledger, choose Accounting Financial Accounting General
ledger Periodic
Processing Closing Check/ count Reconciliation (New) .
You can further check consistency by running the jobs listed below before
copying the source system, as well
as after copying the target system, and then compare the results.
RFUMSV00 (tax on sales / purchases)
RAGITT01 (asset his tory sheet)
RAZUGA01 (asset acquisitions )
RAABGA01 (fixed asset retirements)

Make sure that no customer data is changed in the meantime.

CO Customers
You can perform an additional consistency check by running the report group
1SIP before copying the source
system, as well as after copying the target system, and then compare the
results. Make sure that no customer data
is changed in the meantime.

Caution

Prerequisites for an export:

Before performing an export, make sure that no incremental conversion is in
progress .
To test if an incremental conversion is in progress , run trans action ICNV. If
there are any table entries in table
TICNV, an incremental conversion is in progress . In this case, you have the
following options :
1. Defer the migration until the incremental conversion has finished.
2. Try to finish the incremental conversion by performing the following steps:
If the tables are in state For conversion or in state Done, delete the entries
by choosing Control Delete
Entry .
If the tables are in any other state, you have to finish the incremental
conversion. Choose Assistant and proceed
according to the online documentation.

Caution

Heterogeneous system copy only:

Before you s tart the export of your source system, make sure that the tables
TATGPC and TATGPCA are empty.
To do s o, us e your database utility and delete the contents of these tables
with the following statements :
DELETE from TATGPC
24
CUSTOMER
Copyright 20 14 SAP AG.
All rights reserved.
SAP Systems Based on the Application Server ABAP of SAP Net Weaver on UNIX
Preparations

DELETE from TATGPCA

If the tables are not empty and you do not delete the contents of these
tables you encounter problems while
importing the data to your target system because of non-NULL capable fields
in these tables.

SAP Business Warehouse

When planning the copy of an SAP Business Warehouse (BW) system, read
SAP Notes 88610 2 and 170 7321.