SAP READ_MULTIPLE_TEXTS Function Module for Read Multiple Texts (Selection Using Wildcards or Ranges Tables)
READ_MULTIPLE_TEXTS is a standard read multiple 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 Multiple Texts (Selection Using Wildcards or Ranges Tables) 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 read multiple texts FM, simply by entering the name READ_MULTIPLE_TEXTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXD
Program Name: SAPLSTXD
Main Program: SAPLSTXD
Appliation area:
Release date: 29-Feb-2016
Mode(Normal, Remote etc): Normal Function Module
Update:

Function READ_MULTIPLE_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 'READ_MULTIPLE_TEXTS'"Read Multiple Texts (Selection Using Wildcards or Ranges Tables).
EXPORTING
* CLIENT = SY-MANDT "Client
* ARCHIVE_HANDLE = 0 "ABAP System Field: Row Index of Internal Tables
* LOCAL_CAT = ' ' "Text catalog local
* WILDCARD_PLUS = ' ' "
* NAME = '*' "Text Name of the Texts to Be Read
* OBJECT = '*' "Text object of texts to be searched for
* ID = '*' "Text ID of texts to be searched for
* LANGUAGE = '*' "Language of texts to be searched for
* NAME_RANGES = "Table for text names (RANGES)
* OBJECT_RANGES = "Table for text objects (RANGES)
* ID_RANGES = "Table for text IDs (RANGES)
* LANGUAGE_RANGES = "Table for text languages (RANGES)
IMPORTING
TEXT_TABLE = "Table with Text Headers and Content
ERROR_TABLE = "Texts with Read Errors
EXCEPTIONS
WRONG_ACCESS_TO_ARCHIVE = 1
IMPORTING Parameters details for READ_MULTIPLE_TEXTS
CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: Yes
ARCHIVE_HANDLE - ABAP System Field: Row Index of Internal Tables
Data type: SY-TABIXOptional: Yes
Call by Reference: Yes
LOCAL_CAT - Text catalog local
Data type: ABAP_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
WILDCARD_PLUS -
Data type: ABAP_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
NAME - Text Name of the Texts to Be Read
Data type: THEAD-TDNAMEDefault: '*'
Optional: Yes
Call by Reference: Yes
OBJECT - Text object of texts to be searched for
Data type: THEAD-TDOBJECTDefault: '*'
Optional: Yes
Call by Reference: Yes
ID - Text ID of texts to be searched for
Data type: THEAD-TDIDDefault: '*'
Optional: Yes
Call by Reference: Yes
LANGUAGE - Language of texts to be searched for
Data type: THEAD-TDSPRASDefault: '*'
Optional: Yes
Call by Reference: Yes
NAME_RANGES - Table for text names (RANGES)
Data type: TSPSRNAMEOptional: Yes
Call by Reference: Yes
OBJECT_RANGES - Table for text objects (RANGES)
Data type: TSPSROBJOptional: Yes
Call by Reference: Yes
ID_RANGES - Table for text IDs (RANGES)
Data type: TSPSRIDOptional: Yes
Call by Reference: Yes
LANGUAGE_RANGES - Table for text languages (RANGES)
Data type: TSPSRLANGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for READ_MULTIPLE_TEXTS
TEXT_TABLE - Table with Text Headers and Content
Data type: TEXT_LHOptional: No
Call by Reference: Yes
ERROR_TABLE - Texts with Read Errors
Data type: TEXT_LHOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_ACCESS_TO_ARCHIVE - Archive handle invalid for access
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for READ_MULTIPLE_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_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_text_table | TYPE TEXT_LH, " | |||
| lv_wrong_access_to_archive | TYPE TEXT_LH, " | |||
| lv_archive_handle | TYPE SY-TABIX, " 0 | |||
| lv_local_cat | TYPE ABAP_BOOL, " SPACE | |||
| lv_wildcard_plus | TYPE ABAP_BOOL, " SPACE | |||
| lv_name | TYPE THEAD-TDNAME, " '*' | |||
| lv_error_table | TYPE TEXT_LH, " | |||
| lv_object | TYPE THEAD-TDOBJECT, " '*' | |||
| lv_id | TYPE THEAD-TDID, " '*' | |||
| lv_language | TYPE THEAD-TDSPRAS, " '*' | |||
| lv_name_ranges | TYPE TSPSRNAME, " | |||
| lv_object_ranges | TYPE TSPSROBJ, " | |||
| lv_id_ranges | TYPE TSPSRID, " | |||
| lv_language_ranges | TYPE TSPSRLANG. " |
|   CALL FUNCTION 'READ_MULTIPLE_TEXTS' "Read Multiple Texts (Selection Using Wildcards or Ranges Tables) |
| EXPORTING | ||
| CLIENT | = lv_client | |
| ARCHIVE_HANDLE | = lv_archive_handle | |
| LOCAL_CAT | = lv_local_cat | |
| WILDCARD_PLUS | = lv_wildcard_plus | |
| NAME | = lv_name | |
| OBJECT | = lv_object | |
| ID | = lv_id | |
| LANGUAGE | = lv_language | |
| NAME_RANGES | = lv_name_ranges | |
| OBJECT_RANGES | = lv_object_ranges | |
| ID_RANGES | = lv_id_ranges | |
| LANGUAGE_RANGES | = lv_language_ranges | |
| IMPORTING | ||
| TEXT_TABLE | = lv_text_table | |
| ERROR_TABLE | = lv_error_table | |
| EXCEPTIONS | ||
| WRONG_ACCESS_TO_ARCHIVE = 1 | ||
| . " READ_MULTIPLE_TEXTS | ||
ABAP code using 7.40 inline data declarations to call FM READ_MULTIPLE_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 MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_archive_handle). | ||||
| DATA(ld_local_cat) | = ' '. | |||
| DATA(ld_wildcard_plus) | = ' '. | |||
| "SELECT single TDNAME FROM THEAD INTO @DATA(ld_name). | ||||
| DATA(ld_name) | = '*'. | |||
| "SELECT single TDOBJECT FROM THEAD INTO @DATA(ld_object). | ||||
| DATA(ld_object) | = '*'. | |||
| "SELECT single TDID FROM THEAD INTO @DATA(ld_id). | ||||
| DATA(ld_id) | = '*'. | |||
| "SELECT single TDSPRAS FROM THEAD INTO @DATA(ld_language). | ||||
| DATA(ld_language) | = '*'. | |||
Search for further information about these or an SAP related objects