SCC4-No changes Allowed

[Former Member]

Hi,

As per the Auditors infstructions we need to change the SCC4 settings in Production Environment to No Changes allowed from Changes without automatic recording..

Could you please let us know what is actually meant by that and what would happen if we chaNge that option in Production environment..

Regds,

Satyanarayana N.

[Former Member]

Satyanarayana,

The SCC4 transaction has 2 parts to it:

A.) Changes and transports for client independent objects---which has options:

1. Changes without automatic recording

2. Automatic recording of changes

3. No changes allowed

4. No transports allowed

B.) Client independent object changes---wich has the options:

1. changes to repository and client independent customizing objects allowed

2. No changes to client independent customizing objects

3.No changes to repository objects

4. No changes to repository and client independent customizing objects

Lets start by saying that the options in B.) would only be relevent if the options in A.) are 1, 2 or 4.

The reason why you were asked to change the option A.) from:

Changes without automatic recording

to

No changes allowed --- is that in a productive environment any changes to cutomizing objects or repository objects

1. might lead to the system crashing there by disrupting business

2. may cause a security breach as per SOD (segregations of Duties set by SOX (Sarbanes Oxley) law which has to adhered to world over by businesses.

But yes, there are situations where the option has to be set to:

Changes without automatic recording for a brief period of time. But these situations have to be recorded and presented to the auditors. For instance:

There are certain customizing changes (more often than not done by the FI module) which are not transportable A classic example is NUMBER RANGES for Sales documents, billing documents etc. Nuber ranges for these documents are not transportable and have to be set directly in the production environment. For situations like this, the above option is used. A record is maintained about this and presented to the Auditors.

We have discussed to options :

1.Changes without automatic recoding

2. No changes allowed.

The thrid option

3. automatic recording of changes is always used in a development client. This is because changes done in that system have to be transported to quality and production systems and hence a transport request is automatically generated

4. No transports allowed is used in sandbox clients where Customizing changes are allowed but transports are not allowed to be created (manually also)

Hope the explanation helps. You can also search for details about SOD and SOX which are a very important part business compliance.

Please do award points if the explanation has been helpful

Regards,

Prashant

[Former Member]

Hi Satya,

Changes without automatic recording means that when you change some cross client objects by default there will not be any transport request generated you have to manually generate the transport requests.This type of option should never be used in production environment.

No Changes allowed this is the standard option to be set in production environment.This option does not allow cross-client object to be changed.Change is only possible in the system through importing transport requests.

Reward points if helpfull.

Regards,

Vamshi.

[Former Member]

Hello Vamshi,

This option is not for cross client objects but for client specific objects.

Hello Satya,

However what Vamshi said is fully correct. Don't use this option. This would mean that client specific customizing is changable in production which certainly as I prerceive isn't desirable. Rather convince the auditors for the option NO changes allowed.

Regards.

Ruchit.

[Former Member]

Hello Ruchit,

I think this is for cross-client object like abap reports, though i agree with you that it is also for client specific objects also.

Correct me if i am wrong.

Regards,

Vamshi.

[Former Member]

Hello Vamshi,

Very technically speaking ABAP reports are not cross client objects but are Repository objects.

Also settings for cross client and client specific customizing are different with in SCC4 and are independent of each other. For example if you select Radio Button No Changes Allowed for Tabstrip Changes and Transports for client specific objects then you wont be able to change client specific customizing but that will have no bearing to cross client customizing which will purely depend on what settings have been maintained under Cross Client objects.

Regards.

Ruchit.