transaction code SCC4

Click on Display/Change button

Click ok button.

Click on New Entries. Choose client role as customizing and click Save. Go back and click save again. Now logoff.

Client Copy
000 is a master client which maintains all the data given by SAP. But it will not allow client independent customization. For this reason of implementing software or customization as a part of post installation a new client will be created and copied from 000 with SAP_ALL profile. We have three types of client copy procedures in R/3 Local client Copy Remote Client copy Client Export / Import

Local client Copy

If a client copy held under the same database between two clients, this is called Local Client Copy. This is recommended as a post installation step.

Preparation
Set a system message about the client copy information with SM02 Lock all users except administrator in source client. Lock can be given by SU10 transaction code. Because in any client copy the source data should not be edited. Cancel all the released background jobs in the source client. Check all table spaces and add data files if any table filled above 85% Create a client using SCC4 transaction and mention client role. Note: In case you are creating a client in PRD system to maintain production data, do not select the client role as production because client role as Production will not allow any client copies within that.

Procedure
y y y y Log on to the target client with user id SAP* and password PASS If unable to login with SAP* (in ECC6) use TCODE RZ10 to create a new Default Parameter login/no_automatic_user_sapstar and set the value to 0. Run the transaction SCCL Select a client profile with source client number y y of client copy we can test the client copy with two options.

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)

y y

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

y y

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 back ground work process can be monitored using SM37 Transaction code. locked. Using background mode a job will be configured with the start condition and runs with the help of

y y

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.

y y

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.

y y

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.

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".

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.

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

Run SCC3 transaction code

You will see the following screen.

Double click on the job being processed

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.

Go back and click on Details button to see the details

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

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

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

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

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 systems 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.