Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NMED (Package) R/3MED: Medical documentation GSD
Basic Data
Data Element | N2_TIP_PUSH |
Short Description | Pushbutton |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Pushbuttons can be used within and outside of multiple structures.
Tab page dialog
Here you define the appearance of the button on the screen
Option
You can select whether the button is to be defined
- with text,
- with an icon, or
- with text and an icon.
Width
This parameter is active if the button is displayed with text (and an icon).
Tab page function
Code
You must enter a Function code for the pushbutton. This will be triggered when you press the button in the dialog.
Save-query
If you set this indicator, you will be offered a Save-query dialog before this command will be executed if the data has been changed.
Active with
You can define which document editing functions the button will be active for.
Routine and Include
Enter the name here and the FORM routine that is given in the generated standard OK-code processing will be called.
If you do not enter a name, then you should process the function code in the PAI user exit or in an appropriate external data module.
Branch into the program editor
After entering the name, by Double-clicking, you can branch into the program editor for processing the Include.
OK-code processing in multiple structures
The line where the function was triggered exists in the global program variable REQUESTED_LINE. You can use this in your user exit or in the function routine.
History
Last changed by/on | SAP | 20050223 |
SAP Release Created in |