SAP RS_CUA_GET_TEXTS Function Module for Read GUI Texts
RS_CUA_GET_TEXTS is a standard rs cua get texts SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read GUI Texts 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 rs cua get texts FM, simply by entering the name RS_CUA_GET_TEXTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEU1
Program Name: SAPLSEU1
Main Program: SAPLSEU1
Appliation area: S
Release date: 01-Jul-1997
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RS_CUA_GET_TEXTS 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 'RS_CUA_GET_TEXTS'"Read GUI Texts.
EXPORTING
* LANGUAGE = ' ' "Language in which the texts should be returned
NAME = "
* DOCU_TEXTS = ' ' "Obsolete from Release 4.0
IMPORTING
MASTER_LANGU = "Source language
TABLES
* TEXTS = "
* DTEXTS = "Obsolete from Release 4.0
* DYNAMIC_TEXTS = "Obsolete from Release 4.0
* GUI_TEXTS = "Function and menu texts
EXCEPTIONS
CUA_NOT_FOUND = 1 NO_TEXTS = 2 PROGRAM_NOT_FOUND = 3
IMPORTING Parameters details for RS_CUA_GET_TEXTS
LANGUAGE - Language in which the texts should be returned
Data type: SY-LANGUDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NAME -
Data type: TRDIR-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
DOCU_TEXTS - Obsolete from Release 4.0
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RS_CUA_GET_TEXTS
MASTER_LANGU - Source language
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RS_CUA_GET_TEXTS
TEXTS -
Data type: RSEU0_FUNOptional: Yes
Call by Reference: No ( called with pass by value option)
DTEXTS - Obsolete from Release 4.0
Data type: RSMP_DTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
DYNAMIC_TEXTS - Obsolete from Release 4.0
Data type: RSEU0_FUNDOptional: Yes
Call by Reference: No ( called with pass by value option)
GUI_TEXTS - Function and menu texts
Data type: RSMPE_TXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CUA_NOT_FOUND - User interface not found (new source)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_TEXTS - No texts were found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_NOT_FOUND - Program not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_CUA_GET_TEXTS 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: | ||||
| lt_texts | TYPE STANDARD TABLE OF RSEU0_FUN, " | |||
| lv_language | TYPE SY-LANGU, " SPACE | |||
| lv_master_langu | TYPE SY-LANGU, " | |||
| lv_cua_not_found | TYPE SY, " | |||
| lv_name | TYPE TRDIR-NAME, " | |||
| lt_dtexts | TYPE STANDARD TABLE OF RSMP_DTXT, " | |||
| lv_no_texts | TYPE RSMP_DTXT, " | |||
| lv_docu_texts | TYPE RSMP_DTXT, " SPACE | |||
| lt_dynamic_texts | TYPE STANDARD TABLE OF RSEU0_FUND, " | |||
| lv_program_not_found | TYPE RSEU0_FUND, " | |||
| lt_gui_texts | TYPE STANDARD TABLE OF RSMPE_TXT. " |
| CALL FUNCTION 'RS_CUA_GET_TEXTS' "Read GUI Texts |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| NAME | = lv_name | |
| DOCU_TEXTS | = lv_docu_texts | |
| IMPORTING | ||
| MASTER_LANGU | = lv_master_langu | |
| TABLES | ||
| TEXTS | = lt_texts | |
| DTEXTS | = lt_dtexts | |
| DYNAMIC_TEXTS | = lt_dynamic_texts | |
| GUI_TEXTS | = lt_gui_texts | |
| EXCEPTIONS | ||
| CUA_NOT_FOUND = 1 | ||
| NO_TEXTS = 2 | ||
| PROGRAM_NOT_FOUND = 3 | ||
| . " RS_CUA_GET_TEXTS | ||
ABAP code using 7.40 inline data declarations to call FM RS_CUA_GET_TEXTS
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 LANGU FROM SY INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = ' '. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_master_langu). | ||||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_name). | ||||
| DATA(ld_docu_texts) | = ' '. | |||
Search for further information about these or an SAP related objects