SAP GET_POPUP_PARAM Function Module for Analysis of feedback from graphic dialog box
GET_POPUP_PARAM is a standard get popup param SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Analysis of feedback from graphic dialog box processing and below is the pattern details for this FM, 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 get popup param FM, simply by entering the name GET_POPUP_PARAM into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRAP
Program Name: SAPLGRAP
Main Program: SAPLGRAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_POPUP_PARAM 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 'GET_POPUP_PARAM'"Analysis of feedback from graphic dialog box.
IMPORTING
BTTN_ID = "ID of the pressed button
TABLES
SNUM_TAB = "Table with scrolled number fields
EXCEPTIONS
INV_MCODE = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLGRAP_001 Customer-specific authorization check and trace for download
EXIT_SAPLGRAP_002 Customer-specific check of the upload data (for example, for viruses)
EXPORTING Parameters details for GET_POPUP_PARAM
BTTN_ID - ID of the pressed button
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GET_POPUP_PARAM
SNUM_TAB - Table with scrolled number fields
Data type: GPOPSNUMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INV_MCODE - Message cannot be evaluated
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_POPUP_PARAM 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_bttn_id | TYPE STRING, " | |||
| lt_snum_tab | TYPE STANDARD TABLE OF GPOPSNUM, " | |||
| lv_inv_mcode | TYPE GPOPSNUM. " |
|   CALL FUNCTION 'GET_POPUP_PARAM' "Analysis of feedback from graphic dialog box |
| IMPORTING | ||
| BTTN_ID | = lv_bttn_id | |
| TABLES | ||
| SNUM_TAB | = lt_snum_tab | |
| EXCEPTIONS | ||
| INV_MCODE = 1 | ||
| . " GET_POPUP_PARAM | ||
ABAP code using 7.40 inline data declarations to call FM GET_POPUP_PARAM
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.Search for further information about these or an SAP related objects