Often in business scenarios, there will be requirements which cannot be transported and which have to be modified directly in respective tables and other repository objects. To perform these operations client to be opened.
Goto transaction SCC4. This lists clients’ overview as below:
From the above screen, we can make out what are the existing clients in the
SAP system, their names and the date they are last modified.
Double click on the client to be opened. It displays similar screen as below
with the complete client details like last changed date, last changed by, client
role and associated logical system of the client
and no changes to the repository and cross-client customizing objects. These 2
settings mean that client is NOT opened.
To open the client we should set the client settings as shown below for a client:
In addition to the above 2 settings, in SE06, System change option should be
set to “modifiable” as shown below:
Go to transaction SE06:
Click on System change option as in the below screen
In the above screen, set the Global setting as “modifiable” to make sure client
is opened.
In case you would like to restrict changes to a client, please set this Global
setting as non-modifiable so that no changes can be done.
Please note that the above setting of system change can be done through
SE03 transaction as well.
What are the various client settings and their significance?
Changes and transports for Client specific objects :
1) Changes without automatic recording: Changes will be done without
recording in a change request
2) Automatic recording of changes: Changes will be done and request will
get generated & changes will be captured in that
3) No changes allowed: No changes will be allowed
4) Changes w/o automatic recording no transports allowed: This flag
means customizing changes will be permitted but changes are not automatically recorded in the change request.
Cross –Client object changes :
1) No changes to cross-client object changes
2) No changes to repository objects
3) No changes to cross-client and repository objects
4) Changes to cross-client and repository objects.
No comments:
Post a Comment