SAP LXE_LANG_CREATE Function Module for NOTRANSL: Übersetzungssprache anlegen
LXE_LANG_CREATE is a standard lxe lang create 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: Übersetzungssprache anlegen 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 create FM, simply by entering the name LXE_LANG_CREATE 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_CREATE 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_CREATE'"NOTRANSL: Übersetzungssprache anlegen.
EXPORTING
LANGUAGE = "ISO Language ID
* PRIORITY = '99' "Priority for translation environment
* SERVER = '' "Server Name
IMPORTING Parameters details for LXE_LANG_CREATE
LANGUAGE - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
PRIORITY - Priority for translation environment
Data type: NUM2Default: '99'
Optional: Yes
Call by Reference: Yes
SERVER - Server Name
Data type: MSNAME2Default: ''
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for LXE_LANG_CREATE 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_language | TYPE LXEISOLANG, " | |||
| lv_priority | TYPE NUM2, " '99' | |||
| lv_server | TYPE MSNAME2. " '' |
|   CALL FUNCTION 'LXE_LANG_CREATE' "NOTRANSL: Übersetzungssprache anlegen |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| PRIORITY | = lv_priority | |
| SERVER | = lv_server | |
| . " LXE_LANG_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM LXE_LANG_CREATE
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_priority) | = '99'. | |||
| DATA(ld_server) | = ''. | |||
Search for further information about these or an SAP related objects