All about client creation in sap

###### All about client creation #########

*Run T CODE- scc4 command to create a new client.

In the client tab fill the new client number and name, city, logical name, currency, and client role.

What is a logical client?

A logical system is a unique ID within an SAP system that identifies a partner communication system. This partner system can be another SAP system, or it can be an external system.

We can use T-code sm59 to define a new client and it's always a good practice to create a logical name after creating a new client.

client role:

Production

By default you cannot make changes to cross-client objects in this client as it is locked.

These settings do not override the system change options.

Test

In this client, you cannot make changes to Repository objects or execute cross-client customizing

Customizing

The client is used for developing programs. Cross-client customizing is only allowed in this client

Training/Education ( This client contains master and transaction data to ensure that training is as realistic as possible)

Demo

This client is used for getting to know the system, trying out applications or testing customizing functions

SAP reference

No changes allowed. We also say this client as Golden Client.

The client-specific change options:

The settings for client-specific change options are maintained via
transaction SCC4 e.g. and can be reviewed via display of the
table T000 per double-click on a selected client number entry within SM30.

The following adjustments can be activated:

Changes and transports for client-specific objects:

This option controls whether client-specific objects can be maintained and if corresponding transports can be executed.

The following settings can be selected:   

•    Changes without automatic recording   
This setting allows changes of client-specific objects. But any changes will not be automatically recorded in a change request. This setting is not recommended for development and production clients. For training clients e.g. this may be a valid setting.   

•    Automatic recording of changes   
This setting allows changes of client-specific objects.
All changes are automatically recorded in a change request.
This adjustment can be recommended for development and customizing clients.   

•   No changes allowed
This setting prevents changes to customizing.

•    Changes without automatic recording, no transport allowed
This setting allows changes of client-specific objects.
Changes will not be recorded automatically in a change request
and with this manual transports are not possible.
This adjustment can be recommended for test clients.

Cross client object changes :

Now, the first thing is in mind is what is cross-client?

We all know that Cross Client Request impact all the Clients in a particular server. When create a new Object & we get a pop-up message that Table is Cross Client. Why does this happen?

Tables which are having MANDT field are called as Client dependent tables.

Tables which are NOT having MANDT field are called Client independent tables.

Go to T-Code SE16N & explore Table VBAK, VBRK, VBAP, KONV, etc. & you will see that the First Field in these Tables is MANDT i.e. Client. These are Client Dependent Tables, means all the changes in these Tables will impact only a particular Client.

Now, Explore Table TTXID (Valid Text ID’s) & you will see that MANDT field is not present in this Table. This means this Table is Cross Client & changes in this Table will impact all the Clients in the Server. As we all know that when we create a new Text Id, we get a Cross Client message. The same is true for Access Sequence.

This option controls how repository and client-independent customizing
objects can be changed in the selected client.

Four settings are selectable:
•    Changes to Repository and cross-client customizing allowed
This option does not restrict the maintenance of cross-clients objects at all.
With this, all cross-client customizing or repository objects can be maintained.

•    No change to cross-client customizing objects
This option does not allow the maintenance of cross-client customizing
objects in the selected client.

•    No change to repository objects
This setting does not allow the maintenance of the repository objects
in the selected client.

•    No change to repository and cross-client customizing objects
This setting does not allow the maintenance of cross-client customizing
or repository objects.

Protection against client copiers and comparison tools:

This setting protects the selected client against  reading access from other clients.
With this the comparison of tables cannot be executed and the client is protected
against overwriting in case of client copies. The following settings are selectable:

•    Protection level 0: no restriction
This setting does not protect the client at all. The selected client may be
overwritten by a client copy and any reading access from other clients are possible.
This protection level can only be recommended for test or training clients.

•    Protection level 1: No overwriting
The client cannot be overwritten by a client copy. This protection level is
appropriate for productive clients.

•    Protection level 2: No overwriting, no external availability
The client cannot be overwritten by a client copy.
Reading access from other clients
is not available. This protection level is recommended for clients
that contain highly sensitive data.

Cat and Ecat Restrictions:

eCATT (extended Computer-Aided Test Tool)

What is eCATT?

eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.

Features of eCATT:

Following functions can be performed using eCATT:

Test transactions, reports and scenarios.

Call BAPIs and function modules.

Test remote systems.

Check authorizations (user profiles).

Test updates (database, applications, GUI).

Set up customizing tables.

Test the effect of changes to customizing settings.

Perform load testing.

Check system messages.

Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.

Supports CATT migration to eCATT.

All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.

eCATT Objects can easily download & upload in XML with XSD format.

There can be several versions of Test Scripts, which allows different implementations with different releases.

The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.

Why eCATT?

CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT are now need to migrate/update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:

Due to automation, testing time is reduced to a large extent.

Due to automation, less manpower is required for testing. This helps financially.

Due to automation, manual errors are reduced to a large extent. Hence results in error-free testing. This helps, as no further problems will occur while the usage of R/3 system by end-users and hence increases efficiency.

Proved to be extremely useful in implementation projects.

In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.

Differences between CATT and eCATT?

Till date, CATT could only be used with the R/3 system. eCATT (which is available with SAP Web Application Server 6.20) covers the automatic testing in SAPGUI for Windows and SAP GUI for Java. For other GUIs and Applications, eCATT provides an interface for external tools. This allows companies to perform automated tests from an SAP system in a complete IT solution landscape across system boundaries. These new options enable complete automation of solution landscapes under standard Windows and Web-based user interfaces- resulting in low-cost operation of an IT Solution.

Restrictions:

• Locked due to client copy
Protect against client copy.

• 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.