Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NPVS (Package) Application development patient management system
Basic Data
| Data Element | ISH_CFNAME |
| Short Description | IS-H: ABAP 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 | GUI_TEXT | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | 14 | Field Name |
| Long | 20 | Field Name |
| Heading | 0 |
Documentation
Definition
The function or menu text is to be modified at run time. Regardless of the PS-STATUS setting, the content of ABAP or dictionary field named in this field is displayed in the menus and function keys that refer to this text.
Tip on using reference techniques
If you want to work with references to GUI definitions of other programs and dynamic texts, you must ensure that the fields for which the status is defined are assigned to the program.
If you define a status that is used by several programs via a function module call, the fields for dynamic texts must be created in the function group for which the status was created - you must not create the fields in the calling program.
If you are using the include menu technique, you have to create the fields for dynamic texts in the program for which the set status was created - in other words, not in the progran for which the included menu was created.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
