System and Client Settings

One-System Landscape
Each client has a different setting according to its role within the system. This setting can, however, vary due to the special requirements of a one-system landscape during the course of the project.

System Setting
The system change options define the customizing and development functions in an SA System. These settings serve as a !asis upon which the client settings are structured. "ater in this document, you will find more detailed information on how the individual clients are set up. #or the one-system landscape, the system change options are set as follows$ System Settings in the One-System Landscape

SAP System roduction system % &'(

Options All o!jects )with Transport *rganizer+

The system change option setting allows you to ma,e any changes to all o!jects in the production system. This means that you must adhere strictly to the default configuration of the clients.

PRD Client Settings

The client settings define the customizing and development functions in the SA System. These settings do not override the system change options. The following graphic displays a client in detail, using the customizing and development client -.. as an e/ample$ )0y default you cannot ma,e changes to cross-client o!jects in this client as it is loc,ed. The loc, must only !e removed temporarily for cross-client changes.+

Description of the Clients in the Production System PRD

000: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client

This client is used to set up new 1neutral 1 clients !y client copy.

'o not change or delete client ... or client ..2. 00: C!S": Customi#ing and de$elopment client All changes are automatically recorded and stored in change requests in client 34ST )-..+. This client is also used for developing programs. 3ross-client customizing is only allowed in this client. 5ou must not create any test data or carry out any tests. At the end of this phase you must release all cross-client requests.

0y default, changes to cross-client o!jects are prevented in this client !y a loc,. *nly remove the loc, temporarily for cross-client changes. 5ou must remem!er that these changes directly affect all other clients. 10: SA%D: &Sand'o(& practice client This client is used for getting to ,now the system, trying out applications or testing customizing functions. 5ou can carry out client-specific customizing in this client. 3hanges are not recorded. Any changes that you ma,e in this client and that you want to ,eep in your system have to !e repeated manually in the client 34ST )-..+. This client can !e updated !y the administrator at any time using a client copy from 34ST )-..+. )00: *"S": Reference client for integration and training This client has two uses. 6t is used to chec, the customizing and development changes !efore the integration test, and to set up the training client T&78 )92.+ !efore training, to ensure that all training sessions !egin with the same conditions. 6n this client you cannot ma,e changes to &epository o!jects or e/ecute cross-client customizing. The function for changing client-specific o!jects is also deactivated in this client. )10: "R%+: "raining client This client is used for training the end user. This client contains master and transaction data to ensure that training is as realistic as possi!le. 7either development nor clientspecific customizing is allowed. The function for changing client-specific o!jects is also deactivated in this client.

Setting T&78 using client copy leads to all master and transaction data !eing lost. 4se Transaction SCC1 to transport change requests. ,00: PROD: Production client

This is the production client for your company. 5ou cannot e/ecute any client-specific customizing settings, nor ma,e any changes to &epository o!jects. ,10: PPRD: Preproduction client 6ntegration testing is e/ecuted in this client. Testing can !egin using master and transaction data that was transferred from the old system. 6n the preproduction client, you cannot ma,e changes to &epository o!jects or e/ecute cross-client customizing. The function that allows you to change client-specific o!jects is similarly deactivated. 0--: .arly /atch Client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 5ou must not change or delete this client. Client Settings in the Production System 0PRD1 213

Settings

0004001

C!S" 2 003 3hanges automatically recorded 7o changes to &epository or customizing, if necessary, open temporarily for changes

SA%D 2 103 3hanges without automatic recording 7o changes to &epository or customizing

*"S" 2)003 7o changes allowed

3hanges to client- 7o changes specific o!jects allowed

3hanges to cross- 7o changes to client o!jects &epository or customizing

7o changes to &epository or customizing

3lient copy protection 3lient role

rotection level 2$ rotection level 2$ rotection level .$ rotection level .$ 7o overwriting 7o overwriting 7o restriction 7o restriction SA reference 3ustomizing: development ractice client Test

Client Settings in the Production System 0PRD1 2 3

Settings

"R%+ 2)103

PROD 2,003 7o changes allowed

PPRD 2,103 7o changes allowed

0-7o changes allowed

3hanges to client- 7o changes specific o!jects allowed

3hanges to cross- 7o changes to client o!jects &epository or 3ustomizing 3lient copy protection 3lient role

7o changes to &epository or 3ustomizing

7o changes to &epository or 3ustomizing

7o changes to &epository or 3ustomizing

rotection level .$ rotection level 2$ rotection level 2$ rotection level 2$ 7o restriction 7o overwriting 7o overwriting 7o overwriting Training roduction 6ntegration 6ntegration test SA Early ;atch

Client Setup
The following graphic outlines the setup of clients !y client copy or transports in this one-system landscape.

Client Setup in PRD

All clients in the production system % &'( are set up after the system is installed !y client copy from client .... The clients SA7' )-2.+ and T&78 )92.+ are also set up again, if necessary. The system administrator does this with client copy )Transaction SCCL +. #or e/ample, !efore the start of end user training, you can initialize the training client T&78 )92.+ again using a client copy of client <TST )9..+, so that each training session is !rought up to an identical point.

The following ta!le gives an overview$ Client Setup in 0PRD1 'y the System Administrator !sing Client Copy

SAP System % &'(

Source client 34ST )-..+ <TST )9..+

"arget client SA7' )-2.+ T&78 )92.+

Reason 6nitial client setup 6nitial client setup

"ime As needed As needed

Reference 2 -

The two clients <TST )9..+ and T&78 )92.+ are then also supplied with the customizing changes e/ecuted in client 34ST )-..+. After each unit of wor,, each project wor,er who has made customizing changes copies those changes to !oth clients )Transaction SCC1 +. Client Setup in 0PRD1 'y Pro5ect /or6ers 7ith "ransport Re8uests

SAP System % &'(

Source client 34ST )-..+

"arget client <TST )9..+ T&78 )92.+

Reason 3ustomizing 3ustomizing

"ime As needed As needed

Reference A 0

The production client &*' )=..+ and the preproduction client system is installed !y client copy from client ....

&' )=2.+ are set up after the

The tested transport requests, the customizing changes and the developments from client 34ST )-..+ are imported into client &' )=2.+, as outlined in the ta!le a!ove. The integration test ta,es place in client &' )=2.+. After completion of integration testing, the production client &*' )=..+ is also supplied with the transport requests from client 34ST )-..+.

'o not delete any files in ...\TRANS\DATA or ...\TRANS\COFILE during the project phase. These files contain information and data for the import process. The ta!les !elow give another overview of transporting change requests in the one-system landscape. The system administrator performs the transports. 6f transports are to !e made into the preproduction client &' )=2.+, then the project manager has to release the requests. Transports into the production client &*' )=..+ are made after a successful integration test. "ransport of Change Re8uests in a One-System Landscape

Source system

"arget system Reason "ime Reference '

SAP System SAP System "arget client % &'( % &'( &' )=2.+

3ustomizing and 6ntegration test developments 3ustomizing and After successful developments integration test

&*' )=..+

System and Client Settings in a "7o-System Landscape

Each system has a specific role within the system landscape and there is a configuration for each role. As well, each client in a system has its own settings.

System Settings
The system change option settings defines the availa!le 3ustomizing and development functions in an SA System. These settings are the !asis on which the client settings are !uilt. The following sections give you detailed information on the configuration of the individual clients. 6f you own a &eady-to-&un system, the system change options for the development or production system are set according to the following ta!les. 6f you do not own a &eady-to-&un system, we recommend configuring your system according to these settings. System Settings in a "7o-System Landscape

SAP System 'evelopment system %'E>( roduction system % &'(

Options All o!jects )with Transport *rganizer+ *!jects cannot !e modified

Client Settings for D.9

The client settings define the 3ustomizing and development functions in the SA System. These settings do not override the system change option. O$er of Client Settings in the De$elopment System 0D.91 2"7o-System Landscape3

Description of Clients in the De$elopment System D.9 2"7oSystem Landscape3

000: SAP standard client

This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client This client is used to set up new 1neutral 1 clients !y client copy. 'o not change or delete client ... or client ..2. 00: C!S": Customi#ing and de$elopment client All changes are automatically recorded and stored in change requests in client 34ST )-..+. This client is also used for developing programs. 3ross-client customizing is only allowed in this client. 5ou must not create any test data or perform any tests. 10: SA%D: Sand'o( client This client is used for getting to ,now the system, trying out applications or testing customizing functions. 5ou can perform client-specific 3ustomizing in this client. 3hanges are not recorded. Any changes that you ma,e in this client and that you want to ,eep in your system have to !e repeated manually in the client 34ST )-..+. The administrator can update this client at any time using a client copy from 34ST )-..+. )00: *"S": Reference client for integration and training This client has two uses. 6t is used to chec, the customizing and development changes !efore the integration test, and to set up the training client T&78 )92.+ !efore training to ensure that all training sessions !egin with the same conditions. 6n this client you cannot ma,e changes to &epository o!jects or e/ecute cross-client customizing. The function for changing client-specific o!jects is also deactivated in this client. )10: "R%+: "raining client This client is used for training the end user. This client contains master and transaction data to ensure that training is as realistic as possi!le. 'evelopment and client-specific 3ustomizing is not allowed. The function for changing client-specific o!jects is also deactivated in this client. Setting T&78 using client copy leads to all master and transaction data !eing lost. 4se Transaction SCC1 to transport change requests. 0--: .arly/atch client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 5ou must not change or delete this client. 'o not change or delete this client. Client Settings in the De$elopment System 0D.91 213

Settings 3hanges to clientspecific o!jects

000 7o changes allowed

001 7o changes allowed

C!S" 2 003 3hanges are automatically recorded

SA%D 2 103 3hanges are automatically recorded

3hanges to crossclient o!jects

7o changes to &epository or 3ustomizing

7o changes to &epository or 3ustomizing

3hanges allowed 7o changes to to &epository and &epository or cross-client 3ustomizing 3ustomizing rotection level 2$ 7o overwriting 3ustomizing: development rotection level .$ 7o restrictions Sand!o/ client

3lient copy protection

rotection level 2$ 7o overwriting

rotection level 2$ 7o overwriting SA &eference

3lient role

SA &eference

Client Settings in the De$elopment System 0D.912 3

Settings

*"S" 2)003

"R%+ 2)103 7o changes allowed

0-7o changes allowed

3hanges to client-specific 7o changes allowed o!jects

3hanges to cross-client o!jects

7o changes to &epository or 3ustomizing rotection level .$ 7o restrictions Test

7o changes to &epository or 3ustomizing rotection level .$ 7o restrictions Training

7o changes to &epository or 3ustomizing rotection level 2$ 7o overwriting SA Early;atch

3lient copy protection

3lient role

Client Settings for PRD 2"7o-System Landscape3

The following clients are created in the production system$

Description of Clients in the Production System PRD 2"7o-System Landscape3

000: SAP standard client

This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client This client is used to set up new 1neutral 1 clients !y client copy. 'o not change or delete client ... or client ..2. ,00: PROD: Production client This is the production client for your company. 5ou cannot e/ecute any client-specific 3ustomizing settings, nor ma,e any changes to &epository o!jects. ,10: PPRD: Preproduction client 6ntegration testing is e/ecuted in this client. Testing can !egin using master and transaction data that was transferred from the old system. 6n the preproduction client, you cannot ma,e changes to &epository o!jects or e/ecute cross-client 3ustomizing. The function that allows you to change client-specific o!jects is similarly deactivated. 0--: .arly/atch client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 5ou must not change or delete this client. 'o not change or delete this client. The following ta!le gives an overview of client settings in the production system % &'(. Client Settings in the Production System 0PRD1

Settings 3hanges to clientspecific o!jects

000 4 001 7o changes allowed

PROD 2,003 7o changes allowed

PPRD 2,103 7o changes allowed

0-7o changes allowed

3hanges to crossclient o!jects

7o changes to &epository or 3ustomizing rotection level 2$ 7o overwriting

7o changes to &epository or 3ustomizing rotection level 2$ 7o overwriting

7o changes to &epository or 3ustomizing rotection level 2$ 7o overwriting reproduction client 6ntegration test

7o changes to &epository or 3ustomizing rotection level 2$ 7o overwriting SA Early;atch

3lient copy protection

3lient role

SA &eference

roduction

Client Setup
The following graphic outlines the setup of clients !y client copy or transports in this two-system landscape$

Client Setup in D.9

All clients in the production system % &'( are set up after the system is installed !y client copy from client .... The clients SA7' )-2.+ and T&78 )92.+ are also set up again, if necessary. The system administrator does this with client copy )Transaction SCCL +. #or e/ample, !efore the start of end user training, you can initialize the training client T&78 )92.+ again using a client copy of client <TST )9..+, so that each training session has identical starting conditions. The following ta!le gives you an overview. Client Setup in 0D.91 !sing Client Copy 'y the System Administrator

SAP System %'E>(

Source Client "arget Client 34ST )-..+ <TST )9..+ SA7' )-2.+ T&78 )92.+

Reason 3lient setup 3lient setup

"ime As needed As needed

Reference 2 -

The two clients <TST )9..+ and T&78 )92.+ are then also supplied with the customizing changes e/ecuted in client 34ST )-..+. After each unit of wor,, each project team mem!er who has made customizing changes copies those changes to !oth clients )Transaction SCC1 +. Client Setup in 0D.91 !sing "ransport Re8uests 'y the Pro5ect "eam :em'ers

SAP System %'E>(

Source Client 34ST )-..+

"arget Client Reason <TST )9..+ T&78 )92.+ 3ustomizing 3ustomizing

"ime As needed As needed

Reference A 0

Client Setup in PRD

The production client &*' )=..+ and the preproduction client system is installed !y client copy from client .... &' )=2.+ are set up after the

The tested transport requests, the customizing changes and the developments from client 34ST )-..+ are imported into client &' )=2.+, as outlined in the ta!le a!ove. The integration test occurs in client &' )=2.+. After completing integration testing, the production client &*' )=..+ is also supplied with the transport requests from client 34ST )-..+ of the development system %'E>(.

'o not delete any files in ...\TRANS\DATA or ...\TRANS\COFILE during the project phase. These files contain information and data for the import process. The ta!les !elow give another overview of transporting change requests in the two-system landscape. The system administrator performs the transports. 6f transports are to !e made into the preproduction client &' )=2.+, then the project manager has to release the requests. Transports into the production client &*' )=..+ are made after a successful integration test. "ransporting Change Re8uests in a "7o-System Landscape

Source System SAP System

"arget system "arget Client Reason "ime Reference

Source Client SAP System 34ST )-..+ % &'(

%'E>(

&' )=2.+

3ustomizing 6ntegration ? test development 3ustomizing After ? successful development integration

%'E>(

34ST )-..+

% &'(

&*' )=..+

'

test

System and Client Settings in a "hree-System Landscape

Each system has a specific role within the system landscape and there is a configuration for each role. As well, each client in a system has its own settings.

System Settings
The system change option settings defines the availa!le 3ustomizing and development functions in an SA System. These settings are the !asis on which the client settings are !uilt. The following sections give you detailed information on the configuration of the individual clients. 6f you own a &eady-to-&un system, the system change options for the development or production system are set according to the following ta!les. 6f you do not own a &eady-to-&un system, we recommend configuring your system according to these settings. System Settings in a "hree-System Landscape

SAP System 'evelopment system %'E>( <uality assurance system %<AS( roduction system % &'(

Options All o!jects )with Transport *rganizer+ *!jects cannot !e modified *!jects cannot !e modified

Client Settings for D.9

The client settings define the 3ustomizing and development functions in the SA System. These settings do not override the system change option.

Description of Clients in the De$elopment System D.9 2"hreeSystem Landscape3

000: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete client ... or client ..2. 00: C!S": Customi#ing and de$elopment client

All changes are automatically recorded and stored in change requests in client 34ST )-..+. This client is also used for developing programs. 3ross-client customizing is only allowed in this client. 5ou must not create any test data or perform any tests. 10: SA%D: Sand'o( client This client is used for getting to ,now the system, trying out applications or testing customizing functions. 5ou can perform client-specific 3ustomizing in this client. 3hanges are not recorded. Any changes that you ma,e in this client and that you want to ,eep in your system have to !e repeated manually in the client 34ST )-..+. The administrator can update this client at any time using a client copy from 34ST )-..+. 0--: .arly/atch client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 5ou must not change or delete this client. 'o not change or delete this client. The following ta!le gives an overview of client settings in the development system %'E>($ Client Settings in the De$elopment System 0D.91 213

Settings 3hanges to clientspecific o!jects

000 7o changes allowed

001 7o changes allowed

C!S" 2 003 3hanged are automatically noted

SA%D 2 103 3hanged are not automatically noted

3hanges to crossclient o!jects

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

3hanges allowed 7o changes to to &epository and &epository and cross-client 3ustomizing 3ustomizing rotection level 2$ 7o overwriting 3ustomizing: development Sand!o/ client rotection level .$ 7o restrictions

3lient copy protection

rotection level 2$ 7o overwriting

rotection level 2$ 7o overwriting SA &eference

3lient role

SA &eference

Client Settings in the De$elopment System 0D.912 3

Settings

0--

3hanges to client-specific o!jects

7o changes allowed

3hanges to cross-client o!jects

7o changes to &epository and 3ustomizing

3lient copy protection

rotection level 2$ 7o overwriting SA Early;atch

3lient role

Client Settings for *AS

The client settings define the 3ustomizing and development functions in the SA System. These settings do not override the system change option.

Description of Clients in the *uality Assurance System *AS 2"hree-System Landscape3

000: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete client ... or client ..2. )00: *"S": Reference client for integration and training This client has two uses. 6t is used to chec, the customizing and development changes !efore the integration test, and to set up the training client T&78 )92.+ !efore training to ensure that all training sessions !egin with the same conditions. 6n this client you cannot ma,e changes to &epository o!jects or e/ecute cross-client customizing. The function for changing client-specific o!jects is also deactivated in this client. )10: "R%+: "raining client This client is used for training the end user. This client contains master and transaction data to ensure that training is as realistic as possi!le. 'evelopment and client-specific 3ustomizing is not allowed. The function for changing client-specific o!jects is also deactivated in this client.

Setting T&78 using client copy leads to all master and transaction data !eing lost. 4se Transaction SCC1 to transport change requests. 0--: .arly/atch client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 'o not change or delete this client. The following ta!le gives an overview of client settings in the quality assurance system %<AS($ Client Settings in the *uality Assurance System 0*AS1 213

Settings

000

001 7o changes allowed

3hanges to client-specific o!jects 7o changes allowed

3hanges to cross-client o!jects

7o changes to &epository and 7o changes to &epository and 3ustomizing 3ustomizing

3lient copy protection

rotection level 2$ 7o overwriting SA &eference

rotection level 2$ 7o overwriting SA &eference

3lient role

Client Settings in the *uality Assurance System 0*AS1 2 3

Settings

*"S" 2)003

"R%+ 2)103 7o changes allowed

0-7o changes allowed

3hanges to client-specific 7o changes allowed o!jects

3hanges to cross-client o!jects

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

3lient copy protection

rotection level .$ 7o rotection level .$ 7o rotection level 2$ restrictions restrictions 7o overwriting Test Training SA Early;atch

3lient role

Client Settings for PRD 2"hree-System Landscape3

The following clients are created in the production system$

Descriptions of Clients in the Production System PRD

000: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete this client. 001: SAP standard client This client is used to set up new 1neutral1 clients !y client copy. 'o not change or delete client ... or client ..2. ,00: PROD: Production client This is the production client for your company. 5ou cannot e/ecute any client-specific 3ustomizing settings, nor ma,e any changes to &epository o!jects. ,10: PPRD: Preproduction client 6ntegration testing is e/ecuted in this client. Testing can !egin using master and transaction data that was transferred from the old system. 6n the preproduction client, you cannot ma,e changes to &epository o!jects or e/ecute cross-client 3ustomizing. The function that allows you to change client-specific o!jects is similarly deactivated. 0--: .arly/atch client This client is purely a service client that ena!les SA to access remotely the customer system with regard to analyzing errors and performance. 'o not change or delete this client. The following ta!le gives an overview of the client settings in the production system % &'( Clients Settings in the Production System 0PRD1

Settings 3hanges to clientspecific o!jects

000 4 001 7o changes allowed

PROD 2,003 7o changes allowed

PPRD 2,103 7o changes allowed

0-7o changes allowed

3hanges to crossclient o!jects

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

7o changes to &epository and 3ustomizing

3lient copy protection 3lient role

rotection level 2$ rotection level 2$ rotection level 2$ rotection level 2$ 7o overwriting 7o overwriting 7o overwriting 7o overwriting SA &eference roduction reproduction client 6ntegration test SA Early;atch

Client Setup
The following graphic outlines the setup of clients !y client copy or transports in this three-system landscape$

Client Setup in D.9

All clients in the production system % &'( are set up after the system is installed !y client copy from client .... The clients SA7' )-2.+ and T&78 )92.+ are also set up again, if necessary. The system administrator does this with client copy )Transaction SCCL +. The following ta!le gives you an overview. Client Setup in 0D.91 !sing Client Copy 'y the System Administrator

SAP System

Source Client "arget Client

Reason

"ime

Reference

%'E>(

34ST )-..+

SA7' )-2.+

3lient setup

As needed

Client Setup in 0*AS1

All the clients in the quality assurance system %<AS( are set up after the system is installed !y client copy from client ... from the SA standard client .... The client T&78 )92.+ are also set up again, if necessary. The system administrator does this with client copy )Transaction SCCL +. #or e/ample, !efore the start of end user training, you can initialize the training client T&78 )92.+ using a client copy of client <TST )9..+, so that each training session has identical starting conditions. The following ta!le gives you an overview. Client Setup in 0*AS1 !sing Client Copy 'y the System Administrator

SAP System %<AS(

Source Client <TST )9..+

"arget Client T&78 )92.+

Reason 3lient setup

"ime As needed

Reference -

0oth <TST )9..+ and T&78 )92.+ are also supplied with the 3ustomizing changes and developments made in client 34ST )-..+ in %'E>(. After each unit of wor,, each project team mem!er releases the request in %'E>(. The system administrator transports the e/ported request into client <TST in %<AS( and after successful testing it is forwarded into client 92. in %<AS(. Supplying Clients in 0*AS1 !sing "ransport Re8uests 'y the System Administrator

Source System SAP System Source Client %'E>( 34ST )-..+

"arget System SAP System %<AS( "arget Client <TST )9..+ Reason "ime Reference

3ustomizing As needed A )Transport+ ? 'evelopment

%'E>(

34ST )-..+

%<AS(

T&78 )92.+ 3ustomizing As needed 0 ? )#orwarding+ 'evelopment

Client Setup in PRD

The production client &*' )=..+ and the preproduction client system is installed !y client copy from client .... &' )=2.+ are set up after the

The tested transport requests, the customizing changes and the developments from client 34ST )-..+ are imported into client &' )=2.+, as outlined in the ta!le a!ove. The integration test

occurs in client &' )=2.+. After completing integration testing, the production client &*' )=..+ is also supplied with the transport requests from client 34ST )-..+ of the development system %'E>(. 6n !oth cases Transport A is forwarded.

'o not delete any files in ...\TRANS\DATA or ...\TRANS\COFILE during the project phase. These files contain information and data for the import process. The ta!les !elow give another overview of transporting change requests in the three-system landscape. The system administrator transports the requests. 6f transports are to !e made into the preproduction client &' )=2.+, the requests must already have !een imported into client 9.. in %<AS( and tested there. Transports into the production client &*' )=..+ are made after a successful integration test. "ransporting Change re8uests in a "hree System Landscape

Source System SAP System %'E>( Source Client 34ST )-..+

"arget System SAP System % &'( "arget Client Reason "ime Reference

&' )=2.+

3ustomizing 6ntegration ? test development 3ustomizing After ? successful development integration test

3 )#orwarding+

%'E>(

34ST )-..+

% &'(

&*' )=..+

' )#orwarding+

Clients and "heir Roles

;hen you log on to an SA 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. ;hen you plan your SA system landscape, you must consider which clients you need for which activities. 0y assigning activities to !e performed in a client, you give each client a particular role. This section descri!es the most important client roles. Since you need to adapt the SA software for your own !usiness needs, each SA system landscape requires a client where 3ustomizing settings, and possi!ly A0A ;or,!ench developments, can !e made. This client is ,nown as the Customizing and development client, or Customizing client for short. The a!!reviation 34ST is used for this client.

0efore you can use the 3ustomizing settings and ;or,!ench developments productively, you need to test them e/tensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SA applications means that there are many dependencies !etween the different 3ustomizing settings. Even an e/perienced 3ustomizing developer may not discover these dependencies immediately. The correctness of the settings can only !e guaranteed with e/tensive testing. The client where these tests are made is the Quality Assurance Client, <TST for short. A separate client is required for productive use of the SA System. So that this client can !e used without disruption, it is essential that no 3ustomizing settings or ;or,!ench developments are made here, and also that no tests are carried out. This client is ,nown as the Production Client, &*' for short. These three clients, 34ST, <TST and &*', are the central clients that e/ist in every system landscape. Standard system landscapes have precisely one client for each of these client roles. ;e recommend that you ma,e all your 3ustomizing settings in a single 3ustomizing client, and then use the 3TS to transport them to the other clients. ;e also recommend that you do not ma,e any 3ustomizing settings or ;or,!ench developments in the quality assurance or production clients. 5ou can ma,e sure of this !y ma,ing appropriate client settings. 6n addition to the central clients, you can also set up other clients for other tas,s. @owever, you must remem!er that each e/tra client ta,es up additional system resources )main memory and data!ase space+. They also need to !e administrated. #or e/ample, you need to set up and administrate access authorization for the users, and also distri!ute any changes to other clients with the 3TS. 5ou must weigh up the advantages and disadvantages of setting up other clients. E/amples of other client roles are$ De$elopment test client 2".S"3$ 'evelopers can use this client to test their 3ustomizing settings and ;or,!ench developments, !efore they release their change requests. 6n this client the developers can create test application data for realistic tests. 6f they discover errors, they can remove them in the 3ustomizing client. A development test client is always set up in the same SA System as the 3ustomizing client. This means that any changes that are made to crossclient data in the 3ustomizing client are also immediately visi!le in the development test client. 3hanges to client-specific data are copied from the 3ustomizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the 3ustomizing client to do this. The development test client is set so that you cannot ma,e changes to 3ustomizing data and &epository o!jects. Prototype or sand'o( client 2SA%D3: 5ou can use this client to test any client-specific 3ustomizing settings if you are not sure whether you want to use them in this form. Any settings that you want to ,eep are then entered in the 3ustomizing client. To prevent conflicts !etween the prototype client settings and real settings in the 3ustomizing client, you cannot ma,e changes to cross-client 3ustomizing data and &epository o!jects in the prototype client. The 3TS does not record changes made to client-specific 3ustomizing data, and does not transport them from the prototype client. 5ou can ma,e sure of this !y ma,ing appropriate client settings. "raining client 2"R%+3$ To prepare end users for new functions that are to !e 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. This client is set so that you cannot ma,e changes to 3ustomizing data and &epository o!jects.