System and client change option
System and client change option
SAP® consists of many different objects, like e.g. tables, reports, structures etc.
These objects need to be maintained in the various clients and systems to
different extents.
With regard to the fact that objects can be client-specific or cross-client the
maintenance control is covered by two different adjustments.
1. The system change option
The system change option is maintained via transaction SE06 and can be
reviewed with the help of the reports RDDIT097 and RSWBO004.
The settings within SE06 are valid for cross-client objects [repository as well as customizing etc.].
The following adjustments can be activated:
• Customer name space
In the customer name space all customer-specific developments [programs, tables, etc.] that can be transported are covered.
• Local developments
The local developments cover all customer-specific objects that cannot be transported.
• SAP® application components
All standard SAP® application components can be changed via the ABAP® workbench.
• SAP® basis components
All standard SAP® basis components can be changed. During an upgrade the
changed objects will be overwritten with new components.
• ABAP® & GUI tools
This option allows the change of SAP® objects can through the ABAP® editor,
the screen painter or the menu painter.
• Development workbench
This option allows the change to SAP® objects
through the available workbench tools.
• Enqueue function groups
This option allows the change of function groups that are used
for locking and unlocking of data records.
• ABAP/4®-Query/SAP®
This option allows the use of queries. This also allows the creation
of customer specific reports.
The logs of changes to these setting are stored in the table DDPRS.
Any changes are automatically logged. The evaluation can be executed
with the help of the report RSWBO095 via transaction SE38 / SA38.
2. 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 adjustements 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.
Client-independent object changes
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 otion 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 maintenancece of 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 respository 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 excuted 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 is 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.
The prerequisite for an evaluation of changes to the client-specific settings is an activated system parameter rec/client for the selected client. This setting can be checked with the help of the report RSPFPAR through transaction SE38 or SA38.
The table T000 is activated for logging of changes per default.
With the help of the report RSTBHIST via transaction SE38 / SA38 corresponding changes can be evaluated.
The table name needs to be entered together with the evaluation period.
The radio button for table needs to be activated as well.
