SAP LXE_OBJ_CONVERT_WL_OLB Function Module for NOTRANSL: Umsetzen der Objektnamen
LXE_OBJ_CONVERT_WL_OLB is a standard lxe obj convert wl olb 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: Umsetzen der Objektnamen 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 convert wl olb FM, simply by entering the name LXE_OBJ_CONVERT_WL_OLB 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_CONVERT_WL_OLB 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_CONVERT_WL_OLB'"NOTRANSL: Umsetzen der Objektnamen.
EXPORTING
IN_CUSTMNR = "Translation Area
IN_OBJTYPE = "Type of Translation Object
IN_OBJNAME = "Name of Translation Object
IMPORTING
EX_CUSTMNR = "Translation Area
EX_OBJTYPE = "Type of Translation Object
EX_OBJNAME = "Name of Translation Object
IMPORTING Parameters details for LXE_OBJ_CONVERT_WL_OLB
IN_CUSTMNR - Translation Area
Data type: LXECUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
IN_OBJTYPE - Type of Translation Object
Data type: LXEOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
IN_OBJNAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LXE_OBJ_CONVERT_WL_OLB
EX_CUSTMNR - Translation Area
Data type: LXECUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
EX_OBJTYPE - Type of Translation Object
Data type: LXEOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EX_OBJNAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXE_OBJ_CONVERT_WL_OLB 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_ex_custmnr | TYPE LXECUSTMNR, " | |||
| lv_in_custmnr | TYPE LXECUSTMNR, " | |||
| lv_ex_objtype | TYPE LXEOBJTYPE, " | |||
| lv_in_objtype | TYPE LXEOBJTYPE, " | |||
| lv_ex_objname | TYPE LXEOBJNAME, " | |||
| lv_in_objname | TYPE LXEOBJNAME. " |
|   CALL FUNCTION 'LXE_OBJ_CONVERT_WL_OLB' "NOTRANSL: Umsetzen der Objektnamen |
| EXPORTING | ||
| IN_CUSTMNR | = lv_in_custmnr | |
| IN_OBJTYPE | = lv_in_objtype | |
| IN_OBJNAME | = lv_in_objname | |
| IMPORTING | ||
| EX_CUSTMNR | = lv_ex_custmnr | |
| EX_OBJTYPE | = lv_ex_objtype | |
| EX_OBJNAME | = lv_ex_objname | |
| . " LXE_OBJ_CONVERT_WL_OLB | ||
ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_CONVERT_WL_OLB
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