SAP LXE_LOG_REQUEST_DISPLAY Function Module for NOTRANSL: Aufträge/Aufgaben anzeigen
LXE_LOG_REQUEST_DISPLAY is a standard lxe log request 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 NOTRANSL: Aufträge/Aufgaben anzeigen 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 log request display FM, simply by entering the name LXE_LOG_REQUEST_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_LOG_EXPORT
Program Name: SAPLLXE_LOG_EXPORT
Main Program: SAPLLXE_LOG_EXPORT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_LOG_REQUEST_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_LOG_REQUEST_DISPLAY'"NOTRANSL: Aufträge/Aufgaben anzeigen.
EXPORTING
* ISOLANG = "Translation Language
* UNAME = "User Name
EXCEPTIONS
NOTHING_FOUND = 1
IMPORTING Parameters details for LXE_LOG_REQUEST_DISPLAY
ISOLANG - Translation Language
Data type: LXEISOLANGOptional: Yes
Call by Reference: Yes
UNAME - User Name
Data type: SYUNAMEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOTHING_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXE_LOG_REQUEST_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_isolang | TYPE LXEISOLANG, " | |||
| lv_nothing_found | TYPE LXEISOLANG, " | |||
| lv_uname | TYPE SYUNAME. " |
|   CALL FUNCTION 'LXE_LOG_REQUEST_DISPLAY' "NOTRANSL: Aufträge/Aufgaben anzeigen |
| EXPORTING | ||
| ISOLANG | = lv_isolang | |
| UNAME | = lv_uname | |
| EXCEPTIONS | ||
| NOTHING_FOUND = 1 | ||
| . " LXE_LOG_REQUEST_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM LXE_LOG_REQUEST_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.Search for further information about these or an SAP related objects