Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

Do not use this report if the target client contains some users and authorizations you want to preserve.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

Do not use this report if the target client contains some users and authorizations you want to preserve.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

Error Handling in Client Copy and Transport

The copy moves a large volume of data and requires considerable storage and machine resources.

Depending on the data involved and the system configuration, the most likely errors are listed below, together with the steps required to correct them.

Error Handling in Client Copy and Transport

Error	Cause	Solution	Notes
Write error in the target client	usually insufficient space in the database or simultaneous processing in target client	Check the system log to determine the name of the tablespace. Extend the tablespace and repeat the copy. You do not have to delete it first.	Do not work in either the source or target client during the copy.
System log messages: Syn. MC maintenance deactivated fully Buffer TABL/TABLP reset Table logging		None	These messages document special functions that are used to improve performance and guarantee consistency.
Termination in an exit program (the termination is explained in an ABAP runtime error).		Run the log display RSCCPROT to determine the name of the last exit program that caused the termination.	The client copy program has not crashed, this is an application error.
Unexplained cancellation or error		Check: Copy log (SCC3) SysLog (SM21) Dump analysis (ST22) and possibly: Job overview (SM37) Spool (SP02)	See note 22514 for further error analysis tips

Client Copy and Transport Authorizations

To copy or transport clients, you need the appropriate authorizations. There are two types of authorizations: general authorizations for client copy, and special authorizations that depend on what you want to copy.

The nitial user SAP* has all authorizations required, except authorization to create a transport request. It can be used for all client copy tools except the client export (SCC8).

General authorization objects for Client Copy

Authorization objects	Action
S_TABU_CLI	Maintain cross-client tables
S_TABU_DIS	Maintain system tables
S_CLNT_IMP	Import data in client copy
S_DATASET	Access the file system

Copy User Profiles and User Master Records

Authorization objects	Action
S_USER_AGR	Copy roles
S_USER_PRO	Copy authorization profiles
S_USER_GRP	Copy user master records

Transport Clients

You also need the following authorizations to transport clients:

Authorization object	Action
S_CTS_ADMI with · TTYPE 'CLCP' · ACTVT '01'	Create object lists for client transport and copy into another client

Remote Copy (authorization required for RFC user in source client)

Authorization	Action
S_TABU_RFC	Remote access to tables in target system

Error Handling

The copy moves a large volume of data and requires considerable storage and machine resources.

Depending on the data involved and the system configuration, the most likely errors are listed below, together with the steps required to correct them.

Error Handling in Client Copy and Transport

Error	Cause	Solution	Notes
Write error in the target client	usually insufficient space in the database or simultaneous processing in target client	Check the system log to determine the name of the tablespace. Extend the tablespace and repeat the copy. You do not have to delete it first.	Do not work in either the source or target client during the copy.
System log messages: Syn. MC maintenance deactivated fully Buffer TABL/TABLP reset Table logging		None	These messages document special functions that are used to improve performance and guarantee consistency.
Termination in an exit program (the termination is explained in an ABAP runtime error).		Run the log display RSCCPROT to determine the name of the last exit program that caused the termination.	The client copy program has not crashed, this is an application error.
Unexplained cancellation or error		Check: Copy log (SCC3) SysLog (SM21) Dump analysis (ST22) and possibly: Job overview (SM37) Spool (SP02)	See note 22514 for further error analysis tips

Restarting Client Copy

If a copy terminates for technical reasons, for example, due to a database shutdown, you can restart the process from the point of termination.

• if a client copy or client import postprocessing did not finish, the system automatically proposes restart mode when you call the transaction. The same parameter settings are used automantically.

The last step is restarted. You cannot continue to copy an incompletely copied table, the table is reinitialized and recopied.

• If the restart fails, the log displays possible reasons for the error. Before you try to restart the program again, eliminate the error.

Displaying Copy Logs

Procedure

1. Choose Administration
® System administration ® Administration ® Client admin. ® Copy Logs.

The system displays a list of all client copies in which the logon client was the target client. You can go to the overviews of the copies in other clients, the „Copies from Transport Request" (SCC1) and the client exports from the system.

2. When you select a copy, you get a log summary with the following information:

• Copy type
• Profile
• Status
• User
• Tables where copy problems occurred
• Statistical info

Double-click on highlighted entries for further information.

3. For further details of the run, choose Details. You get a selection list in which you can get information about the copied tables (e.g. runtime and number of entries copied) and the exit programs from other application components used.
4. If you had tables with copy problems in a local or remote client copy, you can recopy them with the Recopy Errors function.
5. You can display the original log in the file system with the File Log pushbutton. You can also display the export and import logs of the main transport request (KT).

Deleting Clients

Procedure

1. Log on to the client to be deleted.
2. Choose Administration
® System administration ® Administration ® Client admin. ® Special Functions ® Delete Client.
3. You can also specify whether you want to delete the client from the client administration (T000).
4. Setup the parallel process parameters.
5. Start the deletion.
6. In most databases, space which has become free is only available after a reorganization.