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

Function LXE_OBJ_DISPLAY 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_OBJ_DISPLAY'"LXE_OBJ_DISPLAY.
EXPORTING
* S_LANG = "ISO Language ID
* START_Y = '1' "
* END_X = '116' "
* END_Y = '27' "
* TEXTKEY = '' "
* T_LANG = "ISO Language ID
* CUSTMNR = '999999' "Customer Number
OBJTYPE = "Type of Translation Object
OBJNAME = "Name of Translation Object
* FLAG_REL = '' "Single-Character Flag
* USE_TRANSFORM = 'X' "
* TITEL = '' "
* START_X = '1' "
TABLES
* LT_CONDITIONS = "
* LT_WHERECLAUS = "
IMPORTING Parameters details for LXE_OBJ_DISPLAY
S_LANG - ISO Language ID
Data type: LXEISOLANGOptional: Yes
Call by Reference: No ( called with pass by value option)
START_Y -
Data type: IDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_X -
Data type: IDefault: '116'
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_Y -
Data type: IDefault: '27'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TEXTKEY -
Data type: LXETEXTKEYDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
T_LANG - ISO Language ID
Data type: LXEISOLANGOptional: Yes
Call by Reference: No ( called with pass by value option)
CUSTMNR - Customer Number
Data type: LXECUSTMNRDefault: '999999'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJTYPE - Type of Translation Object
Data type: LXEOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJNAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
FLAG_REL - Single-Character Flag
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
USE_TRANSFORM -
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TITEL -
Data type: CDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_X -
Data type: IDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LXE_OBJ_DISPLAY
LT_CONDITIONS -
Data type: LXE_TABLE_SEL_KEYOptional: Yes
Call by Reference: Yes
LT_WHERECLAUS -
Data type: RSDSWHEREOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for LXE_OBJ_DISPLAY 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_s_lang | TYPE LXEISOLANG, " | |||
| lt_lt_conditions | TYPE STANDARD TABLE OF LXE_TABLE_SEL_KEY, " | |||
| lv_start_y | TYPE I, " '1' | |||
| lv_end_x | TYPE I, " '116' | |||
| lv_end_y | TYPE I, " '27' | |||
| lv_textkey | TYPE LXETEXTKEY, " '' | |||
| lv_t_lang | TYPE LXEISOLANG, " | |||
| lt_lt_whereclaus | TYPE STANDARD TABLE OF RSDSWHERE, " | |||
| lv_custmnr | TYPE LXECUSTMNR, " '999999' | |||
| lv_objtype | TYPE LXEOBJTYPE, " | |||
| lv_objname | TYPE LXEOBJNAME, " | |||
| lv_flag_rel | TYPE CHAR1, " '' | |||
| lv_use_transform | TYPE CHAR1, " 'X' | |||
| lv_titel | TYPE C, " '' | |||
| lv_start_x | TYPE I. " '1' |
|   CALL FUNCTION 'LXE_OBJ_DISPLAY' "LXE_OBJ_DISPLAY |
| EXPORTING | ||
| S_LANG | = lv_s_lang | |
| START_Y | = lv_start_y | |
| END_X | = lv_end_x | |
| END_Y | = lv_end_y | |
| TEXTKEY | = lv_textkey | |
| T_LANG | = lv_t_lang | |
| CUSTMNR | = lv_custmnr | |
| OBJTYPE | = lv_objtype | |
| OBJNAME | = lv_objname | |
| FLAG_REL | = lv_flag_rel | |
| USE_TRANSFORM | = lv_use_transform | |
| TITEL | = lv_titel | |
| START_X | = lv_start_x | |
| TABLES | ||
| LT_CONDITIONS | = lt_lt_conditions | |
| LT_WHERECLAUS | = lt_lt_whereclaus | |
| . " LXE_OBJ_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_DISPLAY
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_start_y) | = '1'. | |||
| DATA(ld_end_x) | = '116'. | |||
| DATA(ld_end_y) | = '27'. | |||
| DATA(ld_textkey) | = ''. | |||
| DATA(ld_custmnr) | = '999999'. | |||
| DATA(ld_flag_rel) | = ''. | |||
| DATA(ld_use_transform) | = 'X'. | |||
| DATA(ld_titel) | = ''. | |||
| DATA(ld_start_x) | = '1'. | |||
Search for further information about these or an SAP related objects