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_FNAME |
| Short Description | ABAP/4 field name for dynamic function text |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DYNFNAM | |
| Data Type | CHAR | Character String |
| Length | 132 | |
| Decimal Places | 0 | |
| Output Length | 132 | |
| 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 | Name |
| Medium | 15 | Field name |
| Long | 20 | Field name |
| Heading | 0 |
Documentation
Definition
Changes the function or menu text at runtime. Regardless of what has been set by PF-STATUS, the contents of the ABAP field or the Dictionary field specified in this field are assigned to the menus and function keys that reference this function text at the end of PBO.
The ABAP or Dictionary field needs to be created using the SMP_DYNTEXT structure. The value in the TEXT field appears in the pull-down menus and on the function keys. If no icon is specified, the text also appears on the pushbuttons. If icons are used, for example, ICON_ID = ICON_OKAY, the icon appears in the application toolbar along with the contents of ICON_TEXT if applicable.
In Release 4.0 it will be possible to create quickinfo independently of the function text. Hence the field already exists, but it is not currently used.
Note on using other reference fields:
Older documentation recommended the use of reference field RSEU1-MENU or a field with length 20. If you use such fields for dynamic text they will behave as before - with all the disadvantages associated with the use of icons.
Notes on the use of reference techniques
If you want to refer to the GUI definitions of other programs and dynamic texts, you must bear in mind that the fields are assigned to the program in which the status is defined.
When you define a status which, through a call to a function module, is used by several programs, you must create the fields for dynamic texst in the function group for which the status was created - the fields must all be created in the calling program.
If you are using include menus, you must create the fields for dynamic texts in the program for which the set status was created - i.e. not in the program for which the included menu was created.
History
| Last changed by/on | SAP | 19970707 |
| SAP Release Created in |
