SAP LXE_CUSTMNR_SELECT Function Module for LXE_CUSTMNR_SELECT
LXE_CUSTMNR_SELECT is a standard lxe custmnr select 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 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 FM, simply by entering the name LXE_CUSTMNR_SELECT 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 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'"LXE_CUSTMNR_SELECT.
EXPORTING
* TITEL = '' "Generic Type
* NEW = '' "Single-Character Flag
* CUSTTYPE = '*' "Translation Area Type
* SHOW_ONLY = '' "
* START_X = '' "Predefined Type
* START_Y = '' "Predefined Type
* END_X = '' "Predefined Type
* END_Y = '' "Predefined Type
IMPORTING
CUSTMNR = "Translation Area
CUSTKTXT = "Translation Area Short Text
LS_LXE_CUSTMNR = "Translation Areas
EXCEPTIONS
NO_SELECTION = 1 DB_PROBLEM = 2
IMPORTING Parameters details for LXE_CUSTMNR_SELECT
TITEL - Generic Type
Data type: CDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
NEW - Single-Character Flag
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
CUSTTYPE - Translation Area Type
Data type: LXECUSTTYPEDefault: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SHOW_ONLY -
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_X - Predefined Type
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_Y - Predefined Type
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_X - Predefined Type
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_Y - Predefined Type
Data type: IDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LXE_CUSTMNR_SELECT
CUSTMNR - Translation Area
Data type: LXECUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
CUSTKTXT - Translation Area Short Text
Data type: LXECUSTKTXOptional: No
Call by Reference: Yes
LS_LXE_CUSTMNR - Translation Areas
Data type: LXE_CUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SELECTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
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 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_custmnr | TYPE LXECUSTMNR, " | |||
| lv_no_selection | TYPE LXECUSTMNR, " | |||
| lv_new | TYPE CHAR1, " '' | |||
| lv_custktxt | TYPE LXECUSTKTX, " | |||
| lv_db_problem | TYPE LXECUSTKTX, " | |||
| lv_custtype | TYPE LXECUSTTYPE, " '*' | |||
| lv_ls_lxe_custmnr | TYPE LXE_CUSTMNR, " | |||
| lv_show_only | TYPE CHAR1, " '' | |||
| 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' "LXE_CUSTMNR_SELECT |
| EXPORTING | ||
| TITEL | = lv_titel | |
| NEW | = lv_new | |
| CUSTTYPE | = lv_custtype | |
| SHOW_ONLY | = lv_show_only | |
| START_X | = lv_start_x | |
| START_Y | = lv_start_y | |
| END_X | = lv_end_x | |
| END_Y | = lv_end_y | |
| IMPORTING | ||
| CUSTMNR | = lv_custmnr | |
| CUSTKTXT | = lv_custktxt | |
| LS_LXE_CUSTMNR | = lv_ls_lxe_custmnr | |
| EXCEPTIONS | ||
| NO_SELECTION = 1 | ||
| DB_PROBLEM = 2 | ||
| . " LXE_CUSTMNR_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM LXE_CUSTMNR_SELECT
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_new) | = ''. | |||
| DATA(ld_custtype) | = '*'. | |||
| DATA(ld_show_only) | = ''. | |||
| 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