Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-CCO (Application Component) Client Copy⤷
STRM (Package) Client Copy & Adjustment Tools
Basic Data
| Data Element | CCIMAILDIS |
| Short Description | Client Control: CATT und eCATT Authorization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SECURECATT | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 6 | CATT |
| Medium | 15 | CATT Allowed |
| Long | 40 | CATT Authorization |
| Heading | 6 | CATT |
Documentation
Definition
This flag determines whether you can run:
CATT - Test cases
eCATT - Test scripts
eCATT - Test configurations
in this client.
Running CATTs and eCATTs can sometimes cause extensive database changes, which is usually not allowed, especially in a production client.
Further information about CATT ("Computer Aided Test Tool") and eCATT ("Extended CATT") is in the ABAP/4 Workbench environment.
From Basis release 620, the extended tool eCATT, which you can also use for remote tests of systems from Release 4.6, is available in addition to the SAP test tool CATT. You need a Basis system from Release 620, in which you manage your tests. You can run the test functions from there via remote RFC connections, even in older systems from Release 4.6. When settings for eCATT in these older systems (4.6 to 610) are mentioned here, it means the effect on remote eCATT from a newer administration system from Release 620.
eCATT contains enhancements of CATT, in particular in the eCATT functions FUN and ABAP, which can be supported by an enhanced client setting.
Until now, you had to specify for each client in a system, in the client table T000, whether you can run test cases with CATT and eCATT in it. Most aspects of CATT and eCATT processing, such as calling transactions and editing tables can usually be protected adequately by authorizations.
The client setting enhancements are CATT-compatible. You do not need to change your CATT settings. If you make changes, they define whether and under which conditions it runs.
The enhanced client settings do not affect the authorization checks specified in CATT and eCATT.
The enhancements are concerned mainly with the creation of remote connections. 'Trusted' RFC connections allow you to copy security settings from the initial system into the remote test system. The enhanced client settings can make running partly or completely depend on the RFC connection type, as well as simply allowing or forbidding it.
You can make the following settings in the client table T000:
eCATT and CATT restrictions:
' ' eCATT and CATT not allowed
X eCATT and CATT allowed
T eCATT and CATT only allowed in 'Trusted RFC'
E eCATT allowed, but FUN/ABAP and CATT not allowed
F eCATT allowed, but FUN/ABAP and CATT only in 'Trusted RFC'
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 50A |
