SAP GRAPH_GET_LANGUAGEFILE Function Module for Create a language file from table TGUI, RFC interface for MAKE
GRAPH_GET_LANGUAGEFILE is a standard graph get languagefile SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create a language file from table TGUI, RFC interface for MAKE 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 graph get languagefile FM, simply by entering the name GRAPH_GET_LANGUAGEFILE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GSPR
Program Name: SAPLGSPR
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRAPH_GET_LANGUAGEFILE 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 'GRAPH_GET_LANGUAGEFILE'"Create a language file from table TGUI, RFC interface for MAKE.
EXPORTING
LANGUAGE = "
PROJECT = "
IMPORTING
COUNT_ALL = "
COUNT_CUR = "
TABLES
LANGUAGE_TAB = "
EXCEPTIONS
INVALID_LANGUAGE = 1 INVALID_PROJECT = 2
IMPORTING Parameters details for GRAPH_GET_LANGUAGEFILE
LANGUAGE -
Data type: TGUI-LANGUAGEOptional: No
Call by Reference: No ( called with pass by value option)
PROJECT -
Data type: TGUI-PROJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRAPH_GET_LANGUAGEFILE
COUNT_ALL -
Data type: SY-INDEXOptional: No
Call by Reference: No ( called with pass by value option)
COUNT_CUR -
Data type: SY-INDEXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRAPH_GET_LANGUAGEFILE
LANGUAGE_TAB -
Data type: TGUIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_LANGUAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PROJECT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRAPH_GET_LANGUAGEFILE 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 TGUI-LANGUAGE, " | |||
| lv_count_all | TYPE SY-INDEX, " | |||
| lt_language_tab | TYPE STANDARD TABLE OF TGUI, " | |||
| lv_invalid_language | TYPE TGUI, " | |||
| lv_project | TYPE TGUI-PROJECT, " | |||
| lv_count_cur | TYPE SY-INDEX, " | |||
| lv_invalid_project | TYPE SY. " |
|   CALL FUNCTION 'GRAPH_GET_LANGUAGEFILE' "Create a language file from table TGUI, RFC interface for MAKE |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| PROJECT | = lv_project | |
| IMPORTING | ||
| COUNT_ALL | = lv_count_all | |
| COUNT_CUR | = lv_count_cur | |
| TABLES | ||
| LANGUAGE_TAB | = lt_language_tab | |
| EXCEPTIONS | ||
| INVALID_LANGUAGE = 1 | ||
| INVALID_PROJECT = 2 | ||
| . " GRAPH_GET_LANGUAGEFILE | ||
ABAP code using 7.40 inline data declarations to call FM GRAPH_GET_LANGUAGEFILE
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.| "SELECT single LANGUAGE FROM TGUI INTO @DATA(ld_language). | ||||
| "SELECT single INDEX FROM SY INTO @DATA(ld_count_all). | ||||
| "SELECT single PROJECT FROM TGUI INTO @DATA(ld_project). | ||||
| "SELECT single INDEX FROM SY INTO @DATA(ld_count_cur). | ||||
Search for further information about these or an SAP related objects