SAP LXE_LIST_READ_DB Function Module for
LXE_LIST_READ_DB is a standard lxe list read db 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 lxe list read db FM, simply by entering the name LXE_LIST_READ_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_LIST
Program Name: SAPLLXE_LIST
Main Program: SAPLLXE_LIST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_LIST_READ_DB 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 'LXE_LIST_READ_DB'".
EXPORTING
LISTE = "
IMPORTING
PSTATUS = "
TABLES
EX_LIST2 = "
IMPORTING Parameters details for LXE_LIST_READ_DB
LISTE -
Data type: LXE0020LINOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LXE_LIST_READ_DB
PSTATUS -
Data type: LXESTATPRCOptional: No
Call by Reference: Yes
TABLES Parameters details for LXE_LIST_READ_DB
EX_LIST2 -
Data type: LXE_LIST2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_LIST_READ_DB 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_liste | TYPE LXE0020LIN, " | |||
| lv_pstatus | TYPE LXESTATPRC, " | |||
| lt_ex_list2 | TYPE STANDARD TABLE OF LXE_LIST2. " |
|   CALL FUNCTION 'LXE_LIST_READ_DB' " |
| EXPORTING | ||
| LISTE | = lv_liste | |
| IMPORTING | ||
| PSTATUS | = lv_pstatus | |
| TABLES | ||
| EX_LIST2 | = lt_ex_list2 | |
| . " LXE_LIST_READ_DB | ||
ABAP code using 7.40 inline data declarations to call FM LXE_LIST_READ_DB
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