SAP R/3 Client Copy using Client Export/Import

It is one type of client copy to copy a client data between two R/3 systems using TMS. Using client Export /Import client independent and dependent data also can be copied between two different databases. But both the systems patch level, type of database and software version should be same. It is a two step process where in client Export, source client data will be converted as a “transport request” and the request exported to target system. In Client Import, the exported TR has to be imported in to target client using STMS.

Export

Client Export is done using SCC8 transaction code.

Preparation

1) Setup a system message about source client lock.
2) Lock all dialogue users in source client except administrators.
3) Delete all released background jobs and ensure that there are no background jobs running in source during copy.
4) Check transport tool to confirm functioning of “tp and R/3 trans” include TMS configuration.
5) Ensure there are no updated errors in SM13 of source client.
6) Check for database deadlocks, delete if existing.
7) Make sure that there is enough space in target system table spaces and in Common Transport directory.

Procedure

Log on to source system’s source client and make sure that all above steps were performed .Then go to SCC8 tcode for Export. Select a client profile according to data to be copied as a Transport request. Mention target system into which the client should be copied. Configure this as a background or dialogue.
According to the client profile selected and the data available, maximum 3 transport requests will be created and automatically exported to target system mentioned. The requests are like
<sid>KO<No> – For cross client data
<sid>KT<No> – For client specific data
<sid>KX<No> – for client specific texts

Once above TRs got created, all of them automatically released and exported to a larger system. This can be checked in SE01 or SCC3.

Import

Log on to target system, create a new client in target system using SCC4 tcode. Then logon to that new client execute STMS tcode.

STMS –> import overview->refresh the buffer to find exported requests→import Queue of target client→start importing using different options.
In case 3 transport requests are created in export any one of the TR is started then the rest TRs also imported in to target client automatically.

Client Open & Close

An R/3 client can be opened or closed against to importing workbench data, customizing data as a transport request. An R/3 client can be opened or closed using SCC4 tcode.
In production environment productive client always would be closed to restrict import of workbench type of requests. This can be obtained by changing client configuration using client admin tool in SCC4. Where these changes applied on T000 table in database.

Client import post processing

After importing TRs in target client successfully we can find same TR selected to perform post processing in tcode SCC7.Then start this job as a dialogue or back ground to perform client import post processing.

Client refresh

Deletion of existing client data and copying the same client using a productive client data is called as “client Refresh”. In support environment client refresh may required to be done frequently for the clients in quality system with production clients.
Normally this happens once in 3 months in production environment. The main object of client refresh is to provide production environment in test & quality system. This may be held using remote client copy or client import/Export .But client transport is preferable in real time.

Client deletion

We can delete the client using SCC5 transaction code.

SAP RCC – Steps in creation of RFC destination

Steps in creation of RFC destination
• Go to SM59 in target client
Display-and-maintain-RFC-destinations
• Create
• Give RFC destination Name (SIDCLNT)
• Connection type (3) for R/3 connection
Type-of-entry-in-RFCDES
• 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
SAP-RFC-Destination-DR1

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.
SAP-Remote-Client-Copy-User-Display
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

SAP R/3 Local Client Copy – Regular Run

Scc3-Log-Display

Click refresh to see the number of tables processed. Click on file log to see the log Go back and click on Details button to see the details.

Scc3-Log-Summary

Go back and click on Details button to see the details

RSL-G0001 - Analysis-of-the-Central-System-log

Go back and click on Monitor to see the status of the copy

SAP-R-3-Client-Copy Local-Client-Copy-transport-log-Analysis

The local client copy mode allows copying only client dependent data from the source to target, because independent data is common in entire database.

SAP R/3 Local Client Copy – choose background scheduling parameters

Schedule the client copy in background: Choose source client (000 in our case), profile name (SAP_ALL in this case), background server to run this job. Click on “immediately” to start the job after clicking “OK”.

Screen to Schedule the SAP R/3 client copy in background

Once you click OK, you will see the following verification dialog. Please verify the target client, profile name and source client and make sure they are what you intended. Also verify the source client user. Click continue.

screen to verify the target client, profile name and source client

In the next information screen, you will see “background job was successfully scheduled; log is displayed in SCC3”

background job was successfully scheduled; log is displayed in SCC3

SAP R/3 Local Client Copy – Test Run

Before we start up the actual run of client copy we can test the client copy with two options.

Local-Client-Copy-Test-Run

You can change the profile from SAP_ALL (All Client specific data without Change Docs) to a different profile such as SAP_APPL (Customizing and Application Data without Change Docs), SAP_CUST (customizing), SAP_CUSV (Customizing and user Variants), SAP_UCSV (SAP Customizing user master records and user Variants), SAP_UCUS (customizing and user master records), SAP_USER (User master records and Authorization profiles)

Local-Client-Copy-Test-Run

Finally click OK and a “Client Copy Verification Dialog Box” will appear as below. Click on Simulation to start the client copy simulation.

Local-Client-Copy Verification

Resource Check

Click this to check resources are sufficient. Such as disk space etc. All the data to be copied will be counted without being read. Using this we can find database free space availability with amount of data going to be copied. Client copy can be done with Dialogue mode or Back ground mode.
Using Dialogue mode the copy will be configured with Dialogue work process and the screen will be locked.
Using background mode a job will be configured with the start condition and runs with the help of back ground work process can be monitored using SM37 Transaction code.

Simulation

Data to be copied will be read without saving to database. Using this we can find if any inconsistency there in the data to be copied. Click this to simulate client copy. All data from source client is read but not written to target client.

Client Profile

It is a selection Criteria of the data to be copied from the source to target client. There are some client profiles already created by SAP. We have to use required profile as per the data to be copied from source to target client.

Example

SAP_ALL – All client specific data.
SAP_APPL – Application data.
SAP_USER – User master records with authorization data
SAP_CUST – Customizing data
SAP_EXPC – Customizing with cross client data.
Local-Client-Copy-Status

Copyright 2005-2016 KnowledgeHills. Privacy Policy. Contact .