SAPclient Administration(2.0)

7/30/2019 SAPclient Administration(2.0)

1/10

SAP SAP R/3 CLIENT ADMINISTRATION

2.0.1-A

1.0 Purpose

To provide a detail Information of Client and Client Management.

2.0 Scope

The procedure covers SAP R/3 Client detail and Client Maintenance.

3.0 System Description :

Refer to Doc 2.0S

4.0 Methodology:

Standard SAP R/3 Clients

SAP delivers SAP R/3 with three standard clients:

o Client 000

o Client 001

o Client 066

4.1 Client 000

4.1.1 It is reserved by SAP to enable the maintenance of the standard SAPR/3 Repository objects and the Baseline Customizing settings in the

system.

4.1.2 It contains the basic Customizing settings with organizational structures

and business parameter settings

4.1.3 It may not be modified or deleted by the customer. It contains noapplication data.

4.2 Client 001

4.2.1 It is a copy of client 000, including the sample organizational structureand configuration, except that customers can modify Client 001.

4.2.2 There is no application data in client 001.


2/10

4.3 Client 066(Early Watch Client)

4.3.1 It is reserved for SAP accesses to its customers' system to perform remote

services such as EarlyWatchand GoingLiveCheck.

4.3.2 it serves as a mechanism to allow remote access for the purpose of system.

This client should not be modified or deleted.

4.4 Create New Client:

This procedure contains following major activities:

4.4.1 Client Copy from the Existing client :

you should use client 001 for client copy. Normally, a copy is made of

client 000. This copy is then used to realize company-specific businessprocesses.

4.4.2 Creating a New Client :You can also create a New Client using SCC4.

4.4.3 Creating Additional Client Roles

It is necessary to define additional clients to fulfill certain needs. These

alternative client roles can include any of the following:

4.4.3.1 Unit test client:

Specialized development client Before you promote Customizingand developments to the quality assurance client, SAP

recommends that you perform unit testing. Unit testing is the

lowest level of testing, where the program or transaction is testedand evaluated for faults.

You can perform unit testing in the client CUST. However, SAPrecommends setting up a unit test client to keep CUST free of

application data.

4.4.3.2 Sandbox client

This client is a used for people who are Customizing SAP R/3 andwant to test their efforts before actually impacting the customizing-

and-development client.

4.4.3.3 End-user training client:

This is an environment for training end users who will be usingSAP R/3 to supply and access production data.


3/10

4.0 MIS Reports:

4.1 No. of clients

4.2 Client Refresh

4.3 Client Modified for QA and PRD

Report to be Maintained

NIL


4/10

Level 3

Defining an SAP R/3 Client

1.0 Purpose: The Procedure gives the work instruction for Client Creation, client

copy, Client Export / Import

2.0 Scope:

3.0 System description

Refer Doc 3.0A

4.0 Work Instruction

Transaction:

SCC4, SCCL, SCC7, SCC8

4.4 Creating a client:

4.4.1 In the Command field, enter transaction SCC4 and choose Enter4.4.2 Choose .

(Figure : 4.4.1)

4.4.3 To continue, choose .

(Figure : 4.4.2)

4.4.4 Select the client number


5/10

4.4.5 Choose New Entries.

(Figure: 4.4.3)

4.4.6 Change View Screen Appears


6/10

(Figure 4.4.4)

An SAP R/3 client is defined by its unique client settings. In addition, you

make selections for all of the following parameters:

4.4.7 Client-Dependent Change Options

The most critical client setting used to define a client is its client-

dependent change option. This option determines whether changes arepermitted in a client and whether the changes are going to be recorded

automatically to change requests.

Figure 4.4.5: The path for determining the appropriate client-dependent

change option

4.4.8 Changes without automatic recording: This setting allows changes to

client-dependent Customizing, but does not automatically record orinclude the changes in change requests.

4.4.9 Automatic recording of changes: This setting allows changes to client-

dependent Customizing settings and automatically includes them in a

change request.

4.4.10 No changes allowed: This setting prevents all users from making client-


7/10

dependent Customizing changes from within the client. This option is

useful for those clients in which Customizing changes do not take place-

that is, clients that are used for testing and training purposes as well asproduction activities.

4.4.11 No transports allowed: This setting allows client-dependent Customizingchanges that will not be promoted either manually or automatically to

other clients. This option can be used to isolate a sandbox client

4.4.12 Client-Independent Change OptionsThe client change options for client-independent attributes protect both

client-independent Customizing and SAP R/3 Repository objects.

i. Changes to Repository and client-independent Customizing

allowed

ii. No changes to client-independent Customizing objects (Changes toRepository objects are still allowed.)

iii. No changes to Repository objects (Changes to client-independent

Customizing are still possible.)

iv. No changes to Repository and client-independent Customizing

objects

All clients in your system landscape-except for the Customizing- and-development client (CUST)-should be assigned the last client-independent

change option, No changes to Repository and client-independent

Customizing objects. The CUST client needs the setting Changes toRepository and client-independent Customizing allowed.

4.4.1 Copy a client on the same system :

1. In the Command field, enter transaction SCCL and choose Enter

On the Client Copy - Copy a Client screen.

a. In Selected profile, choose to select a copy profile that matches your

requirements.

b. In Source client, enter the source client number .

c. If your user masters will be copied from a specific client, in the Sourceclient user masters field, enter this client number

d. You can perform test Run to check the size of the client

e. Choose Schedule as background job.


8/10

On the Schedule Client Copy in Background screen:

f. If you have multiple application servers, in Background server, choose

to select the server on which to run the client copy.

g. Select the server to run the client copy on.

h. Choose .

Choose Schedule job.

Choose Continue. The scheduling proceeds as in scheduling any other

background job.

2. To begin the copy immediately, select Immediate.

3. Choose Check.

4. Choose .5. In Output device, enter the printer name (for example, dcbd).

6. Choose .

7. Choose .8. The displayed message indicates the job was successfully scheduled.

9. Choose .

Tip

If client-independent Customizing takes place in a client, that client shouldalso be used for client-dependent Customizing. Only one client within an

SAP R/3 System should allow for both client-dependent and client-independent Customizing.

Technical Limitations

At a technical level, a client ID is the primary key field in the

Customizing and application tables of the SAP R/3 database. An SAP R/3


9/10

database can house as many clients as you wish-up to a total of 1,000

clients. The required database resources and hardware performance are

largely derived from the number of active users and not from the numberof clients used.

More clients require additional main memory for the SAP R/3 buffers. Asa general rule, an additional 10MB is required for each client under SAP

R/3 Release 4.0B.

Only limited technical maintenance is possible due to increased

availability requirements. Multiple clients within an SAP R/3 System will

have different roles and therefore different end-user demands. Technicalmaintenance, such as reorganizing the database or making an offline

backup, requires the SAP R/3 System to be down and unavailable.

Scheduling of system unavailability is more difficult if the end-user

audience has varying demands.


10/10

Level 4

MIS Reports:

4.1 No. of clients

4.2 Client Refresh4.3 Client Modified for QA and PRD

Server Client Description

DEV 410 SandBox HR

430 Development- ABAP

450 G.M- Consultant

460 Test - DEV

470 Sandbox IT

480 HREL Project

490 SandBox for all End Users

QA 500 Integration Test Client-SD

560 Testing Client HPL(Other)

570 Copy client0-FI

580 HREL

590 Testing-For all

users(Functional Team

Member)

PS1 600 Production Client

610 Pre-Golive

800 Backup client of Productionconfiguration

Client Refresh:

Documents

SAPclient Administration(2.0)