SAP LXE_GRAPH_GET_T_LANGS Function Module for Graphs
LXE_GRAPH_GET_T_LANGS is a standard lxe graph get t langs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Graphs 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 graph get t langs FM, simply by entering the name LXE_GRAPH_GET_T_LANGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_GRAPH
Program Name: SAPLLXE_GRAPH
Main Program: SAPLLXE_GRAPH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_GRAPH_GET_T_LANGS 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_GRAPH_GET_T_LANGS'"Graphs.
EXPORTING
GRAPH = "Translation graph
IMPORTING
PSTATUS = "Process Status
TABLES
EX_T_LANGS = "Languages in Which Data is Available
IMPORTING Parameters details for LXE_GRAPH_GET_T_LANGS
GRAPH - Translation graph
Data type: LXEGRAPHOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LXE_GRAPH_GET_T_LANGS
PSTATUS - Process Status
Data type: LXESTATPRCOptional: No
Call by Reference: Yes
TABLES Parameters details for LXE_GRAPH_GET_T_LANGS
EX_T_LANGS - Languages in Which Data is Available
Data type: LXE_LANGUAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_GRAPH_GET_T_LANGS 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_graph | TYPE LXEGRAPH, " | |||
| lv_pstatus | TYPE LXESTATPRC, " | |||
| lt_ex_t_langs | TYPE STANDARD TABLE OF LXE_LANGUA. " |
|   CALL FUNCTION 'LXE_GRAPH_GET_T_LANGS' "Graphs |
| EXPORTING | ||
| GRAPH | = lv_graph | |
| IMPORTING | ||
| PSTATUS | = lv_pstatus | |
| TABLES | ||
| EX_T_LANGS | = lt_ex_t_langs | |
| . " LXE_GRAPH_GET_T_LANGS | ||
ABAP code using 7.40 inline data declarations to call FM LXE_GRAPH_GET_T_LANGS
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