SAP RM_DDIC_TEXTS_GET Function Module for RM: Lesen von Texten zu einem Dictionary-Objekt
RM_DDIC_TEXTS_GET is a standard rm ddic texts get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: Lesen von Texten zu einem Dictionary-Objekt 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 rm ddic texts get FM, simply by entering the name RM_DDIC_TEXTS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMDI
Program Name: SAPLRMDI
Main Program: SAPLRMDI
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DDIC_TEXTS_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 'RM_DDIC_TEXTS_GET'"RM: Lesen von Texten zu einem Dictionary-Objekt.
EXPORTING
I_NAME = "Objektname
I_TYPE = "Objekttyp (Tabelle, Datenelement, ...)
* I_LANGU = SY-LANGU "Sprache (optional)
IMPORTING
E_DDTXT = "Kurzbeschreibung des Objekts
E_HDTXT = "Überschrift (nur bei Datenelementen)
E_STXT = "Feldbezeichner kurz (nur bei Datenelementen)
E_MTXT = "Feldbezeichner mittel (nur bei Datenelementen)
E_LTXT = "Feldbezeichner lang (nur bei Datenelementen)
EXCEPTIONS
OBJTYPE_NOT_SUPPORTED = 1 ILLEGAL_INPUT = 2
IMPORTING Parameters details for RM_DDIC_TEXTS_GET
I_NAME - Objektname
Data type: RMDI_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TYPE - Objekttyp (Tabelle, Datenelement, ...)
Data type: RMDI_OBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGU - Sprache (optional)
Data type: RMDI_LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_DDIC_TEXTS_GET
E_DDTXT - Kurzbeschreibung des Objekts
Data type: RMDI_DDTXTOptional: No
Call by Reference: No ( called with pass by value option)
E_HDTXT - Überschrift (nur bei Datenelementen)
Data type: RMDI_HDTXTOptional: No
Call by Reference: No ( called with pass by value option)
E_STXT - Feldbezeichner kurz (nur bei Datenelementen)
Data type: RMDI_STXTOptional: No
Call by Reference: No ( called with pass by value option)
E_MTXT - Feldbezeichner mittel (nur bei Datenelementen)
Data type: RMDI_MTXTOptional: No
Call by Reference: No ( called with pass by value option)
E_LTXT - Feldbezeichner lang (nur bei Datenelementen)
Data type: RMDI_LTXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJTYPE_NOT_SUPPORTED - Der geforderte Objekttyp wird nicht unterstützt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_INPUT - Wert nicht erlaubt (z.B. Objekt nicht vorhanden)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_DDIC_TEXTS_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_i_name | TYPE RMDI_NAME, " | |||
| lv_e_ddtxt | TYPE RMDI_DDTXT, " | |||
| lv_objtype_not_supported | TYPE RMDI_DDTXT, " | |||
| lv_i_type | TYPE RMDI_OBJTYPE, " | |||
| lv_e_hdtxt | TYPE RMDI_HDTXT, " | |||
| lv_illegal_input | TYPE RMDI_HDTXT, " | |||
| lv_e_stxt | TYPE RMDI_STXT, " | |||
| lv_i_langu | TYPE RMDI_LANGU, " SY-LANGU | |||
| lv_e_mtxt | TYPE RMDI_MTXT, " | |||
| lv_e_ltxt | TYPE RMDI_LTXT. " |
|   CALL FUNCTION 'RM_DDIC_TEXTS_GET' "RM: Lesen von Texten zu einem Dictionary-Objekt |
| EXPORTING | ||
| I_NAME | = lv_i_name | |
| I_TYPE | = lv_i_type | |
| I_LANGU | = lv_i_langu | |
| IMPORTING | ||
| E_DDTXT | = lv_e_ddtxt | |
| E_HDTXT | = lv_e_hdtxt | |
| E_STXT | = lv_e_stxt | |
| E_MTXT | = lv_e_mtxt | |
| E_LTXT | = lv_e_ltxt | |
| EXCEPTIONS | ||
| OBJTYPE_NOT_SUPPORTED = 1 | ||
| ILLEGAL_INPUT = 2 | ||
| . " RM_DDIC_TEXTS_GET | ||
ABAP code using 7.40 inline data declarations to call FM RM_DDIC_TEXTS_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.| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects