SAP POPUP_GET_VALUES_USER_CHECKED Function Module for Dialog box for requesting values, check by user exit

Search SAP Function Modules

POPUP_GET_VALUES_USER_CHECKED is a standard popup get values user checked SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dialog box for requesting values, check by user exit 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 popup get values user checked FM, simply by entering the name POPUP_GET_VALUES_USER_CHECKED into the relevant SAP transaction such as SE37 or SE38.

Function Group: SPO4
Program Name: SAPLSPO4
Main Program: SAPLSPO4
Appliation area: *
Release date: 22-Dec-1994
Mode(Normal, Remote etc): Normal Function Module
Update:

Function POPUP_GET_VALUES_USER_CHECKED 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 'POPUP_GET_VALUES_USER_CHECKED'"Dialog box for requesting values, check by user exit
  EXPORTING
   FORMNAME =  "Name of external subroutine
   POPUP_TITLE =  "Text of title line
   PROGRAMNAME =  "Name of module pool of external subroutine
*  START_COLUMN = '5' "Start column of the dialog box
*  START_ROW = '5' "Start line of the dialog box
*  NO_CHECK_FOR_FIXED_VALUES = ' ' "Flag: Deactivate check on fixed values (X)

 IMPORTING
   RETURNCODE =  "User response

TABLES
   FIELDS =  "Table fields, values and attributes

EXCEPTIONS
   ERROR_IN_FIELDS = 1 

.

IMPORTING Parameters details for POPUP_GET_VALUES_USER_CHECKED

FORMNAME - Name of external subroutine

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

POPUP_TITLE - Text of title line

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PROGRAMNAME - Name of module pool of external subroutine

Data type: TRDIR-NAME
Optional: No
Call by Reference: No ( called with pass by value option)

START_COLUMN - Start column of the dialog box

Data type:
Default: '5'
Optional: Yes
Call by Reference: No ( called with pass by value option)

START_ROW - Start line of the dialog box

Data type:
Default: '5'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_CHECK_FOR_FIXED_VALUES - Flag: Deactivate check on fixed values (X)

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for POPUP_GET_VALUES_USER_CHECKED

RETURNCODE - User response

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for POPUP_GET_VALUES_USER_CHECKED

FIELDS - Table fields, values and attributes

Data type: SVAL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_IN_FIELDS - FIELDS were transferred incorrectly

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for POPUP_GET_VALUES_USER_CHECKED 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.

ABAP code using 7.40 inline data declarations to call FM POPUP_GET_VALUES_USER_CHECKED

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