SAP LXE_CUSTMNR_SELECT_MULTIPLE Function Module for LXE_CUSTMNR_SELECT_MULTIPLE
LXE_CUSTMNR_SELECT_MULTIPLE is a standard lxe custmnr select multiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LXE_CUSTMNR_SELECT_MULTIPLE 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 lxe custmnr select multiple FM, simply by entering the name LXE_CUSTMNR_SELECT_MULTIPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_CUSTMNR
Program Name: SAPLLXE_CUSTMNR
Main Program: SAPLLXE_CUSTMNR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_CUSTMNR_SELECT_MULTIPLE 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_CUSTMNR_SELECT_MULTIPLE'"LXE_CUSTMNR_SELECT_MULTIPLE.
EXPORTING
* TITEL = '' "
* CUSTTYPE = '*' "Single-Character Flag
* DISPLAY_ONLY = 'X' "Single-Character Flag
* START_X = '' "
* START_Y = '' "
* END_X = '' "
* END_Y = '' "
IMPORTING
SEL_DONE = "Single-Character Flag
TABLES
* EX_CUSTMNR = "Translation Areas
* EX_CUSTMNR2 = "
* MARK_CUSTMNR = "Translation Areas
EXCEPTIONS
DB_PROBLEM = 1
IMPORTING Parameters details for LXE_CUSTMNR_SELECT_MULTIPLE
TITEL -
Data type: CDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
CUSTTYPE - Single-Character Flag
Data type: CHAR1Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_ONLY - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_X -
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_Y -
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_X -
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_Y -
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LXE_CUSTMNR_SELECT_MULTIPLE
SEL_DONE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
TABLES Parameters details for LXE_CUSTMNR_SELECT_MULTIPLE
EX_CUSTMNR - Translation Areas
Data type: LXE_CUSTMNROptional: Yes
Call by Reference: Yes
EX_CUSTMNR2 -
Data type: LXE_CUSTMNR2Optional: Yes
Call by Reference: Yes
MARK_CUSTMNR - Translation Areas
Data type: LXE_CUSTMNROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DB_PROBLEM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXE_CUSTMNR_SELECT_MULTIPLE 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_titel | TYPE C, " '' | |||
| lv_sel_done | TYPE CHAR1, " | |||
| lv_db_problem | TYPE CHAR1, " | |||
| lt_ex_custmnr | TYPE STANDARD TABLE OF LXE_CUSTMNR, " | |||
| lv_custtype | TYPE CHAR1, " '*' | |||
| lt_ex_custmnr2 | TYPE STANDARD TABLE OF LXE_CUSTMNR2, " | |||
| lv_display_only | TYPE CHAR1, " 'X' | |||
| lt_mark_custmnr | TYPE STANDARD TABLE OF LXE_CUSTMNR, " | |||
| lv_start_x | TYPE I, " '' | |||
| lv_start_y | TYPE I, " '' | |||
| lv_end_x | TYPE I, " '' | |||
| lv_end_y | TYPE I. " '' |
|   CALL FUNCTION 'LXE_CUSTMNR_SELECT_MULTIPLE' "LXE_CUSTMNR_SELECT_MULTIPLE |
| EXPORTING | ||
| TITEL | = lv_titel | |
| CUSTTYPE | = lv_custtype | |
| DISPLAY_ONLY | = lv_display_only | |
| START_X | = lv_start_x | |
| START_Y | = lv_start_y | |
| END_X | = lv_end_x | |
| END_Y | = lv_end_y | |
| IMPORTING | ||
| SEL_DONE | = lv_sel_done | |
| TABLES | ||
| EX_CUSTMNR | = lt_ex_custmnr | |
| EX_CUSTMNR2 | = lt_ex_custmnr2 | |
| MARK_CUSTMNR | = lt_mark_custmnr | |
| EXCEPTIONS | ||
| DB_PROBLEM = 1 | ||
| . " LXE_CUSTMNR_SELECT_MULTIPLE | ||
ABAP code using 7.40 inline data declarations to call FM LXE_CUSTMNR_SELECT_MULTIPLE
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_titel) | = ''. | |||
| DATA(ld_custtype) | = '*'. | |||
| DATA(ld_display_only) | = 'X'. | |||
| DATA(ld_start_x) | = ''. | |||
| DATA(ld_start_y) | = ''. | |||
| DATA(ld_end_x) | = ''. | |||
| DATA(ld_end_y) | = ''. | |||
Search for further information about these or an SAP related objects