SAP LXE_XT_API_GET_LANGS_FOR_OBJ Function Module for Get Available Languages









LXE_XT_API_GET_LANGS_FOR_OBJ is a standard lxe xt api get langs for obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Available 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 xt api get langs for obj FM, simply by entering the name LXE_XT_API_GET_LANGS_FOR_OBJ 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_LANGS_FOR_OBJ 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_LANGS_FOR_OBJ'"Get Available Languages
EXPORTING
TRL_AREA = "Translation Area
OBJNAME_EXT = "Name of Translation Object

IMPORTING
ORIG_LANG = "Original Language
TRL_LANGS_TAB = "Languages

EXCEPTIONS
HASH_ERROR = 1 OBJECT_DOES_NOT_EXIST = 2
.



IMPORTING Parameters details for LXE_XT_API_GET_LANGS_FOR_OBJ

TRL_AREA - Translation Area

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

OBJNAME_EXT - Name of Translation Object

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

EXPORTING Parameters details for LXE_XT_API_GET_LANGS_FOR_OBJ

ORIG_LANG - Original Language

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

TRL_LANGS_TAB - Languages

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

EXCEPTIONS details

HASH_ERROR -

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

OBJECT_DOES_NOT_EXIST -

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_LANGS_FOR_OBJ 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_trl_area  TYPE LXECUSTMNR, "   
lv_orig_lang  TYPE LXEISOLANG, "   
lv_hash_error  TYPE LXEISOLANG, "   
lv_objname_ext  TYPE LXESTRING, "   
lv_trl_langs_tab  TYPE LXE_TT_LXEISOLANG, "   
lv_object_does_not_exist  TYPE LXE_TT_LXEISOLANG. "   

  CALL FUNCTION 'LXE_XT_API_GET_LANGS_FOR_OBJ'  "Get Available Languages
    EXPORTING
         TRL_AREA = lv_trl_area
         OBJNAME_EXT = lv_objname_ext
    IMPORTING
         ORIG_LANG = lv_orig_lang
         TRL_LANGS_TAB = lv_trl_langs_tab
    EXCEPTIONS
        HASH_ERROR = 1
        OBJECT_DOES_NOT_EXIST = 2
. " LXE_XT_API_GET_LANGS_FOR_OBJ




ABAP code using 7.40 inline data declarations to call FM LXE_XT_API_GET_LANGS_FOR_OBJ

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



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!