2014

SAP CLIENT CONCEPT

Kunal Rai

9/2/2014
 Clients in SAP
Important Point about Client
 When you log on to an SAP System, you log on to a particular client of this system.
 Any activities you carry out in the system are always carried out in one client.
 When you plan your SAP system landscape, you must consider which clients you
need for which activities.
 Clients are essentially self-contained business entities within each SAP system.
 Each system—SAP ERP, CRM, SCM, and so on—has a unique system-specific client
you log in to.
 A client has its own separate master records and own set of "tables"
 In the SAP landscape, a client is an entity with independent information and data.
 The SAP client concept allows an organization to split a system into logical subunits.
 Clients may operate as separate business units, where all data is stored in a common
database
 Access rights for each client are defined during the installation process.
 Client specific data includes
1. user master data (including authorizations and user groups)
2. Data customization
3. Application/business data
Note:
There are 2 types of data in SAP
1. Client specific data: Client specific data means data such as user master and
application data which belong to a specific client only.
2. Cross client data: Cross client data is not specific to any client. It is the data that
belongs to all clients. It means data such as cross client customizing and all
repository objects which affects the whole SAP system.

The number of clients in a SAP system directly influences the following:

 Buffer: The number of clients impacts buffering demand. An example is main
memory usage.
 Upgrade: Different activities are affected by SAP upgrades, where run timers are
longer, depending on the number of clients.

Clients and Their Roles in a complete landscape

1. CUST
 For business requirement a client need for Customizing settings, and possibly
ABAP Workbench developments.
 This client is known as the Customizing and development client, or Customizing
client for short. The abbreviation CUST is used for this client.
2. QTST
 Before you can use the Customizing settings and Workbench developments
productively, you need to test them extensively for errors.
 The client where these tests are made is the Quality Assurance Client, QTST for
short.
3. PROD
 A separate client is required for productive use of the SAP System.

1
  It is essential that no Customizing settings or Workbench developments are made
here and also that no tests are carried out.
 This client is known as the Production Client, PROD for short.

These three clients, CUST, QTST and PROD, are the central clients that exist in every
system landscape.
It is recommend that make all Customizing settings in a single Customizing client, and then
use the CTS to transport them to the other clients.

Examples of other client roles are:

4. Development test client (TEST):
Developers can use this client to test their Customizing settings and Workbench
developments, before they release their change requests. In this client the
developers can create test application data for realistic tests. If they discover errors,
they can remove them in the Customizing client. A development test client is always
set up in the same SAP System as the Customizing client.
5. Prototype or sandbox client (SAND):
You can use this client to test any client-specific Customizing settings if you are not
sure whether you want to use them in this form. Any settings that you want to keep
are then entered in the Customizing client. To prevent conflicts between the
prototype client settings and real settings in the Customizing client, you cannot make
changes to cross-client Customizing data and Repository objects in the prototype
client. The CTS doesn’t record changes made to client-specific Customizing data, and
does not transport them from the prototype client. You can make sure of this by
making appropriate client settings.
6. Training client (TRNG):
To prepare end users for new functions that are to be transported into the production
client, you can set up a training client. The users can use the new functions in this
client with specially created application data.
Defaults Client in SAP System
1. 000 - Master client
2. 001 - Copy of master client
3. 066 - Early watch
SAP Reference client (000)
All SAP tables are in the SAP Reference client. Sample entries, which you can change, exist
for the tables in which you store your organizational structure.

The SAP Reference client contains the following settings:

 Tables with default values
 These tables are independent of the organization units.
 Examples of the organization units
 No application data, that is, no master data and no movement data
 Do not use this client in production processing.
 A default Customizing setting

2
Note
Company code 0001 in client 000 contains complete Customizing. Country-specific
Customizing (legal and business requirements) of all standard countries is delivered in
company code templates XX01 (XX = country indicator).
SAP updates the settings in each new release. As a result, client 000 always has the current
status.

During release upgrade, SAP automatically updates:

 Table contents and table structures
 Programs
 Screens
 Forms
 Online help
 SAP Reference IMG
You can use the SAP reference client to copy default settings into other clients.
Production preparation client (001)
The production preparation client is identical to the SAP Reference client,
I.e. you cannot use this client in production processing either. The Customizing settings are
made in this client. You customize it into your test environment. Copy the new or changed
table entries which are put in client 000 by SAP during a system or a release upgrade, using
Release Customizing.
Early Watch Client (066)
This client is purely a service client that enables SAP to access remotely the customer
system with regard to analyzing errors and performance.
You must not change or delete this client.

User Description Clients Default

Password
SAP* SAP system super user 000, 001, 06071992
066 PASS
all new
clients
DDIC ABAP Dictionary and software logistics super 000, 001 19920706
user
EARLYWATC Dialog user for the Early Watch service in 066 support
H client 066

 How to view all clients in SAP system

Transaction SCC4.Using SCC4 transaction, client settings can be modified
 What is the table which holds client details in SAP?
Table T000 will contain all the client details and their settings.

Client Creation

3
Open client activities
 Whenever there is an issue in the system which is not solved by consultants, the
issue will be intimated to SAP by means of an OSS message. Now SAP will ask the
client to be opened and ask for a user id and password.
 If the client is opened, then SAP can be able to logon to the client from their location
and test the scenario.
 Another scenario can be where a transport has not moved properly to the production
system, but there is not enough time to move the transport once again. Now people
just open the production system, which means, any configuration can be directly
done in the system.
 Now the changes can be done in the production system directly. After that the
system will be closed for any configuration.
 Open client activity is number range for various objects. Number range is never
transported, but is a open client activity.
 Also some settings in EDI are done open client.

Client Activity
SCC0 Client Copy SCC1 Client Copy - Special Selections
SCC2 Client transport SCC3 Client Copy Log
SCC4 Client administration SCC5 Client Delete
SCC6 Client Import SCC7 Client Import – Post Processing
SCC8 Client Export SCC9 Remote Client Copy
SCCL Local Client Copy

SAP client copy methods

The Procedure followed in performing client copy and client export/import differs, but the
final output would be the same.
Using client copy methods, client independent and dependent data can also be copied
between same or two different R/3 System.

Types of SAP client copy Methods:

1. Local Client Copy: Using this method of client copy, copy of data from one
client to another will be performed within same R/3 system using Tcode SCCL.
2. Remote Client Copy: Using Remote Client Copy method, we can remotely
perform client copy with required Client Copy PROFILES between two R/3
Systems. This Method of client copy will take very long time to complete and may
slow down the system performance.
3. Client Export/Import: Using Client Export/Import Method, Data from one client
can be copied to another client between two R/3 systems using Transport
Management System. This method requires downtime for Production system at
the time of Export Production Client. And the estimated time for client export
activity will depend on the size of Client to be exported.

In this process, we will first export the data from Source System can be Production client
which will generate transport request (TR's) and during the process client data will be

4
exported as DATA FILE, COFILE at OS level. Later the generated files at OS level of Source
system will be copied/exported to target system and kept in same location. In target
System can be Quality Client, the exported TR's will be added to Quality system transport
Queue and will be imported in to target client using STMS.

NOTE: To perform Remote Client Copy or Client Export/Import, Make sure both source
and target system must have same SAP version along with Patch Levels.

Local client copy (SCCL)

Reason:
You want to copy the users and required data from a customized client to a new client
 The client copy does not copy ABAP programs or table structures.
 According to profile selection we determine which data need to copy, we don't copy
all of the data.
 It took several or more hours (even up to a day for very large clients) to complete.
 We may have to adjust the system parameter max_wp_run_time for large client
copies.
 You should stop all users and backgrounds jobs when performing a copy otherwise
there may be inconsistent data in the target client when the copy has finished.
 It is possible to perform test runs before actually copying the client, this will
determine if you have enough resources (memory, disk space, etc.) to perform the
copy
Pre-requisites:
To perform a local client copy we must first
1. Create a new logical system
2. Create a new client
3. You need to monitor Log area continuously else Client copy will be failed once it
is full.
4. Also take care of Temp Table space if you are working in Oracle Database.
1. Logical System:
Logical system enables the system to recognize the target system as an RFC destination.
Logical system is required for communication between systems within the landscape. You
need a logical system when you create a new client in SAP
 T-Code to create Logical System in SAP is BD54
 Logical System is transportable.
Create Logical System in SAP
1. Run transaction code BD54. We will get table is cross client click on OK

2. Click in edit button

5
3. Click on new entries.

4. Enter the name of logical client into format

5. Now save the entries it will ask you to transport request click on new request and
define description.

6
 6. Now new transport request and click ok

2. Create Client
Execute SCC4 and click on Edit option and then new entries it is also going to ask like
above that table is cross client (click ok) and save it.

NOTE:
If the client role is production then the settings should be as follows:
 No changes allowed
 No changes to repository and cross client
 Protection level -1 – No overwriting
 eCATT & CATT Not Allowed

7
Local Client Copy
To perform the local client copy, first we need to login into the target client (i.e. newly
created client)
Logging in to the new client:-
You may use the following credentials to login into the newly created client.
 User = sap*
 Password = pass

Note:
If you are unsuccessful, then please change the parameter
"login/no_automatic_user_sapstar" = 0 in default profile and try logging in again with above
credentials.

8
Enter transaction SCCL
The following screen appears

Choose the Profile and source client and depend on your organization strategy run the job
immediately or in background.
SAP 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.

9
At last schedule job it will took time to copy all the data.

10
11
Once the copy is started, you can now check the logs in scc3

12
 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.
 The client copy does not copy ABAP programs or table structures.
 According to profile selection we determine which data need to copy, we don't copy
all of the data.
 It took several or more hours (even up to a day for very large clients) to complete.
 We may have to adjust the system parameter max_wp_run_time for large client
copies.
 You should stop all users and backgrounds jobs when performing a copy otherwise
there may be inconsistent data in the target client when the copy has finished.
 It is possible to perform test runs before actually copying the client, this will
determine if you have enough resources (memory, disk space, etc.) to perform the
copy
 Resource check confirms that we have enough resources.
 It will give to an idea on how long the copy will take.
 If you are performing a remote copy while an existing copy is taking place, SAP will
inform you that another client copy is running.
Prerequisite for Remote client copy
Find the source client space with the client size. Note'0118823' will give you the size of the
source client.
Create ABAP RFC connection from target to source client. Tcode SM59, Connection type 3
 both source and target client will be locked
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

ECP4 _887 ECP_200

Target System Source System

Target System Source System

 Login to client there u want to copy Login to Client that u want to copy
 Create RFC Create user RFCUSER
 SCC9

Target System/ Target client: The system which going to get data
Source System/ Source client: The System Which having the data

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

Source System
Create user RFCUSER

14
15
Target System
Execute SM59 and define RFC for from target to source means from where we r going to copy data.

16
Give source system client and rfcuser

Test the connection

17
.

18
19
Once the copy is started, you can now check the logs in scc3

20
 Client Export and Import Activity
In general above activity can be performed when there is a requirement of refreshing the
Quality Client Data with Production Client Data using available SAP Client Copy profiles.
 only one system's client is locked at a time
 The client copy does not copy ABAP programs or table structures.
 According to profile selection we determine which data need to copy, we don't copy
all of the data.
 It took several or more hours (even up to a day for very large clients) to complete.
 We may have to adjust the system parameter max_wp_run_time for large client
copies.
 You should stop all users and backgrounds jobs when performing a copy otherwise
there may be inconsistent data in the target client when the copy has finished.
 It is possible to perform test runs before actually copying the client, this will
determine if you have enough resources (memory, disk space, etc.) to perform the
copy
A client transport is way to copy a client across system, this involves three steps
1. Client export
2. Client import
3. Import post-processing
Client Export Activity Prerequisites:
 Intimate all the users regarding System Downtime and lock all the users in
Production Client using SU10 (recommended) or EWZ5 (NOTE: using EWZ5, the
entire unchecked user will be locked).
 Make sure around 10-15GB of free space is available in UNIX: mount point of
"/usr/sap/trans", WINDOWS: "D:\usr\sap\trans".
Steps for Client Export Activity in Source system:
1. Execute Tcode SCC8
2. Select Profile for desired copy type (Usually All SAP_ALL or user master only
SAP_USER)

21
3. Select target System (or group)

4. De- Select "Test Run" (If selected)

5. Click On Schedule as background Job to start the Export

6. Select Background server by double clicking on it. It is optional. Make sure “No
printer dialog” and “Immediate” are checked. Then click on schedule Job.

22
7. Max of three Transport Requests(TR's) will be created, depending on the data
selected and available:

23
8. "SIDKO00025" for transporting client-independent data, if you have selected this
9. "SIDKT00025" for transporting client-specific data
10. "SIDKX00025" for transporting client-specific texts, provided texts are available
in this client.
11. Monitor TP logs from SCC3, AL11 or from OS level for errors and check the
growth of exporting file at OS level under /usr/sap/trans/data/

24
 12. Once the Export of required client has been successfully completed. We can
unlock all the user of Production Client and end users can starting using
Production Client
Import Activity Prerequisites:
 First Copy the DATA FILES and COFILES generated during Export activity at OS level
of SOURCE SYSTEM located under "/usr/sap/trans/data/" and "/usr/sap/trans/cofile/"
to the SAME location in the TARGET SYSTEM. And change the permissions of the
copied file as required.
 Secondly there are some Database specific activities to be taken care of... before
starting the import activity as explained below:
Since SAP will work in combination with various databases, from client import prospective
care has to be taken in monitoring the growth of log files and in some cases it is required
need to increase the size or number of log files to be used during this activity. And each
database (Oracle, DB2, MSSQL, Sybase, MAXDB) has its own method in doing so...

Example: Let’s ask we are performing client import activity in R/3 system with DB2 as
Database, In general active log file used by DB2 will be controlled by parameters
LOGPRIMARY, LOGSECOND. Where LOGPRIMARY = 20 and LOGSECOND = 40, in total by
default DB2 will use 60(20+40) active log files to complete daily transactions.
But in this case, DB2 with 60 active logs will not be sufficient to complete the Client Import
activity. So before starting the import activity make sure you cross check and increase the
number of Log file to be used during the activity (LOGPRIMARY = 20 and LOGSECOND =
120).

Note: If you change the value of LOGPRIMARY, then DB2 needs to be restarted in order to
apply the parameter changes which will generate a new log sequence. So, if you don't want

25
to restart DB2 or SAP then it is better to change or increase the value of LOGSECOND which
doesn't requires a restart.
Similarly other Databases have their own procedure of monitoring and increasing the log
files/transaction log which has to be done prior to importing client.

Steps for Client Import Activity in Target system:

 Create new client using SCC4 or use existing client in target system to import the
client exported in above step. Login to existing client or newly created client with
ADMINUSER/SAP*
 Go to STMS. Highlight the transport request for client exports and choose the lorry
icon to import.

26
Choose Import to continue. Choose one of the transport requests of the client transport in
the Transport Management System (TMS). The other transport requests belonging to this
client transport are then automatically added in the correct order. Import these transport
requests into the target

 Manually add "SIDKO00025" transport then "SIDKX00025" then "SIDKT00025" to

TMS buffer
 From the TARGET SYSTEM Transport Queue, Highlight "SIDKO00025" and use
"Request -> Import" to launch import tool.
 Monitor log file updating at OS level "/usr/sap/trans/tmp" dir. for progress info or
from Tcode "AL11"
 After successfully importing the TR's Execute Tcode "SCC7" and performs "Import
post processing activities"
Nothing to fill in here, either start as a background process or start immediately

27
28
Once everything has finished you will see an informational message at the bottom left-hand
screen

Again we can use transaction code SCC3 to view the details, we can see the import was
successful

Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use
transaction code SCC5, select the client to be deleted

29
Deleting client usually took very long time.

30
 Remote Client Copy Client Export/Import
 Remote client copy is done The client export generates transport files,
through RFC and it will not create which can be imported into another system
a transport request thru STMS
 Remote client copy method is not Client data is exported into a file at OS level,
preferred for large client copy. at any given time, the client data is imported
from source to target system.
 Remote client copy does not The export process will generate up to three
require files space at OS level for files at OS level – SIDKO, KT, KX depend on
transports. client profile
 Identical copy cannot be Identical copy can be duplicated at a later
duplicated at a later date. date.
 Automatic repository, consistency No Automatic repository consistency check is
check is performed, if done; need to be done manually using Tcode
inconsistency are detected, the SCC7.
client copy is terminated
 Remote CC cannot be done from OS level
OS level.
Benefits Drawbacks
 The copy is an exact  the version history is
copy of the lost, its might be ok
production system for test systems but
 client-specific not for development
changes are also systems
recorded and copied  the target system
to the target system must be the same
 normal backups are size as the production
Database Copy of the used to avoid system
Production system impacting the  the target system has
production system to be reconfigured
after the copy
 the client structure in
the target system is
lost because its
overwritten with the
client structure from
the source system
 you do not need to  users cannot work in
reconfigure the target both the source or
system target systems during
 the client structure is the execution of a
not overwritten in the client copy, Client-
target system specific objects that
were changed and are
Client Copy with Data not identical in both
systems are not
copied

END

31