SAP Remote Client Copy Transaction Code:SCC9

The client copy held between two different databases or two different servers (R/3 systems) is known as Remote Client copy. Remote Client copy requires RFC Connections.

Create RFCUSER with SAP_ALL and SAP_NEW profiles on source system (DR1)
Run su01 and create new user RFCUSER and copy from ddic

Make sure the user type is SYSTEM.

Lock all users on source
• Send system message to all users SM02
• Wait for one hour and kill any remaining users
• Run SU10 to mass user lock

Stop all background jobs
• Display all background jobs using sm37
• Run BTCTRANS1 to de schedule all jobs
• Run BTCTRANS2 to re schedule all jobs

Make sure enough space is available for TableSpaces in target
Create RFC Connection from target to source (TCODE SM59)
Connection type should be R3 connection
Connecting two applications running on two different servers to enable the data communication is called as RFC connection. Using RFC connection the communication obtained between source and target systems with the help of gateway work process which enables data communication between them.

RFC connections will be created using SM59 transaction code
Types of RFC connections
Connecting application server with same database
Connecting with R/2 system database
Connecting with R/3 system database connecting type 3 stands for creating a connection between R/3 to R/3 technology servers.

SAP R/3 to SAP R/3
SAP R/3 to SAP BIW (vice versa)
SAP R/3 to SAP CRM (vice versa)
SAP R/3 to SAP SRM (vice versa)

If SAP R/3 to SAP R/3 connection obtained the data communication held between those two systems as per its technical and configuration 
Steps in creation of RFC destination
• Go to SM59 in target client

• Create
• Give RFC destination Name (SIDCLNT)
• Connection type (3) for R/3 connection

• Choose Description and Enter
• Now additional tabs will be opened
• Give CI host name of Source client and Instance number in the tab
“Technical Settings”: Go to “Logon/Security” tab, mention source client number, give user information using which source RFC to be logged on to target then save and Test connection.

User info in RFC
In RFC administration, screen logon details required to be given for the source system of RFC to be logged in to the target system RFC. This user type should be system or service which ever part of target system database. Once RFC is created source to target system the data extraction can be done from target system to source system
 
Test


Go back and run SM59 and you will see the newly created connection.

Run Remote Client Copy (TCODE SCC9)
Remote client copy will be done using SCC9 transaction code using the same steps as done in local client copy.

 

Only difference is for the source client, instead of giving the client number of a local client you will need to provide the RFC connection for the system containing the source client, which is defined in step 1.