SAP RSAR_INFOOBJECTS_GET_TEXTS Function Module for Get InfoObjects text and technical details
RSAR_INFOOBJECTS_GET_TEXTS is a standard rsar infoobjects 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 Get InfoObjects text and technical details 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 rsar infoobjects get texts FM, simply by entering the name RSAR_INFOOBJECTS_GET_TEXTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAC
Program Name: SAPLRSAC
Main Program: SAPLRSAC
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAR_INFOOBJECTS_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 'RSAR_INFOOBJECTS_GET_TEXTS'"Get InfoObjects text and technical details.
EXPORTING
* I_LANGU = SY-LANGU "Requested Language
IMPORTING
E_NOT_ALL_ACTIVE = "Not all information objects are present
E_T_IOBJ_DETAIL = "Detailed technical description of the InfoObject
E_T_IOBJ_WITH_ICON = "Copy of C_T_IOBJ plus icon
CHANGING
C_T_IOBJ = "Input / Output text table
IMPORTING Parameters details for RSAR_INFOOBJECTS_GET_TEXTS
I_LANGU - Requested Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSAR_INFOOBJECTS_GET_TEXTS
E_NOT_ALL_ACTIVE - Not all information objects are present
Data type: RS_CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
E_T_IOBJ_DETAIL - Detailed technical description of the InfoObject
Data type: RSARC_T_RSFIELDTXTOptional: No
Call by Reference: No ( called with pass by value option)
E_T_IOBJ_WITH_ICON - Copy of C_T_IOBJ plus icon
Data type: RSARC_T_IOBJOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RSAR_INFOOBJECTS_GET_TEXTS
C_T_IOBJ - Input / Output text table
Data type: RSD_T_IOBJOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAR_INFOOBJECTS_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: | ||||
| lv_i_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_c_t_iobj | TYPE RSD_T_IOBJ, " | |||
| lv_e_not_all_active | TYPE RS_CHAR1, " | |||
| lv_e_t_iobj_detail | TYPE RSARC_T_RSFIELDTXT, " | |||
| lv_e_t_iobj_with_icon | TYPE RSARC_T_IOBJ. " |
|   CALL FUNCTION 'RSAR_INFOOBJECTS_GET_TEXTS' "Get InfoObjects text and technical details |
| EXPORTING | ||
| I_LANGU | = lv_i_langu | |
| IMPORTING | ||
| E_NOT_ALL_ACTIVE | = lv_e_not_all_active | |
| E_T_IOBJ_DETAIL | = lv_e_t_iobj_detail | |
| E_T_IOBJ_WITH_ICON | = lv_e_t_iobj_with_icon | |
| CHANGING | ||
| C_T_IOBJ | = lv_c_t_iobj | |
| . " RSAR_INFOOBJECTS_GET_TEXTS | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_INFOOBJECTS_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_i_langu). | ||||
| DATA(ld_i_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects