0% found this document useful (0 votes)
271 views20 pages

Sap New Client Copy Tools by Mayur Pimpalkar

The document discusses SAP's New Client Copy tool which is used to copy client data from one system to another. It describes the different phases and screens of the client copy process, provides tips on optimizing runtime and monitoring tables copied, and lists various transaction codes and reports related to client copying.

Uploaded by

nehra.raman07
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
271 views20 pages

Sap New Client Copy Tools by Mayur Pimpalkar

The document discusses SAP's New Client Copy tool which is used to copy client data from one system to another. It describes the different phases and screens of the client copy process, provides tips on optimizing runtime and monitoring tables copied, and lists various transaction codes and reports related to client copying.

Uploaded by

nehra.raman07
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

SAP New Client Copy tool

Contents
New Client Copy Tool Overview :.................................................................................................................. 2
Client Copy phases and Processing Options: ................................................................................................ 5
New Client Copy Screens: ............................................................................................................................. 8
Client size determination: ........................................................................................................................... 16
New authorizations for Client copy ............................................................................................................ 17
Optimization of runtime of client copy ....................................................................................................... 19
Excluding Tables before client copy or from running client copy ............................................................. 19
Monitor Tables yet to be copied during local or remote client copy ......................................................... 20
References .................................................................................................................................................. 20

Mayur Pimpalkar
SAP BASIS/HANA
New Client Copy Tool Overview :

Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Client Copy phases and Processing Options:

Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
New Client Copy Screens:

Local Client Copy:

Transaction : SCCLN

Task list :

Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Remote Client Copy:

Transaction : SCC9N

SCC9N

Mayur Pimpalkar
SAP BASIS/HANA
Client Export/Snpashot:

Transaction : SCC8N

Mayur Pimpalkar
SAP BASIS/HANA
Client Deletion:

Transaction : SCC5N

Mayur Pimpalkar
SAP BASIS/HANA
Client Copy logs :

Transaction code : SCC3N

Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Client size determination:
T-code : SCC_client_size

Mayur Pimpalkar
SAP BASIS/HANA
New authorizations for Client copy

Mayur Pimpalkar
SAP BASIS/HANA
Mayur Pimpalkar
SAP BASIS/HANA
Optimization of runtime of client copy

A production client contains a large amount of data. The client copy must access this data selectively. The
database interface limits the throughput to approximately 500MB per hour and process. This means a
runtime of 1-2 hours for a customizing client and an even longer runtime - up to several weeks - for
production clients.

To keep the runtime as short as possible, note the following points:

a) Lock the source and target clients


b) Use parallel processes
c) Reorganize the database and update statistics
d) No Archive log/logging the database and indexes
e) Advance deletion of the target client
f) Network throughput
g) Simulating the copying process and memory space requirements in the database

Please refer SAP note 489690 for more information.

Excluding Tables before client copy or from running client copy


Some tables should not be copied along with a client copy, since they are either not relevant for this
particular case, they are currently assigned an incorrect delivery class, or these tables cannot be copied for
technical reasons. We do not recommend that you exclude tables from the standard system since this may
lead to data inconsistency.

Customers should never include tables belonging to the standard SAP system in the exclusion table of their
own accord. This must first be discussed with SAP.

Start the RSCCEXPT report (for example using transaction SE38 or SA38) in the target systemof the client
copy (if there is just one table only in the source system in a remote copy,this table must also be excluded
from the source system prior to Release WAS 6.20).

An exception list is displayed. Up to Release 4.6D, you can include a table in the exception list by clicking "Add
table". In later releases, you can simply enter the table into the list. Save the entry. As of Release WebAS
6.40, you can start the exceptions list directly from the client copy transaction by choosing menu path "Edit -
> Expert settings -> Tables".

If you already started a client copy (local or remote) and it is still running (not in the post processing step), it
is possible to exclude some tables that were not yet copied from the running client copy. To do this, execute
the following steps:

Cancel the client copy in SCC3.


Run report RSCCEXPT or menu "Edit -> Expert settings -> Tables" in the client copy transaction.
Add the required tables in the exception list.
Restart the client copy in the client copy transaction (SCCL or SCC9).

This solution only works for local and remote client copy types.

Mayur Pimpalkar
SAP BASIS/HANA
Monitor Tables yet to be copied during local or remote client copy

1. In order to determine the tables yet to be copied (processed) check the entries in table CCSELTAB.
2. The remaining table list is in field 'TABNAME' searching by the condition of field 'STATUS' <> (Not
Equal) 'P'.
3. This table is client specific so please check in the target client of the copy.

References

2962811_E_New_Client_Copy_Tool

489690_E_Copying_large_Production_Clients

70290_E_RSCCEXPT

2459313_E_Excluding tables from a running CC

2233823_E_Tables yet to be copied in CC

Blog : https://blogs.sap.com/2020/11/03/new-client-copy-tool/
https://help.sap.com/doc/34796706f38646f68d51a0fa0d4636e4/100/enUS/2b3f8e7447fc4ea08dddaa4
864b0ff2c.html

Mayur Pimpalkar
SAP BASIS/HANA

You might also like