SAP LXE_LANG_CLIENT_DISPLAY2 Function Module for Translation Languages









LXE_LANG_CLIENT_DISPLAY2 is a standard lxe lang client display2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Translation Languages 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 lang client display2 FM, simply by entering the name LXE_LANG_CLIENT_DISPLAY2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_LANG
Program Name: SAPLLXE_LANG
Main Program: SAPLLXE_LANG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function LXE_LANG_CLIENT_DISPLAY2 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_LANG_CLIENT_DISPLAY2'"Translation Languages
EXPORTING
* DISPLAY_ONLY = 'X' "Single-Character Flag
* START_X = 0 "
* START_Y = 0 "
* END_X = 0 "
* END_Y = 0 "
.



IMPORTING Parameters details for LXE_LANG_CLIENT_DISPLAY2

DISPLAY_ONLY - Single-Character Flag

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: Yes

START_X -

Data type: I
Optional: Yes
Call by Reference: Yes

START_Y -

Data type: I
Optional: Yes
Call by Reference: Yes

END_X -

Data type: I
Optional: Yes
Call by Reference: Yes

END_Y -

Data type: I
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LXE_LANG_CLIENT_DISPLAY2 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_display_only  TYPE CHAR1, "   'X'
lv_start_x  TYPE I, "   0
lv_start_y  TYPE I, "   0
lv_end_x  TYPE I, "   0
lv_end_y  TYPE I. "   0

  CALL FUNCTION 'LXE_LANG_CLIENT_DISPLAY2'  "Translation Languages
    EXPORTING
         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
. " LXE_LANG_CLIENT_DISPLAY2




ABAP code using 7.40 inline data declarations to call FM LXE_LANG_CLIENT_DISPLAY2

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_display_only) = 'X'.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!