Creating a client and setting up the client attributes 

To create a client you have to maintain T000 table. From 3.0 onward, transaction SCC4can be used to maintain T000 table. Also you can chose Administration-> Client admin -> Client Maintenance from the initial screen to do the same. In client table T000, SAP system displays all the clients available, their names, currency used and when the client was changed last. If the system is in display mode then you must change it to the change mode by selecting the display/change icon to create a new client. When you click display/change button, a warning is displayed as “Warning: the table is client-independent”. The “New entries” icon should be clicked to create a new client.

In the new client creation screen to define a new client you must fill all the required entries. The client number and the name are entered first. Then in the second line the location of the SAP system is defined.

Logical system is defined next.  SAP uses logical system concept in ALE (Application Link Enabling), workflow and EDI areas. The logical system must be unique through out the company and any other ALE system group can not use it. You must be careful changing the logical system entry. SAP treats a logical system as a client. You can use transaction BD54 to create a logical system and then enter that entry in the logical system box while creating a client. 

Next entry “standard currency” can be defined according to the country. For example USD can be used as a standard currency for USA. To enter a category of a client you must know the objective of that client beforehand. For example if this client will be used as a customizing client then customizing entry should be used from the options. In the next category “Changes and transports for client-dependent objects”, there are four options. If you want to use this client as a sandbox client; and you do not want to record or create a change request every time a change happens to the client then “Changes W/O automatic recording” is the right option. If all the changes to the client should be recorded in a change request then “Automatic recording of changes” is the right option. You must choose this option for your master configuration client. If  “No changes allowed” is chosen, then no changes will be allowed to this client. You must chose his option for clients in the production environment to protect your system. “No transport” option is used when you do not want any user to create a transport from this client.

The “Client-independent object changes” category determines if the client independent data maintenance is allowed in this new client. You get following four options in this category:

• Changes to Repository and client-ind. customizing allowed 
• No changes to client-independent customizing objects
• No changes to Repository objects 
• No changes to Repository and client-independent custom. obj.

To choose the right option from “Client-independent object changes” category, you must know the definition of Clint independent customizing objects and repository objects. The examples of SAP repository objects are data dictionary objects, module pools and screens. Client independent objects apply to all the clients. The factory calendar is an example of client independent object of customizing. For sandbox client, where user learns how to do the customizing, you must not allow the client independent customizing. 

Changes to Repository and client-ind. customizing allowed: Both client independent customizing objects and SAP repository objects can be maintained. Usually this option is selected in a master-customizing client. 

No changes to client-independent customizing objects: No change is allowed for client independent customizing objects but changes to repository objects are allowed. This option can be used for a sand box client. 

No changes to Repository objects: If you select this option, then no changes are allowed to the Repository objects but the client independent customizing is allowed. When you want to protect the repository objects in a client, this is the right option to use. 

No changes to Repository and client-independent custom. Obj: This option does not allow any changes to client independent customizing objects and repository objects. You should use this option for a consolidation and production client where the security of client independent objects and repository objects are necessary. 

In the restriction category of the ‘Change View “Clients”: Details’ screen, there are four options. You are allowed to maintain only the following three options.

Protection against overwrite by copying:  If you chose this option, a client copy can not overwrite the new client. You should chose this option for a master-customizing client or for an important client as production.

• Start of CATT processes allowed: This option determines whether you want to allow the CATT (Computer Aided Test Tool) process in the client or not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different functionality of the SAP system.  To run the CATT tool you can execute transaction SCAT. CATT process changes the database extensively and requires lot of system resources. So we recommend not to chose this option if you are in the production environment.

• Protection against SAP upgrade:  If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customer’s SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client. You need S_CTS_ALL authorization to maintain this option.