What is System Change Option Used For?

[Former Member]

Hi,

I need help on security.

we use scc4 settings for client protection. the settings are 'No changes allowed' for client-specific objects and 'No Changes to Repository and cross-client customizing objects' for cross-client object changes.

system change options are set to 'Modifiable'. what is the difference between these settings? Is there any situation that may cause problems?

thanks,

- ferudun

[Former Member · Accepted solution]

Hi Ferudun,

For a production system you should set SCC4 to the following:

Client Role = Production

Changes and Transports for client-specific objects = No Changes Allowed

Client-Independent Object Changes = No changes to repository and cross-client customizing objs

Protection: Client copier and comparison tool = Protection level 1: No overwriting

Restrictions when starting CATT and eCATT = eCATT and CATT not allowed

For SE06 - System Change Options:

All software components and namespace/name range options should be set to NOT MODIFIABLE. This can be done easily by setting the "Global Setting" to Not Modifiable.

SE06 controls what types of repository objects and what objects in a specific namespace can be modified in your system. The user/developer would still require appropriate authroisations to make a change, however for a production system, this setting should ALWAYS be set to NOT MODIFIABLE.

[Former Member]

Hi,

Have you tried F1 help for these fields? Is there anything particular you'd like to ask about it? The difference between settings is mentioned in the F1 help.

Regards

[Former Member]

we use scc4 options as mentioned above for productive systems. we don't use the system change option even for our productive systems. should we use it, why?

- thanks

[Former Member]

Hi,

The system change options are associated with the role the system is intend to take. The role can be any of Customizing, Test, Demo, Production, etc. For Production systems, you should set it to Non Modifiable. No changes should be directly made in Production unless necessary. All changes should come from DEV into QA and then into Production.

Regards