SAP Architecture

SAP Provides Three Layers in the Database

Repository Layer:

These are the standard objects in the Database which are provided by SAP and in the Name space A to
X. SAP Repository Objects such as Fields, Domain, data elements, Tables, Programs, Functional Modules,
Screens, Menus, Transactions in the namespace of A to X can be modified by a Developer upon
obtaining SSCR Key (SAP Software Change Registration Key) from SAP Market Place. Customer can
define their own objects in the namespace y or z

Cross Client Layer(objects):

These are the tables entries in the tables where field 'MANDT' is not available. The Table which does not
contain Field MANDT are called as cross client tables.

Client Specific Layer:

These are the tables entries in the tables where field 'MANDT' is available. The Table which contains
Field MANDT are called as client specific tables.

Client Field is used to segregate the data between clients in the SAP System.

Client Field is a Data separator, and it is the first field to display the data based on logged in Client.

Client and what is the Need for Creating a New Client?

It is an independent business Unit which is represented by three digits(ranges from 000 to 999).it is a
data separator, and it is the first field to login along with user id, password, and language.

sap provides three default clients 000,001,066 with specific purpose.

➢ 000 client provides predefined default templates, scenarios for creating other Clients. it is also
used to apply support packages, patches, add-ons, Languages etc. it is also used to configure the
transport management system. it cannot be used for productive use.
➢ 001 is backup client for 000,but 000 is updated by applying support packs,langs, add- ons etc.
and 001 is outdated with information related to client specific objects and no more treated as a
backup client of 000. (Now 001 can be used for production purposes. Ex: Solution Manager and
Dual Stack ABAP and Java Engines).
➢ 066 is an early watch alert client which is used by SAP to generate EWA Reports for every six
(one)months.

As the sap standard clients(000,001 and 066) could not be used for customizing and development ,there
is a need to create new clients based on the customer requirement.

Client is a 3-digit number in the database Table (T000) which is represented by a field 'MANDT'. Client is
a data separator in the database tables.

The tables with field MANDT are called as client specific tables.(only exception is table T000 because it
maintains client information).The Tables without field MANDT are called as cross client tables.
Client Creation:

Clients are created in Transaction SCC4.

Specify the Number of the Client Unique no(000-999) as 000,001,066 are reserved and the remaining
available client numbers can be used.

• Client Number :(Three-digit number)

• Client Description(specify text)

• Client Location(location of the client)

• Currency:(currency to be used in client)

• Client Role:

• Logical System: To identify the client uniquely in the landscape. it is in the naming convention
<SID>CLNT<CLNT NUMBER>. it is defined in transaction SALE.it is mandatory in BW Systems as the Data
transfer between clients is performed by using logical systems. Logical Systems Names are modified
using BDLS Transaction.

SAP Provides 6 predefined Client Roles:

CUST|TEST|SAND |QTST|TRNG| PROD

DEV System Quality System Production System

Client Specific Options:

These are used to specify whether changes are allowed in the specific client.

a. Changes without Automatic Recording(Changes allowed but not recorded):(Customizing Client

Specific is allowed)

SAND(BOX)Changes are allowed but not recorded in this Client (Facilitate functional team to work on
this client before they work on Cust Client. it is possible to transport the objects if required)

b. Automatic Recording of Changes:

CUST(Customizing): There will be only one client which is set with ARC(Automatic Recording of Changes)
in the SAP System Landscape.

The Changes are allowed and recorded to change request for transporting the changes from one system
to another system in the Landscape. it is also referred as Golden(Master/Parent) Client.

c. No Changes allowed: No Changes are allowed in this 'Client' for Development/Customizing

TEST(ING) Client is only used for Unit Testing, so no changes are allowed. QTST(Quality Testing) is used
for Integration Testing, so no changes are allowed. TRNG(Training Client) is used for training to end
users, so no changes are allowed. PROD(Production Client) is used by end users for Business, so no
changes are allowed.

d. Changes Allowed but not recorded/nor transported:

The Changes are allowed but not recorded nor transported, Test Client may have this option to check
the inputs and modify before CUST.

Cross Client Options:

Changes to Repository Objects and cross client objects are allowed Changes to repository objects
allowed (CCC not allowed)

Changes to cross client objects allowed(REP not allowed)

No changes to Repository Objects and Cross Client Objects are allowed (Production Systems are set with
this option)

Protection Level: it is used to protect the client information from copying and overwriting.

Level 0 : Client Copy is allowed(external availability)/Overwriting is allowed Generally set to customer

Clients

Level 1 :Client Copy is allowed(external availability)/no Overwriting Generally set to SAP Default Client

Level 2: Client Copy is not allowed(no external availability)/no Overwriting Production systems are set
with these options.

Ecatt:(Extended/Electronic Computer aided Test Tool)

SECATT(is allowed to run during Implementation, once the system goes live it is not allowed to RUN. This
is used to massively transfer the data using transaction SECATT(during data upload)
Client creation screen shots:

Go to scc4 T-code

And the click on Display and change

Click on continue

Click on new entries

You select the options according to your client and choose client settings.

And the click on save and then we have to create a logical system for the client, and we have to assign it
to client.

We have to create logical system in BD54 T code

Click on new entries

Logical system format is <SID> CLNT<Client number>

And then click on save

Click on Create Request

Click on Save and the continue

IG4K900008 ➔ TR number
And then assign the created logical system to client in SCC4 T code
done

What happens when Client is Created?

When the Clients are created in SCC4 only an entry in Table T000 is created without any data. it is inbuilt
with a user sap* which is available at kernel level and created as many times as it is deleted with default
password "PASS".
sap* default password is 06071992 and DDIC default password is 19920706 which are overridden by
master passwords provided during installation.(These Passwords remains same for IDES Clients like 800)

Client has access to the cross-client information and repository objects, but it does not contain any
client specific data.

So, in order to get the client specific data a client copy is required from default template client i.e.,
either from '000' or '001'.

During a rollout existing clients can be taken as reference for client copy.

NetWeaver systems like BI/Solman a client copy from 001 is recommended or 001 can be used as
production client. by default, sap* user is disabled in the sap system(for all clients),so enable by setting
the parameter login/no_automatic_user_sapstar=0 and set it to '1' later due to security reasons.

What is Client Copy and client copy Methods?

it is used to copy the client specific data between clients. There are three types of clients copy methods

1.Local Client Copy

2.Remote Client Copy

3.Client export and import

1.Client Copy Local(SCCL): it is used to copy the data between two clients in the same system.

2.Remote Client Copy(SCC9): it is used to copy the data between two clients from two different
systems(the systems are in the landscape and reachable through RFC)

3.Client Export/Import: it is used to Export the client data from one system and transport it to other
systems which are not in the landscape.(if the systems/clients are not reachable through RFC.

Client Description in SAP Environment

Sandbox Client

This client is a general test client and is initially created as a copy of the SAP reference client but is
refreshed periodically with a copy of the quality assurance-testing client. This client is used for
familiarization and testing application and customization functions.

Customizing/Development Client

Customizing settings are made in the customizing/development client (CUST) to create a prototype
system. All application customizing is performed in this client. All system development occurs in this
client according to the business requirements of the CUSTOMER.

Once all the settings have been created, these are transferred to the QA client for testing. The
development changes are then transported using change request transport management system.
Quality Assurance and Testing Client

The configuration from Customizing Client is transported to this client tested and checked. When the
configuration has been thoroughly tested in this client and signed off by the Quality Auditors and Core
Group Members, it will be transported to the Production client.

Training Client

This client is primarily used for user training purpose. The client is pre-configured and contains test data.
Here, the users can run all their transactions and have a feel of the system.

Pre-Production Client

The pre-production client (PPRD) is used for the final testing of the R/3 configuration in the productive
environment. The PPRD is used by the project team to perform final testing of the customizing changes
before they are transferred to the production client. This client can also be used to test data transfer
programs with large amounts of data, in preparation for the final import into the production system.
This configuration allows the entering of master data and transaction data into the production system to
simulate the live environment. This can be deleted.

Production Client

Data transfer procedures will have been tested in the customizing/development testing client and the
pre-production client, with the final run to load the production data being made in the Production client.

The production client is used for its production work once the project goes live. This client contains the
company's live data and the real business processes are performed here.

Distribution of Clients in SAP Systems

The tables below show the distribution of clients in the various SAP systems of landscape.

Development System

Client number Client Description

100 Development /Customizing Client

110 Configuration client

120 Sandbox Client

150 Unit Testing Client

Quality Assurance System

Client number Client Description

220 Testing/Quality Assurance Client

200 End User Training Client(Optional)

Production System

Client number Client Description

900 Production Client

910 Pre-Production Client (Optional)

Client configuration parameters:

Each client is used for specific purpose and has to be configured accordingly. The following are the
configuration parameters for each client.

For Development system: (DEV)

Client Purpose Currency Category Client Client Protected

no Dependent Independent against
settings Settings Overwrite

100 Customizing SAR Customizing Automatic Changes to Yes

recording of repository
changes and client
independent
objects
allowed

120 Sandbox SAR General Changes No Changes Yes

Test client without to repository
automatic and client
recording independent
objects
allowed

150 Unit Testing SAR Testing No Changes No Changes Yes

Client allowed to repository
and client
independent
objects
allowed

220 Quality SAR Integration No Changes No Changes Yes

Assurance testing allowed to repository
and client
Testing independent
objects
allowed
 200 End User SAR Training No Changes No Changes Yes
Training allowed to repository
and client
independent
objects
allowed

➢ The client strategy can be modified as per requirement.

Production system:

Client Purpose Currency Category Client Client Protected

no Dependent Independe against
settings nt Settings Overwrite

900 Production SAR Productive No Changes No Changes Yes

allowed to repository
and client
independent
objects
allowed

Prerequisites of Client Copy:

• It is performed always on the target client

• it always copies/pulls the data from source client

• Check the space in DB02 and ensure that enough space is available for client copy

• Users should not be logged on the source client(lock the users in source client)

• Client copy should be performed in the background mode only and ensure that at least two BTC
processes are available.

• Ensure that all the languages/support packages/add-ons are applied before client copy.

• Identify the space required for client copy using RSTABLESIZE

/RSSPACECHECK(report gives size of current client)

• Define RFC Connection between two clients during Remote Client Copy

• Ensure that /usr/sap/trans directory has enough space to perform client export and write client
copy logs

• Select the profile to specify the data to be copied from Source client to target client.
• Ensure that STMS is Configured in 000 Client

• Client Copy always overwrites(deletes) the data and data merging is not possible.

• it is recommended to delete a client during client refresh In SCC5 and copy from the source
client. Client Deletion Consumes more time in Hours| Days.(example a copy from PRD Client to QAS
client)

• Client Copy logs are displayed in SM37/SCC3/SM50

• The source system and target system version and patch levels should be same to perform client
copy. (It effects in remote client copy and client export and import)

• Multiple Client Copies originating from the same source client is not allowed

Local Client Copy:

Execute SCCL on target System.

Target Client is Displayed Select the Profile

specify the Source Client

schedule as a background job/or start immediately in the dialog mode.

Profile: it specifies the type of data that need to be copied from Source Client.(SAP_CUST is mandatory
profile to setup all the new clients)

SAP_ALL--Copies the Cust, application and user master(to setup training Client) sap_appl--Copies cust
and application

sap_user--only user master sap_cust---only customizing data

Client Copy Copies only the table entries from the source client and paste(copy) them in the same table
with target client.(different MANDT).

The Number of tables will not increase due to a client copy. The entries are copied with a target client
number.

Test run is used to check the resources that are required for client copy.

Remote Client Copy

1. Define RFC Connection between Target Client and Source Client

2. Execute SCC9

3. Select the profile

4.select destination RFC(source system and source client are displayed) 5.schedule as a background job
or run in the dialog mode.

Note: The Source System and Target System should contain the same version and patch levels)
Client Export and Import:

1.Client export is performed using scc8 in the source Client.

2.The Data Files and Co-files are generated in /usr/sap/trans directory. Based on the profile The
Transport Requests like KO-Cross Client Data, KT -Client Specific data and KX- client specific text are
created-->select the profile sap_user/ sap_cust

3.Copy these files to the Target System.

4.Add these files to the import Queue in STMS

5.Import these requests using STMS

6.perform post-client copy activities in SCC7.

Client Refresh:

it is the process of setting up a client with live data from production system for Testing/Training
Purposes. Periodically it is required to set up clients for preproduction/quality assurance/training clients.

Most of the scenarios the Remote client copy is the best method then the local client copy on the
production system(to avoid client settings/accidental client copies in Production).

However, in some of the environments the preproduction client will exist in Production system, but it is
only possible to test client specific scenarios because the Rep and CCC are shared between clients(set to
not modifiable)

It is also recommended to perform DB/System Refresh instead of Client Refresh.

Note: There will be only one client in the production system apart from 000,001 and 066.but it is
possible to have more than one client in the production system.
New Client Copy Tool:
With SAP_BASIS 7.54 (SAP S/4HANA 1909), SAP delivers new client management tools based on new
common architecture. They are a complete redesign of the previous client copy (transactions SCCL,
SCC9, SCC5, …). The new tools replace the old client copy and also offer new functions. They are
optimized for increased performance, process automation and stability. The log of the client copy has
also been completely revised and is now much more meaningful and easier to read, so that
troubleshooting is much easier.

Improvements:
Execution from a third Client. It is no longer necessary to start the client copy in the target client.
Instead, this can now be started in a neutral third client (usually client 000). This increases efficiency and
ensures that no users romp around in the target client during the client copy. The use of the user SAP *
and restart of the application server to enable the user is no longer necessary.

HANA Optimization: The new tool is optimized for use with HANA. Our tests showed that the new Local
Client Copy is about 10x faster than the old tool. The new Remote Copy was up to 5 times faster than
the old tool in our tests. Instead of first loading the data onto the application server for a local copy.

Client Copy Optimizer. The new Client Copy Tool has implemented an optimizer for empty and
unchanged tables. At the beginning of each client copy, the tool reads the HANA database statistics. It
then checks whether a table in the database is completely empty in all clients. If this is the case, this
table can be skipped in the delete and copy phase.
Handling of very large tables

In order to be able to deal with very large database tables, the Client Copy was enhanced to include a
splitter algorithm. This splits very large database tables by generating WHERE conditions, which can then
be copied by different processes in parallel

Renovated Log. Finally, the client copy log (transaction SCC3) was completely revised and replaced by a
clearer solution. The logs are shown in tabs. In addition to the well-known “Client View”, there is now a
“Timeline View” and a view for each copy mode (local copy, remote copy, etc.). Different columns show
the exit status, the table copy status and a general message status. This makes it possible to assess the
success of a client copy at a glance. With SAP_BASIS 756, SCC3 supports the display of the client size
based on the data collected by the Client Size Estimation Tool and the Client Copy Tool.

Task list Support: All of the new copy processes presented here now offer execution via task lists. The
task lists can either be started from the corresponding transaction or directly using transaction STC01

Local Client Copy

The local client copy takes place within a system. The local client copy is started via transaction SCCLN.

Remote Client Copy

The remote client copy copies data from an external system to another client in the target system using
RFC. The process is always started from the target system. The remote client copy is started via
transaction SCC9N.
Client Copy Phases

The new client copy runs in four phases:

1. Initialization Phase
In the first phase the tool initializes the list of all relevant tables, the client lock objects, the exit
handler and many other smaller objects.
2. Analysis Phase
In the second phase, all client copy exits are executed. Exits can exclude certain tables from the
copy, request emptying or even explicitly include tables into the list of tables to be copied.
After all exits finished, the finalized list of tables to be deleted and copied is saved in the
database. If the option to split tables is activated, very large database tables are analyzed for
processing in parallel processes and broken down into smaller work packages.
3. Delete and Copy Phase
The actual deletion and copying process takes place in this phase. First, all tables in the target
client are deleted. The data is then copied from the source client to the target client. After all
tables have been finished the source client gets unlocked.
4. Post Processing Phase
Finally, the postprocessing exits run. Typically, these convert data or generate objects that are
dependent on the data.

The New Client Copy has the following new features:

• Split Large Tables

• Copy Individual Tables
• Simultaneous execution of several client copies in the same system (from SAP_BASIS 756).

Client Deletion

The new client deletion is started via transaction SCC5N. It has the same phases as the client copy. The
client can be deleted directly from the client list (accessible via transaction SCC4) using the “Delete from
System Table T000” setting. In contrast to the old client deletion, the transaction must be started from
another client and no longer from the client to be deleted.

Client Export and Import:

Client export : New T code is SCC8N

Client import post processing : New T code is SCC7N

The old Client Copy Tool previously only allowed exports using transport requests. With SAP_BASIS 755
there is now a further option for exporting to “Client Table Snapshots”. These are saved in the database
of the exporting system and can be imported into the import system via an RFC connection. Compared
to transport requests, the snapshots offer increased performance and greater flexibility in usability. The
list of all snapshots can be viewed in transaction SCC3.
Please note: Exports that were carried out with the old tool are not compatible with the new tool and
vice versa.

Comparison Tool

A new product is delivered with the comparison tool. It allows the comparison of clients, client table
snapshots or client templates in any combination. The Comparison Tool can be used to compare
customizing or entire clients. The comparison tool is started using transaction SCC_COMPARE.

Client Size Estimation:

The Client Size Estimation Tool allows you to estimate the size of individual tables or an entire client.

The Client Size Estimation Tool is started using transaction SCC_CLIENT_SIZE.

As of SAP_BASIS 756, the Client Size Estimation Tool runs automatically with every client copy. The size
of all clients can then be checked in transaction SCC3

Continued…
Process/Tasks Old Transaction New Transaction Task list ( T code: STC01) Released with
Local Client Copy SCCL SCCLN SAP_CLIENT_COPY_LOCAL SAP_BASIS 754 SP00
Remote Client Copy SCC9 SCC9N SAP_CLIENT_COPY_REMOTE SAP_BASIS 754 SP01
Client Deletion SCC5 SCC5N SAP_CLIENT_DELETION SAP_BASIS 754 SP00
Client Export SCC8 SCC8N SAP_CLIENT_EXPORT SAP_BASIS 754 SP02
Client Import SCC7 SCC7N SAP_CLIENT_IMPORT_POSTPROCESSING SAP_BASIS 754 SP02
Client Copy Log SCC3 SCC3 n/a SAP_BASIS 754 SP01
Client Copy – Special
Selection SCC1 SCC1N SAP_CLIENT_COPY_BY_TRANSPORT SAP_BASIS 755 SP01
Comparison Tool N/A SCC_COMPARE SAP_CLIENT_COMPARISON SAP_BASIS 754 SP03
Client Size
Determination N/A SCC_CLIENT_SIZE – SAP_BASIS 754 SP00