Skip to Content

Difference between Remote Client Copy and Client Export/Import

Brief explanation of difference between Remote client copy and client export/import

Remote Client Copy

  • Remote client copy is done through RFC and it will not create a transport  request


  • Remote client copy method is not preferred for large client copy.


  • With parallel processes from Release 4.6, the remote copy is faster than a client transport. Usually the entire copying time for a remote copy is in fact well below the pure export time of a client transport. However, a high speed LAN/WAN link is required.

  • Remote client copy does not require files space at OS level for transports.
  • Identical copy cannot be duplicated at a later date.
  • In automatic repository, consistency check is performed, if inconsistency are detected, the client copy is terminated and error msg. is displayed
  • Parallel processing: Parallel processing (speed up copying process) can only be used when performing local and remote client copy (SCC9), Click on Go To, Select Parallel Processing.


Client Export/Import

  • The client export generates transport files, which can be imported into another system thru STMS


  • Client data is exported into a file at OS level, at any given time, the client data is imported from source to target system.

  • Identical copy can be duplicated at a later date.

  • No Automatic repository consistency check is done, need to be done manually using Tcode SCC7.

  • The export process will generate up to three files at OS level – SIDKO, KT, KX depend on client profile

<SID>KO<No> – For cross client data

<SID>KT<No> – client specific data
<SID>KX<No> – for client specific texts

Remote Client Copy Method:

  • Make sure there is no activity in source and target client
  • Make sure enough space available on target system
  • Create a system message SM02
  • Suspend the background jobs, Tcode SE38, BTCTRNS1


Prerequisite for Remote client copy

  • Create ABAP RFC connection from target to source client. Tcode SM59, Connection type 3

Steps:

  1. Login into target client
  2. 2.     Run transaction  SCC9 on target client, and enter the following:
    1. a. Selected profile:                        Choose the correct copy profile
    2. b. Source Destination:       Choose the RFC destination created in above steps
    3. c. System name and source client automatically filled after choosing the RFC connection
  3. 3.     Run in background
  4. 4.     Monitor the remote client copy logs in SCC3 and background job in SM37

remote client.GIF

Thanks


To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Hector Ganga Castro

    Excellent, gratefull information. Just to clarify, the program to suspend the background jobs is BTCTRNS1, and to reactivate them is BTCTRNS2 (without the “A”).

    Best regards.

    (0) 

Leave a Reply