SAP DISPLAY_LIST Function Module for List object display (ABAPLIST)
DISPLAY_LIST is a standard display list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for List object display (ABAPLIST) 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 display list FM, simply by entering the name DISPLAY_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLST
Program Name: SAPLSLST
Main Program: SAPLSLST
Appliation area: S
Release date: 16-Jan-1998
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function DISPLAY_LIST 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 'DISPLAY_LIST'"List object display (ABAPLIST).
EXPORTING
* FULLSCREEN = "List as fullscreen display (or pop-up)
* CALLER_HANDLES_EVENTS = "
* STARTING_X = 10 "Popup Coordinates
* STARTING_Y = 10 "Popup Coordinates
* ENDING_X = 60 "Popup Coordinates
* ENDING_Y = 20 "Popup Coordinates
IMPORTING
USER_COMMAND = "
TABLES
LISTOBJECT = "Container for list object
EXCEPTIONS
EMPTY_LIST = 1
IMPORTING Parameters details for DISPLAY_LIST
FULLSCREEN - List as fullscreen display (or pop-up)
Data type: SY-MARKYOptional: Yes
Call by Reference: No ( called with pass by value option)
CALLER_HANDLES_EVENTS -
Data type: SY-MARKYOptional: Yes
Call by Reference: No ( called with pass by value option)
STARTING_X - Popup Coordinates
Data type: IDefault: 10
Optional: Yes
Call by Reference: No ( called with pass by value option)
STARTING_Y - Popup Coordinates
Data type: IDefault: 10
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENDING_X - Popup Coordinates
Data type: IDefault: 60
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENDING_Y - Popup Coordinates
Data type: IDefault: 20
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DISPLAY_LIST
USER_COMMAND -
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DISPLAY_LIST
LISTOBJECT - Container for list object
Data type: ABAPLISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EMPTY_LIST - The list object transported is empty
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DISPLAY_LIST 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_empty_list | TYPE STRING, " | |||
lv_fullscreen | TYPE SY-MARKY, " | |||
lt_listobject | TYPE STANDARD TABLE OF ABAPLIST, " | |||
lv_user_command | TYPE SY-UCOMM, " | |||
lv_caller_handles_events | TYPE SY-MARKY, " | |||
lv_starting_x | TYPE I, " 10 | |||
lv_starting_y | TYPE I, " 10 | |||
lv_ending_x | TYPE I, " 60 | |||
lv_ending_y | TYPE I. " 20 |
  CALL FUNCTION 'DISPLAY_LIST' "List object display (ABAPLIST) |
EXPORTING | ||
FULLSCREEN | = lv_fullscreen | |
CALLER_HANDLES_EVENTS | = lv_caller_handles_events | |
STARTING_X | = lv_starting_x | |
STARTING_Y | = lv_starting_y | |
ENDING_X | = lv_ending_x | |
ENDING_Y | = lv_ending_y | |
IMPORTING | ||
USER_COMMAND | = lv_user_command | |
TABLES | ||
LISTOBJECT | = lt_listobject | |
EXCEPTIONS | ||
EMPTY_LIST = 1 | ||
. " DISPLAY_LIST |
ABAP code using 7.40 inline data declarations to call FM DISPLAY_LIST
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."SELECT single MARKY FROM SY INTO @DATA(ld_fullscreen). | ||||
"SELECT single UCOMM FROM SY INTO @DATA(ld_user_command). | ||||
"SELECT single MARKY FROM SY INTO @DATA(ld_caller_handles_events). | ||||
DATA(ld_starting_x) | = 10. | |||
DATA(ld_starting_y) | = 10. | |||
DATA(ld_ending_x) | = 60. | |||
DATA(ld_ending_y) | = 20. | |||
Search for further information about these or an SAP related objects