The client copy should be performed on a low system activity timeframe.
To have a consistent client copy you should not have any activity on the source system.
Therefore, it is recommended to :
Disconnect and lock dialog users.
Suspend background jobs :
This can be done using report BTCTRNS1. The jobs will be released afterwards using report BTCTRNS2.
For remote client copies, the data dictionnaries beetween the source and target systems should be the same.If not, in case of client copy beetween a production and development system ,you can exclude tables from the client copy using report RSCCEXPT. You have to be sure that your target client will still be usable and consistent compared to your needs depending on the table excluded
2================================================
i am new to sap- basis and please do not mind in case of any wrong message passed...and do correct me.....
what i know is described below....
This is Remote client copy as from one system to other system,so the steps r :
1. Export the user masters of the target system - by "SCC8" and save the Change request no. and confirm that the Change request no is saved in transport directory (/usr/sap/trans/)
2. then lock all users in both systems expect which you and other's required to operate at that time and it is done by using Transaction code - su10
3. check all active users by using "AL08"...it is "AL(zero)8"
4. use transaction code - SCC9 to identify the two systems and define here...the target and source systems with SAP_ALL profile.
5. check job log in "SCC3"
6. check archive log space in "ST04" (if log free space is less than 10GB, then run C:\sqllog.cmd present in other server )
7. After Finishing client copy, import user master by Change request no in "STMS_IMPORT".
8. Run "SCC7", post import steps....mention target and source sytem with SAP_USER profile and schedule by background jobs.