R/3 Client Is Defined As an Independent Accountable Business Unit with in an R/3 System

CLIENT ADMINISTRATION:

Client:

R/3 Client is defined as an “independent accountable business unit” with in an R/3 system.

In technical way client is a logical unit of R/3 database.

Data in the R/3 database are classified as two types, Client Independent data and client dependent data.

1) Client Independent data / Cross client data.

Data which can be accessable through entire R/3 database from any client is called as client independent data or cross client data.

Ex: screen data, transaction data, repository data, dictionary data….etc

2) Client independent data / Client specific data.

Data which can be accessable through a client in which it was created is called as client dependent data or client specific data.

Ex: user data,authorization data, application data….etc

As per above two types, the R/3 client maintains differentiation with respect to client dependent data. No.of clients created in one R/3 database to maintain differentiation in customization, testing, quality assurance and production data.

R/3 client can be identified with three digit numeric number starts from 000 to 999

Default clients:

By installation there are three default clients will be configured in database.

Which are ( for Non-Ides Software)…

000 - Master Client

001 - Copy of master client

066 - Early watch client

For Ides Software we have clients ..800,810,812..

Client creation:

- New client will be created using SCC4 transaction code.

Client Copy:

000 being as a master client which maintains all the data given by SAP company. 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 profiles.

We have three types of client copy procedures in R/3

(1) Local client Copy

(2) Remote Client copy

(3) Client Export / Import

(1)Local Client Copy:

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

Preparation:

(a) Set a system message about the client copy information with SM02

(b) 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.

(d) Check all tablespaces and add data files if any table filled above 85%

(e) 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 alolw any client copies with in that.

Procedure:

-Log on to the target client with user id SAP* and password PASS

-Execute SCCL and select a client profile with source client number

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.

Ex: 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.

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

Test Run:

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

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.

Resource Check: 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 workprocess 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 workprocess can be monitored using SM37 Transaction code.

Client Copy log:

We can check the client copy log using SCC3 transaction code .

(2) Remote Client Copy:

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 .

Remote client copy will be done using SCC9 transaction code using the same steps mentioned in above client copy.

RFC 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:

i) Connecting application server with same database

ii) Connecting with R/2 system database

iii)Connecting with R/3 system database, etc…

connecting type 3 stands for creating a connection between R/3 to R/3 technology servers.

Ex: 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 settings.

Steps in creation of RFC destination

Go to SM59 in target clientà Creteà Give RFC destination Name(SIDCLNT<Sourec clnt No.>)àConnection type(3)àDescriptionàEnter

So that below tabs will be opened…

Now 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à saveà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.

(3)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 will be done using SCC8 transaction code

Preparation:

a) Set a system message about source client lock

b) Lock all dialogue users in source client except administrators.

c) Delete all released background jobs and ensure that there are no background jobs running in source during copy.

d) Check transport tool to confirm functioning of “tp and R/3 trans” include TMS configuration.

e) Ensure there are no updated errors in SM13 of source client.

f) Check for database deadlocks, delete if existing.

g) 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>KONo - For cross client data

<sid>KTNo - For client specific data

<sid>KXNo - for client specific texts

Once above TRs got created, all of them automatically released and exported to targer 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 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 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 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 productive 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