Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-CAT (Application Component) CATT Computer Aided Test Tool⤷
SCAT (Package) Computer Aided Test Tools
Basic Data
| Data Element | CATNEUCOM |
| Short Description | CATT - CATT mode w/o COMMIT WORK end |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 10 | COMMIT WRK |
| Medium | 15 | CATT mode |
| Long | 32 | CATT mode w/o COMMIT WORK end |
| Heading | 1 | C |
Documentation
Definition
CATT mode without COMMIT WORK termination
CATT no longer runs transactions in BATCH INPUT mode and the MEMORY flag CATTAKTIV is not set. The new CATT mode only performs CATT error handling. The transactions run as if they had been called in dialog. The checkbox
CATT mode without COMMIT WORK termination
must be set in the CATT transaction data maintenance. Otherwise the transactions run in BATCH INPUT mode.
Ending application transactions
Application transactions in CATT mode without COMMIT WORK termination are not automatically terminated at COMMIT WORK. Transactions must be ended explicitly in one of the following ways
- an extra screen with the OK code /3 (Back)
- an extra screen with the OK code /bcn.
In these cases no extra message is created after the last message in the application transaction, so CATT message checking is unchanged.
- the OK code /bn
processing unchanged, i.e. the CATT log contains the message :
- transaction terminated by the user.
Application transaction screen sequence
Screen sequences which depended on SY-BINPT and CATTAKTIV cannot be retained for the new CATT mode. The normal dialog screen sequence must be specified. You must also specify for recording whether the transaction is for BATCH INPUT mode or the new CATT mode without COMMIT WORK termination.
Some application transactions perform certain actions only when they are run by CATT, for example messages are output which are not relevant in normal dialog, but control the transaction flow in CATT. In the new CATT mode, this information is in a new flag CATTNEU which is set to �X� every time a transaction is run in MEMORY, not in SY-BINPT and CATTAKTIV.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
