different Client roles in SCC4

[Former Member]

Hello Everyone,

Can someone help me understand the concept on different types of Client roles as found in SCC4. As we view there, there are 6 types, production, test, customizing etc. Can you help me what is it about in each client role, the difference, the details, the special privileges?

I am trying to find related documets and have been exhausted finding none but only about the client dependent and independent change settings, CATT details etc in SCC4.

Grateful you could share your insights.

Thanks,

jennah

[Former Member]

Hi Deepak and Sean,

That is one of the infos I need and most especially the dependency of the different client roles to the system change option as well as the other settings such as client dependent and client independent settings in SCC4. So you mean that at each client role, whenever you have settings in cliebnt specific and non client specific some may not take effect?

Anyone else if you have ideasa please shout out..

Many many Thanks,

jennah

[nelis]

Jennah,

The actual role definition doesn't change anything in the system besides entry's in table T000. It's the Client Specific, Cross-Client and the System Change Option settings that define how data is managed in the system.

The global System Change options(SE06) will also take precedence over the SCC4 cross client options, for example, if you set the option for Cross-Client object in SCC4 to "Changes to Repository and cross-client customizing allowed" and your System Change Option is globally set to "Not modifiable" you will still NOT be able to make any changes to the repository.

Also, other programs depend on the role definition to decide how they will react with the system.

Regards,

Nelis

[Former Member]

Hi Sean and Deepak,

Thanks and even for the F1 tip! But do you know of any docs that tackles each of the client role:

Production

Test

Customizing

Training/Education

Demo

SAP reference

Just want to check if they are just names or there are technicalities once these roles were assigned in SCC4.

Regards,

Jennah

[Former Member]

Hi,

Possible roles of a client are:

Production client

Test client

Training client

Demo client

Customizing client

SAP reference client

This field should be maintained by the customer for documentary purposes.

It is particularly important for the production client:

Production clients and SAP reference clients are protected from the client copy tools, including "Copy by Transport Request" (transaction SCC1).

There is corresponding protection from the automatic Customizing Distribution and other tools.

In a production client, customizing settings that can be maintained as "current settings" are excluded from a client lock or transport connection; this means current settings (e.g. exchange rates, posting periods) can always be maintained in a productive client without recording changes. Other clients usually require a transport request.

regards, Sean.

[Former Member]

Hi

When u define these options in SCC4, the following things should happen

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 says this client as Golden Client.

For further things, pls check this

http://help.sap.com/saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/content.htm

[Former Member]

Check this:

When you log on to an SAP 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. When you plan your SAP system landscape, you must consider which clients you need for which activities.

By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.

Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.

Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively 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 SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.

A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.

These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.

We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.

We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.

In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.

Examples of other client roles are:

Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.

Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.

Training client (TRNG): To prepare end users for new functions that are to be 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 make changes to Customizing data and Repository objects.

Link is http://help.sap.com/saphelp_nw04/helpdata/en/6c/a74a3735a37273e10000009b38f839/content.htm

[Former Member]

Hi there,

Please follow the link:

http://help.sap.com/saphelp_nw70/helpdata/EN/69/c24ca94ba111d189750000e8322d00/frameset.htm

I'd rather use trusted "F1" on each field of any transaction for details. Try it in SCC4 and on each client details.

regards, Sean.