You can use the Transport Organizer to record all changes to Customizing settings in change requests and mark them for transport.

The transport of Customizing settings to another SAP System is prepared. You only need to release the change request.

However, it is not always a good idea to record every single change made to the system. That is why many SAP Systems have a test, training, or demo client in addition to the production client. Recording changes is not appropriate here. In extreme cases, this could even result in unintentional transports that could destroy the target client.

To meet these sometimes contradictory requirements, you can assign each client appropriate attributes, which you can maintain in table T000 (transaction SM30):

• Role of the client: Indicates whether the client is a production, test, training, demo, or Customizing client.

• Changes and transports for client-specific Customizing objects: You can specify for each client whether you want the changes to be recorded. As with the
system change option in the Transport Organizer, changes can also be forbidden here altogether. You can make the following settings:

• Changes without automatic recording
• Automatic recording of changes
• No changes possible
• Changes without automatic recording; no transports allowed

• Changes to cross-client objects: You can specify for each client whether you want to allow changes to Repository objects and/or cross-client Customizing objects.

Different request types in the Transport Organizer allow you to distinguish between the two modes. Changes to cross-client Customizing objects and to Repository objects are recorded in Workbench requests; changes to client-specific Customizing objects are recorded in Customizing requests.

If you use only Customizing requests, you make sure that the results of a Customizing project can be transported to the target client of another system without affecting other clients there.

In contrast, no guarantee can be given that the results of transporting Workbench requests will be restricted to one client. In this case, the import must be checked to establish whether it includes any cross-client objects. If such objects are found, we recommend that you adjust the corresponding settings in the source and target systems in order to assess the affect on all other clients.

Other features that affect the client are:

• Flag that locks the logon procedure. It is set in the target client by the client copy program. This means that no work may be carried out in the target client when client copy is in progress.

• Protection against SAP upgrade means that the client is no longer provided with SAP upgrades. Users can no longer work actively in the client after the system has been upgraded. The flag can only be set for a test client or an SAP reference client (
EarlyWatch). This function is only intended for exceptional cases, when, for example, the basis for an adjustment is needed after an upgrade has been performed. Every "normal" client must be updated by an SAP upgrade, since otherwise data resources from system and Customizing tables required for transactions may not be available. However, you can prevent clients that need to contain certain tables purely for backup purposes (backup clients) from being supplied with SAP upgrades that are not necessary or not wanted. To maintain this flag, you require the administration authorization for the Transport Organizer (authorization S_CTS_ADMIN).

• Restricted permission to execute CATT procedures. CATT (Computer Aided Test Tool) allows you to restart recorded test runs repeatedly. This process changes the database and it is therefore necessary to declare this as a property of the client.