SAP SDU_LANGUAGE_GET Function Module for
SDU_LANGUAGE_GET is a standard sdu language get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sdu language get FM, simply by entering the name SDU_LANGUAGE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDU2
Program Name: SAPLSDU2
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDU_LANGUAGE_GET 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 'SDU_LANGUAGE_GET'".
EXPORTING
OBJ_NAME = "Name of the object to be read
OBJ_TYPE = "Type of object to be read (UDMO, UENO, UCLO)
IMPORTING
MASTER_LANGUAGE = "Maintenance language of the object
EXCEPTIONS
TADIR_FAULT = 1
IMPORTING Parameters details for SDU_LANGUAGE_GET
OBJ_NAME - Name of the object to be read
Data type: TADIR-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE - Type of object to be read (UDMO, UENO, UCLO)
Data type: TADIR-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SDU_LANGUAGE_GET
MASTER_LANGUAGE - Maintenance language of the object
Data type: TADIR-MASTERLANGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TADIR_FAULT - Error calling TADIR interface
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SDU_LANGUAGE_GET 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_obj_name | TYPE TADIR-OBJ_NAME, " | |||
| lv_tadir_fault | TYPE TADIR, " | |||
| lv_master_language | TYPE TADIR-MASTERLANG, " | |||
| lv_obj_type | TYPE TADIR-OBJECT. " |
|   CALL FUNCTION 'SDU_LANGUAGE_GET' " |
| EXPORTING | ||
| OBJ_NAME | = lv_obj_name | |
| OBJ_TYPE | = lv_obj_type | |
| IMPORTING | ||
| MASTER_LANGUAGE | = lv_master_language | |
| EXCEPTIONS | ||
| TADIR_FAULT = 1 | ||
| . " SDU_LANGUAGE_GET | ||
ABAP code using 7.40 inline data declarations to call FM SDU_LANGUAGE_GET
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 OBJ_NAME FROM TADIR INTO @DATA(ld_obj_name). | ||||
| "SELECT single MASTERLANG FROM TADIR INTO @DATA(ld_master_language). | ||||
| "SELECT single OBJECT FROM TADIR INTO @DATA(ld_obj_type). | ||||
Search for further information about these or an SAP related objects