Figure 13: Client Change Options
Client change options that are found in the clients master table T000, can be maintained by using transaction SCC4.
The two settings that must be maintained to implement controls on where changes are made and enforce the changes being recorded to transport requests are:
• Changes and transports for client-specific objects
• Cross-client object changes
The following list gives a brief description of what each option allows:
• Changes and transports for client-specific objects:
– Changes without automatic recording
This flag means that changes in the Customizing settings of the client are permitted. The changes are not automatically recorded in a transport request.
Customizing settings can be exported from the client by manual creation of a transport request. A manual transport can be carried out in the particular transaction (if possible) or manually.
This variant makes sense for pure test, training or demonstration clients.
– Automatic recording of changes
This flag means that changes are permitted in the customizing settings of the client and all the changes are automatically recorded in a transport request.
It is also possible to export independently of the automatic recording from the client customizing settings by manual creation or recording of a transport request.
In a productive client, settings that can be maintained as current settings are excluded from automatic recording; current settings (e.g. exchange rates, posting periods) are maintained without recording the changes.
This variant can be used for customizing clients and productive clients.
– No changes allowed
This flag means that changes in the customizing settings of the client are not permitted.
However, customizing settings can be exported from the client by manual creation of a transport request.
In a productive client, the customizing settings that can be maintained as current settings are excluded from the client lock; this means that current settings (e.g. exchange rates, posting periods) can always be maintained in the productive client.
This variant can be used for productive clients, demonstration clients and training clients.
– Changes w/o automatic recording, no transports allowed
This flag means that changes are permitted in the customizing settings of the client. The changes are not automatically recorded in a transport request, however.
No manual transport of customizing settings from the client is possible.
This variant can be used for pure test clients.
• Cross-client object changes
This feature controls in which clients you are allowed to maintain cross-client objects.
It makes sense to disallow cross-client maintenance if the objects to be maintained in a client are exclusively application objects (all client-specific) or client-related customizing objects. In this case (for example in a test client), you must be able to ensure that cross-client functionality cannot be changed.
Cross-client functions include all cross-client customizing objects (e.g.
factory calendar, definition of price list conditions, printer controls). But in particular they also include all objects of the SAP Repository (programs, function modules, screens, dictionary etc.).
– Changes to repository and cross-client customizing allowed
There are no restrictions on the maintenance of cross-client objects for the client when this setting is used. Both cross-client customizing objects and objects of the SAP Repository can be maintained.
Use in customizing/development client only – No changes to cross-client customizing objects
Cross-client customizing objects cannot be maintained in the client with this setting.
Only use this if development client is separate from customizing client – No changes to repository objects
With this setting, objects of the SAP Repository cannot be maintained in the client.
Only use this if customizing client is separate from development client.
– No changes to repository and cross-client customizing objects Combination of both restrictions: Neither cross-client customizing objects nor objects of the SAP Repository can be maintained in the client.
Use this in every client in the landscape except customizing/development client(s)
Figure 14: Customizing Using Current Settings
In a customizing project and also during the maintenance of a SAP system all the customizing changes should be transported and tested in the quality assurance system. But certain kinds of customizing changes, so called data-only customizing changes, need to be carried out in a production client without being saved as transport requests. Examples of such data include interest rates, health insurance premiums, pension schemes, tax schemes, and currency exchange rates, which may require frequent adjustment in SAP systems.
Since these types of changes have a frequent change rate and they are not subject to extensive testing like other customizing changes, these changes are done directly in the productive client in the productive system. To avoid having to use transport requests for these changes, SAP has introduced the Current Settings function.
Current Settings may be used within a production client without impacting business flow-related Customizing objects.
SAP-approved Current Settings for customizing objects are kept in the field CURSETTING in the table OBJH. SAP recommends that no customer changes be made to the table.
When using Current Settings in a production environment:
• Client role is set to: Production
• Cross-client object changes are set to: No changes to Repository and cross-client Customizing objects
• Changes and transports for client-specific objects are set to: No changes allowed.
Lesson Summary
You should now be able to:
• Describe the system change options in an SAP system
• Describe the client change options in an SAP system