SAP LXE_XT_API_GET_LANGUAGE Function Module for Export Language

Search SAP Function Modules

LXE_XT_API_GET_LANGUAGE is a standard lxe xt api get language SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export Language 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 xt api get language FM, simply by entering the name LXE_XT_API_GET_LANGUAGE into the relevant SAP transaction such as SE37 or SE38.

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

Function LXE_XT_API_GET_LANGUAGE 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_XT_API_GET_LANGUAGE'"Export Language
  EXPORTING
   TRL_AREA =  "Translation Area
   OBJNAME_EXT =  "External Object Name
   LANGUAGE =  "ISO Language ID

 IMPORTING
   XTEXT_TAB =  "Short Texts
   YTEXT_TAB =  "Long Texts
   ZTEXT_TAB =  "Special Texts
   ZBIN_TAB =  "Special Texts (Binary)

EXCEPTIONS
   INVALID_OBJECT = 1    HASH_ERROR = 2    OBJECT_DOES_NOT_EXIST = 3    ORIG_LANG_CONFLICT = 4 

.

IMPORTING Parameters details for LXE_XT_API_GET_LANGUAGE

TRL_AREA - Translation Area

Data type: LXECUSTMNR
Optional: No
Call by Reference: Yes

OBJNAME_EXT - External Object Name

Data type: STRING
Optional: No
Call by Reference: Yes

LANGUAGE - ISO Language ID

Data type: LXEISOLANG
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for LXE_XT_API_GET_LANGUAGE

XTEXT_TAB - Short Texts

Data type: LXE_TT_XTEXT_TRL
Optional: No
Call by Reference: Yes

YTEXT_TAB - Long Texts

Data type: LXE_TT_YTEXT_TRL
Optional: No
Call by Reference: Yes

ZTEXT_TAB - Special Texts

Data type: LXE_TT_ZTEXT_TRL
Optional: No
Call by Reference: Yes

ZBIN_TAB - Special Texts (Binary)

Data type: LXE_TT_ZBIN_TRL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_OBJECT -

Data type:
Optional: No
Call by Reference: Yes

HASH_ERROR -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ORIG_LANG_CONFLICT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for LXE_XT_API_GET_LANGUAGE 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.

ABAP code using 7.40 inline data declarations to call FM LXE_XT_API_GET_LANGUAGE

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