0% found this document useful (0 votes)
35 views20 pages

Client Adminstration

Uploaded by

sdprotiviti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views20 pages

Client Adminstration

Uploaded by

sdprotiviti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Page 1

Client Administration
 Client is an independent business entity which has its own data.
 SAP provides a predefined client with default settings that are necessary to customize a company
 The default settings are defined by getting Business requirements from various customers
 Client is an field in DB represented by MANDT (MANDANT is nothing but client in German language)
 All the clients’ details are stored in T000 table
 We can create up to 1000 clients ranging from 000 to 999 (because client field contains 3 digits only)
 Right after installation of SAP, we will get some default clients, those are
In IDES 800, 810, 811, 812, in Non IDES 000, 001, 066
000 client
It is a default client provided by SAP.
It consists of templates which can be customized according to customer requirements
As this is a standard client, SAP recommends not to work / perform any customizing, but this is used to
apply Support Packages, Patches, Language imports, correction transports & Notes
This is to ensure that 000 is continuously updated and stands as a template for other clients in the system

001 client
During the initial stages of SAP implementation, people use to customize 000 client
001 is created as a copy of 000
001 is a backup client of 000 and used to restore 000 in case of any changes
But the purpose is completely deviated because 000 is continuously updated by applying support packages,
Notes, Patches etc
So 001 is outdated and cannot be used to restore unless we perform client compare & adjust settings from
000 to 001

066 client (Early watch client)


It is used by SAP to logon to customer systems (yearly twice) and generate early watch reports
This client is also used by SAP to recommend the fine tunings to optimize the performance of Production
system

 When a client is created an entry in table T000 is created with a user ‘sap*’ and password ‘pass’
 Logon to newly created client using the standard user sap* password pass
Note: sap* does not exists in user master records, it is a kernel level user

1
Page 1 of 37
Page 2
Client Roles or Client Strategy:
 The first client which needs to be created in the Development system is “Master client / Golden client /
Parent client / Customizing client”
 This is the only client where the changes are performed in the complete landscape. The changes are
performed in this client are carried forward to other clients in the Landscape.

Client Client-specific Cross-client object Protection


type objects changes level CATT & eCATT Restrictions
Changes to
Automatic Repository and
Golden recording of cross-client
Client changes are Customizing
[CUST] allowed allowed 0 CATT & eCATT allowed
Changes
without
Sand box automatic No changes are
[SAND] recording allowed 0 CATT & eCATT allowed

Changes
Testing allowed or No
client changes No changes are
[TEST] allowed allowed 0 CATT & eCATT allowed

Quality
testing No changes , No changes are
[QTST] No recording allowed 0 CATT & eCATT allowed

Pre-
Production No changes , No changes are
[PRED] No recording allowed 2 CATT & eCATT not allowed

Production No changes , No changes are


[PROD] No recording allowed 2 CATT & eCATT not allowed

SAND box:
It is used to perform Customizing by functional consultants
The changes are not carried forward
Developers are not allowed to work on this box, because they always work with customer or SAP repository
objects

Testing client:
It is used to test the objects that are developed in CUST client
The changes are carried forward using transaction SCC1, but the change request should not be released

Quality testing:
The changes which are performed either client specific, repository, cross-client are imported in to quality
system to perform integration, consolidation, quality testing, stress, load testing
Some functional data is loaded to test the scenarios
This is only the client in the Landscape which signals the object movement into PROD
If the object/changes is not approved it will not be moved further in the Landscape

2
Page 2 of 37
Page 3

Training Client:
It is used by the service provider to train the end users of the company

Pre-Production & Production clients:


Pre-Production is an environment where changes will be moved from quality before moving in to
Production
Mostly client-specific changes are moved
Changes are not allowed in client specific, cross-client & repository, CATT
It is highly protected and even eCATT is disabled

Summary:
It is recommended to perform changes in only one client and move them strategically in the landscape
If not the system will be inconsistent with various versions
By using this options version management is maintained in one system

Local client copy profiles


SAP_ALL All Client-Specific Data w/o Change Documents
SAP_APPL Customizing and Application Data w/o Change Docs
SAP_APPX SAP_APPL w/o Authorization Profiles and Roles
SAP_CUST Customizing
SAP_CUSV Customizing and User Variants
SAP_CUSX Customizing w/o Authorization Profiles and Roles
SAP_PROF Only Authorization Profiles and Roles
SAP_UCSV Customizing, User Master Records and User Variants
SAP_UCUS Customizing and User Master Records
SAP_UONL User without Authorization Profiles and Roles
SAP_USER User Master Records and Authorization Profiles

Client Export profiles


SAP_ALL All Client-Specific Data w/o Change Documents
SAP_CUST Customizing
SAP_CUSV Customizing and User Variants
SAP_CUSX Customizing w/o Authorization Profiles and Roles
SAP_EXBC Customizing, Users and Cross-Client Customizing
SAP_EXPA SAP_ALL with Cross-Client Customizing
SAP_EXPC Customizing Including Cross-Client Customizing
SAP_PROF Only Authorization Profiles and Roles
SAP_RECO Recovery (Only if Source Client = Target Client)
SAP_UCSV Customizing, User Master Records and User Variants
SAP_UCUS Customizing and User Master Records
SAP_UONL User without Authorization Profiles and Roles
SAP_USER User Master Records and Authorization Profiles
Client Related T_Codes
SCC1 – Local Client Transport
SCCL – Local Client Copy

3
Page 3 of 37
Page 4
SCC3 – Client Copy / Transport Log analysis
SCC4 – Client Creation
SCC5 – Client Deletion
SCC7 – Post Client Import Actions
SCC8 – Client Export
SCC9 – Remote Client Copy
SCU0 – Client Comparison

Function Modules Related to Client

Use T_Code SE37 to run below programs

SCCR_LOCK_CLIENT To Lock Client


SCCR_UNLOCK_CLIENT To Unlock Client
SCCR_PERFORM_SCC1
SCCR_CLOSE_CLIENTCOPY To terminate client copy

When SAP is installed it comes in 3 layers

Client-Specific objects / Data

Cross-client Data

Repository objects

Client-Specific Data:
This data will be specific to that particular client
Client specific data contains
1) User master data
2) Customizing data
3) Application data
4) Transaction data
The client specific changes reflects only in that client
Ex: PFCG, SU01

Cross-Client data:
It has measurements, Time settings, calendars
These objects will be accessed by all the clients
If we modified Cross-client data it reflects in all clients
Ex: SALE (Logical systems), SM59 (RFC Connections)

Repository Objects:
It has programs, function modules, screens etc
Table TADIR is used to view the repository objects
These are of SAP standard and by default all the objects are locked for editing (ex: TADIR, TSTC)

4
Page 4 of 37
Page 5

Client Creation:
As we cannot work with the default clients provided by SAP, we need to create our own clients and
perform customizing
 We can create up to 1000 clients ranging from 000 to 999 (000, 001 and 066 are defaults clients)
 Login to the newly created clients with the user sap* and password pass

The settings of the client:


Client: Number of the client
City: City of the client
Logical system: Logical system of the client (naming convention is <SID>CLNT<client-number>)
Std currency: currency of the country, which client belongs to (Ex: INR for Indian Rupees)
Client Role: The type of work that is going to be performed on that client
Given values are: Production
Test
Customizing
Demo
Training/Education
SAP reference
Changes and transports for client-specific objects:
Given options are:
Changes without automatic recording
Automatic recording of changes (default value)
No changes allowed
Changes w/o automatic recording, no transports allowed
Cross-client objects changes:
This is used to set the client whether repository & cross-client objects can be changed
Given options are:
Changes to Repository and Cross-client customizing allowed (default value)
No changes to Cross-client customizing objects
No changes to Repository objects
No changes to Repository and Cross-client customizing objects
Protection: client copier and comparison tool
It is used to set the properties for the client, whether client copy is allowed and client comparison is
allowed
Ex: the production system is not allowed for client copy and even client comparison
Given options are:
Protection level 0: No restriction (default value)
Protection level 1: No overwriting
Protection level 2: No overwriting, no external availability
CATT and eCATT Restrictions:
Computer Aided Testing Tool to upload the data into SAP system
Given options are:
eCATT and CATT Not allowed (default value)
eCATT and CATT Allowed
eCATT and CATT only allowed for ‘Trusted RFC’
eCATT Allowed, but FUN/ABAP and CATT not allowed
eCATT allowed, but FUN/ABAP and CATT only for ‘Trusted RFC’
Restrictions:
Locked due to client copy (by default it is deactivated)
Protection against SAP upgrade

SCC4-Client Creation Santosh Bandari


Page 5 of 37
Page 6

 Hit the T_Code SCC4

 Click on Change icon or press Ctrl+F1

 It gives the information, click on Continue icon

 Click on New Entries button or press F5

Page 6 of 37
Page 7

 Give client number, Client name, City, Currency and Role & select remaining options as per our
requirement

 Click on Save button or press Ctrl+S

 Data will be saved

Page 7 of 37
Page 8

 Click on Back button or press F3

 It shows the newly created client in the list

Page 8 of 37
Page 9
Client deletion (Foreground)

Whenever client is deleted no tables are deleted, only table entries where client no=<deleted client> are deleted

 Login in the client which you want to delete

 Hit the T_Code SCC5

 Check Delete entry from T000 option & click on start immediately button

 Click on Continue button or press Enter

Page 9 of 37
Page 10
 After taking around two hours time it displays as shown below

 Click on Log Display button

Page 10 of 37
Page 11
 Double click on our job

 It displays all the details like start time, end time, and other statistics

 Hit the T_Code SCC4 to see whether the client 143 is still existed or not

 Here the client 143 does not exists, that means deleted successfully

Page 11 of 37
Page 12
Client Deletion (background)

 Login in the client which you want to delete

 Hit the T_Code SCC5

 Check Delete entry from T000 option & click Delete in background button

 Press F4 or click on as shown below

 Double click on server name

 Check immediately option & click Schedule job button

Page 12 of 37
Page 13
 Click Continue button

 Click Continue button

 Hit the T_Code SCC3 to see log analysis

 Double click on our job

Page 13 of 37
Page 14
 It displays the log analysis of client deletion, here status is processing…

 After taking some time Status become successfully completed

 Hit the T_Code SCC4 to view whether the client is still exists or not

 Here the client 143 does not appears, that means deleted successfully

Page 14 of 37
Page 15
Client Lock:
 Hit the T_Code SE37

 Give function module SCCR_LOCK_CLIENT & Press F8

 Click on Execute button or press F8

 Give the client number which you want to lock & Click on Save button

Page 15 of 37
Page 16
 Client locked successfully

 Now try to login with locked (800) Client, It gives below information

Page 16 of 37
Page 17

Client Unlock:
Method 1:

 Hit the T_Code SE37

 Give function module SCCR_UNLOCK_CLIENT & Press F8

 Click on Execute button or press F8

 Give the client number which you want to lock & Click on Save button

Page 17 of 37
Page 18

 Client unlocked successfully

 Now try to login with unlocked (800) Client

 Login successfully, that means client unlocked successfully

Page 18 of 37
Page 19
Method 2:

 Hit the T_Code SCC4

 Click on Change button

 Press Enter

 Double click on client which you want to unlock

Page 19 of 37
Page 20

 Uncheck “Locked due to client copy” option

 Click on Save button or press Ctrl+S

 Client unlocked successfully

Page 20 of 37

You might also like