SAP GRM_POPUP_TO_GET_ONE_VALUE Function Module for
GRM_POPUP_TO_GET_ONE_VALUE is a standard grm popup to get one value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for grm popup to get one value FM, simply by entering the name GRM_POPUP_TO_GET_ONE_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRM_WRAPPER
Program Name: SAPLGRM_WRAPPER
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRM_POPUP_TO_GET_ONE_VALUE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'GRM_POPUP_TO_GET_ONE_VALUE'".
EXPORTING
TEXTLINE1 = "Character 100
* TEXTLINE2 = ' ' "Character 100
* TEXTLINE3 = ' ' "Character 100
TITEL = "Screens, Title Text
VALUELENGTH = "
* VALUEOBLIGATORY = ' ' "General Flag
* START_COLUMN = 25 "Screens, vertical cursor position at PAI
* START_ROW = 6 "Screens, vertical cursor position at PAI
CHANGING
* VALUE = "Character 100
EXCEPTIONS
ACTION_CANCELED_BY_USER = 1
IMPORTING Parameters details for GRM_POPUP_TO_GET_ONE_VALUE
TEXTLINE1 - Character 100
Data type: CHAR100SMOptional: No
Call by Reference: No ( called with pass by value option)
TEXTLINE2 - Character 100
Data type: CHAR100SMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEXTLINE3 - Character 100
Data type: CHAR100SMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TITEL - Screens, Title Text
Data type: SYTITLEOptional: No
Call by Reference: No ( called with pass by value option)
VALUELENGTH -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
VALUEOBLIGATORY - General Flag
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_COLUMN - Screens, vertical cursor position at PAI
Data type: SYCUROWDefault: 25
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_ROW - Screens, vertical cursor position at PAI
Data type: SYCUROWDefault: 6
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for GRM_POPUP_TO_GET_ONE_VALUE
VALUE - Character 100
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ACTION_CANCELED_BY_USER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRM_POPUP_TO_GET_ONE_VALUE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_value | TYPE STRING, " | |||
| lv_textline1 | TYPE CHAR100SM, " | |||
| lv_action_canceled_by_user | TYPE CHAR100SM, " | |||
| lv_textline2 | TYPE CHAR100SM, " SPACE | |||
| lv_textline3 | TYPE CHAR100SM, " SPACE | |||
| lv_titel | TYPE SYTITLE, " | |||
| lv_valuelength | TYPE I, " | |||
| lv_valueobligatory | TYPE FLAG, " SPACE | |||
| lv_start_column | TYPE SYCUROW, " 25 | |||
| lv_start_row | TYPE SYCUROW. " 6 |
|   CALL FUNCTION 'GRM_POPUP_TO_GET_ONE_VALUE' " |
| EXPORTING | ||
| TEXTLINE1 | = lv_textline1 | |
| TEXTLINE2 | = lv_textline2 | |
| TEXTLINE3 | = lv_textline3 | |
| TITEL | = lv_titel | |
| VALUELENGTH | = lv_valuelength | |
| VALUEOBLIGATORY | = lv_valueobligatory | |
| START_COLUMN | = lv_start_column | |
| START_ROW | = lv_start_row | |
| CHANGING | ||
| VALUE | = lv_value | |
| EXCEPTIONS | ||
| ACTION_CANCELED_BY_USER = 1 | ||
| . " GRM_POPUP_TO_GET_ONE_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM GRM_POPUP_TO_GET_ONE_VALUE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| DATA(ld_textline2) | = ' '. | |||
| DATA(ld_textline3) | = ' '. | |||
| DATA(ld_valueobligatory) | = ' '. | |||
| DATA(ld_start_column) | = 25. | |||
| DATA(ld_start_row) | = 6. | |||
Search for further information about these or an SAP related objects