SAP ABAP Data Element XUCATT (CATT: Test Status)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC-USR-ADM (Application Component) User and Authorization Management
⤷ SUSR (Package) ABAP User Administration
⤷ BC-SEC-USR-ADM (Application Component) User and Authorization Management
⤷ SUSR (Package) ABAP User Administration
Basic Data
Data Element | XUCATT |
Short Description | CATT: Test Status |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XUBUTTON | |
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 | CATT FLAG | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | CATT |
Medium | 20 | Test Status |
Long | 40 | CATT: Test Status |
Heading | 0 |
Documentation
Definition
Computer Aided Test Tool (CATT)
If the 'test status' flag is activated for the user, a test status is set when CATT processes are started. The test status itself is language-dependent and is stored depending on the process variant started. A history of test status allocation is also kept.
For the test status flag to be activated, you need authorization for the object
ABAP Development Workbench (S_DEVELOP)
Development class ID SCAT
Activity 70 = Administer, Manage.
The test status should only be set for final tests. Transports of CATT processes are generally compiled in other systems because of the test status.
General information on CATT is available in connection with the ABAP Development Workbench.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in |