Download SAP eBooks @ http://simply-sapebooks.blogspot.com
Changes and Transports for Client-Specific Objects
Controls whether client-specific objects can be maintained and if corresponding transports can be executed.
• Changes without automatic recording
Allows changes of client-specific objects but any changes will not be automatically recorded in a change request.
Allows changes of client-specific objects but any changes will not be automatically recorded in a change request.
• Automatic recording of changes
Allows changes of client-specific objects. All changes are automatically recorded in a change request.
Allows changes of client-specific objects. All changes are automatically recorded in a change request.
• No changes allowed
Disallow changes to customizing.
Disallow changes to customizing.
• Changes without automatic recording, no transport allowed
Allows changes of client-specific objects. Changes will not be recorded automatically in a change request and with this manual transports are not possible.
Allows changes of client-specific objects. Changes will not be recorded automatically in a change request and with this manual transports are not possible.
Cross-Client Object Changes
Controls how repository and client-independent customizing objects can be changed in the selected client.
• Changes to Repository and cross-client customizing allowed
Allow changes of the maintenance of cross-clients objects.
Allow changes of the maintenance of cross-clients objects.
• No change to cross-client customizing objects
Disallow the maintenance of cross-client customizing objects in the selected client.
Disallow the maintenance of cross-client customizing objects in the selected client.
• No change to repository objects
Disallow the maintenance of repository objects in the selected client.
Disallow the maintenance of repository objects in the selected client.
• No change to repository and cross-client customizing objects
Disallow the maintenance of cross-client customizing or repository objects.
Disallow the maintenance of cross-client customizing or repository objects.
Protection: Client Copier and Comparison Tool
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.
• Protection level 0: no restriction
Allow any changes to the client at all. The selected client may be overwritten by a client copy and any reading access from other clients is possible.
Allow any changes to the client at all. The selected client may be overwritten by a client copy and any reading access from other clients is possible.
• Protection level 1: No overwriting
The client cannot be overwritten by a client copy.
The client cannot be overwritten by a client copy.
• 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.
The client cannot be overwritten by a client copy. Reading access from other clients is not available.
CATT and eCATT Restrictions
• eCATT and CATT Not Allowed
Prevents test scripts to be started in the client.
Prevents test scripts to be started in the client.
• eCATT and CATT Allowed
Enables you to implement eCATT and CATT without restrictions. Using inline ABAP and function modules, any code can be run on the target system (security).
Enables you to implement eCATT and CATT without restrictions. Using inline ABAP and function modules, any code can be run on the target system (security).
• eCATT and CATT Only Allowed for 'Trusted RFC'
Automated test cases can be started only if the target system has been addressed via a trusted RFC connection. In this case, the full range of functions can be implemented for tests on this client.
Automated test cases can be started only if the target system has been addressed via a trusted RFC connection. In this case, the full range of functions can be implemented for tests on this client.
• eCATT Allowed, but FUN/ABAP and CATT not Allowed
Only transactions can be executed in the target client. They must be addressed via eCATT.
Only transactions can be executed in the target client. They must be addressed via eCATT.
• eCATT Allowed, but FUN/ABAP and CATT only for 'Trusted RFC'
This protection level allows calling function modules and executing inline ABAP provided that the connection to the target system is established via a trusted RFC.
This protection level allows calling function modules and executing inline ABAP provided that the connection to the target system is established via a trusted RFC.
Restrictions
• Locked due to client copy
Protect against client copy.
Protect against client copy.
• Protection against SAP upgrade
If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customer's SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client.
If you chose this option, then this client will be not updated in time of upgrade. You should use this option for a client that is used for backup purposes or client 066 (Early Watch client) that is used by SAP for customer's SAP system performance. If you chose this option for any client, the upgrade will not provide any data to this client and it can not be used as a regular customizing client.
No comments:
Post a Comment