Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-MEN (Application Component) Menu Painter⤷
SEUC (Package) Menu Painter
Basic Data
| Data Element | CUA_TYPE |
| Short Description | Type of status / menu bar / function key setting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CUA_STYPE | |
| 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 | Type |
| Medium | 15 | Type |
| Long | 20 | Status type |
| Heading | 4 | Type |
Documentation
Definition
The status type determines the input help and standard checking. Normal screens allow you to define a menu bar, function keys and pushbuttons. With dialog boxes, you can define only function keys and pushbuttons.
If you choose the status type 'List', functions that trigger system functions in lists are usually assigned to function keys. If you do not change these proposals, these functions (e.g. print, scroll, ...) are automatically available. If, however, you have to program a system function yourself (because, for example, you have to confirm after F3), you must use a different function code.
In general, the status type affects standard checking. The standards for dialog boxes are different than those for normal screens.
At runtime, the status type is not taken into account.
History
| Last changed by/on | SAP | 19970725 |
| SAP Release Created in |
