SAP Basis Client Copy

SAP Basis - Client CopyPrepared by

Wasim Latif

HP Global SoftMarch 2013Document History

VersionDateAuthorCommentReviewed by

1.0Wasim Latif

TABLE OF CONTENTS

51Introduction

51.1Background

51.2Purpose of this document

51.3Prerequisites

62Creating a New Client

93Client Copy

93.1Features

104Local Client Copy

104.1Prerequisites

104.2Source client lock / system lock

114.3Performing the client copy

134.4Client Export

154.5Importing the exported Profiles/data

154.6Post Processing

164.7Checking the Logs

175SAP Notes

6 SCC9 Remote Client Copy

1 Introduction

1.1 Background

One can use the client copy to create New clients from the SAP reference client 000 during initial installation of an R/3 System.

training clients

demo clients

test clients

production clients

1.2 Purpose of this document

This document will describe the in-detail process of creating a new client, resource estimation for creating new client and performing a local client copy.1.3 Prerequisites

It is assumed that you have proper authorization to perform the client copy in the SAP system.2 Creating a New Client

We perform client copy when we create a new client. This new client is created in transaction SCC4.Pre requisites for creating a new client are listed below.

You should have enough free space in the database for this new client. To estimate the amount of space required, you can perform a test run. This is described more in detail later in this section.

You should have authorization for creating a new client.

Perform the following steps for creating a new client and calculating the resources required for creating and doing client copy.

Log on to SCC4 and go to Change mode. Click on new entries button as shown below.

You will get the below screen. Make the entries in the following screen as per your requirements.

Save the entries once you are done. The new client created. Now the next step is performing client copy i.e copying contents to the new client. Before doing that we need to estimate the resources required. (database space required) To estimate the resources required we will perform a test run in the newly created client. Log in into the new client with standard user SAP*.

You can improve the performance of the client copy, for example, by excluding tables or packages, with Edit -> Expert Settings. You can exclude tables from the client copy, for example if they are not relevant for the target client, in the Tables tab. For further information about excluding tables from the client copy,choose the Help button in the expert settings. For further information about expert settings in the client copy, see the SAP note 446485.

Go to transaction SCCL and fill the entries in the resultant screen with the source client details from which you need copy. Do not for get to check the Test Run Button as shown below.

Schedule as a back ground job.

Click on Continue and you will get the following screen. In this screen click on the check button Resource Check

Now the job will run in the background and the log for this can be found in SCC3. Open the log. Click on green tick. If you click on Resource Analysis button, you will see the estimated database space details as shown below.

Thus you can estimate the resources required for performing client copy.

3 Client Copy Client copy in SAP can be done either locally or remotely. You can copy the following components in client copy 3.1 Features You can copy the following components of the source client into the target client:

User master data: User master data is only deleted in the target system if a profile with user master data is copied. Authorization profiles and roles belong to customizing and are therefore always copied with it. Copying users without authorization profiles is problematic, so the copy profile SAP_USER contains authorization profiles and roles as well. Customizing: All profiles except SAP_USER contain customizing. Customizing data is generally in tables with delivery classes C, G, E and S. Master/transaction (application) data: select this option, for example, if you want to set up a test system from the production client. 4 Local Client Copy4.1 Prerequisites If you are creating a new client and then performing client copy, please check the available free space which can be done using db02 transaction. Also keep monitoring the table space growth.

Make sure that you have authorization to perform the client copy.

Inform all the developers or the team about the activity and make sure no one will log into the system during the activity

If required lock the client against log on or lock the users in SU10.4.2 Source client lock / system lock If required use the report RSCCEXPT to enable the source client locking for the duration of client copy. (Please note - only available from 6.10 systems up, from 6.40 available from the expert settings option in the menu). Run the program in SE38 (any client).Select the lock option:

Press Save.

While the client copy is running, users will not be able to log onto the source client.Once the client copy is complete the lock is automatically removed. If the client copy is cancelled (for whatever reason) log onto another client, and run SCC3, you will be prompted to unlock the source system.

4.3 Performing the client copyThe following steps illustrate the procedure for client copy

1. Log into the target client using SAP* and pass for the password or use DDIC/Super user id.2. Enter transaction SCCL

3. Enter the profile (SAP_ALL to copy everything) depending on what do you want to copy.

The following table describes the list of available profiles along with their description

Copy profileDescription

SAP_USERUsers, user roles and authorization profiles are copied. The client is not reset.

SAP_CUSTClient-specific customizing including authorization profile is copied. The application data is deleted, the user data is retained.

SAP_CUSVSAP_CUST with variants

SAP_UCUSSAP_CUST with user master data

SAP_UCSVSAP_UCUS with variants

SAP_ALLAll client data except change documents (see note 180949) and local data is copied.

SAP_APPLSAP_ALL without user master data

4. Enter the source client number

As shown, enter the appropriate Source client number. 5. Enter the source client for User MastersThis means that the target client User masters will be updated by the source client User masters details. This option will be useful if you are creating a new client and performing the client copy.

Suppose if you dont want use the Source clients user masters, then perform a client export in the target client before running the client copy. The client export process is explained in step 3.4 below.6. Select in the menu bar GOTO ( Parallel processes

a. Fill in:

b. Maximum number of processes: 3

c. Logon/server group: (Select with F4) PUBLIC

d. Click on the SAVE Button

7. Click schedule job button

Enter the Background server name.

8. Click yes after verifying the client copy settings

9. To schedule the job to run immediately, click the immediate button. Otherwise Date/Time and choose an appropriate time.

10. Click the save iconNow the Job has been scheduled (if you have chosen the schedule job option).It is recommended to run this job during low system activity time (off business hours)4.4 Client Export We can use the client export transaction for exporting the user profiles to transport requests (before performing client copy) and then we can import them back in to the system using STMS.Enter the transaction SCC8

Select the profile you need to export to the transport request.

If you want to export the SAP_USER which will contain the user master records and authorization profiles choose it.

Now enter the target system and client number whose User master record details are to be exported.

Schedule the job or else you can run the Job immediately.Now it will give you a transport request which was created with profile data. Up to 3 requests are created, depending on the data selected and available:

1. "KO" for transporting cross-client data, if you have selected this

2. "KT" for transporting client-specific data

3. "KX" for transporting client-specific texts, provided texts are available in this client

When the transport requests have been created successfully, the data is exported synchronously by starting the transport program tp at operating system level, and can take several hours, depending on the data volume.

The status of the export can be found using either Transaction SCC3 or Transaction SE01 and specifying the transport request. Wait until the data has been successfully exported before you start another client copy or transport involving the source client

You can check in SCC3 whether the Client export is successful or not.Go to SCC3 -> Exports ->

4.5 Importing the exported Profiles/data Once you export the SAP profiles using SCC8 then choose one of the above-named requests to import, in the Transport Management System (transaction STMS) import overview. Its other transport requests are then selected automatically.4.6 Post Processing

After importing the exported client following post processing needs to be done. You must post-process with the transaction SCC7 after the import. When you call the transaction SCC7 in the target system an analysis procedure first determines the associated transport request and displays its ID "KT" with the parameters of this export. Verify that the correct transport request was selected for import.

If the transport requests are not yet in the import queue in the target system then add the request manually. You can also import the same at the OS level using TP command. You can check the related import log in SCC3.

4.7 Checking the Logs

All the client copy logs can be found using the transaction SCC3.

You can select the Exports log by clicking on Exports button as shown above.

Also it displays the list of client copies that were performed in the system.

The log file contains the following details.

It will display the type of client copy, and the profiles that are copied.

By looking at this log you can find details like User name which is used for scheduling client copy, and the dates of start and completion.

Also, displays details like No. Of tables accessed, copied and deleted lines during client copy.5 SAP NotesIn This section I have listed useful SAP notes.

Note 198960 - Copies from client: Incorrect update rulesNote 304605 - SAP query: Queries missing after client copyThis note describes how you can improve the performance of local or remote client copies on iSeries.Note 517589 - iSeries: Client copy performancePrerequisite-an RFC connection has to exist

If you experience problems copying from another system, see the SAP note

557132.

For more information about remote client copies, see also SAP Note 47502

On how to copy large production clients, see SAP Note 489690 in the SAP

Service Marketplace.SAP Remote Client Copy (Transaction Code: SCC9)/ LABELS:SAPThe 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 targetCreate RFC Connection from target to source (TCODE SM59)Connection type should be R3 connectionConnecting 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

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 tabTechnical 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 RFCIn 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 systemTest

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.55HP Global Soft