SAP RSTS_READ Function Module for Read from TemSe Object
RSTS_READ is a standard rsts read 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 from TemSe Object 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 rsts read FM, simply by entering the name RSTS_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: STMS
Program Name: SAPLSTMS
Main Program: SAPLSTMS
Appliation area: S
Release date: 10-Mar-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSTS_READ 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 'RSTS_READ'"Read from TemSe Object.
EXPORTING
* BUFFLG = '*' "Maximum Storage Length per Line
* FBHANDLE = 0 "Handle for Open Object
* MAXIX = '*' "Maximum Number of Lines to be Read (1000)
* PARTS1BY1 = ' ' "Only Part of TemSe Object Each Time
* SHOWLG = ' ' "Every Line with Length Field
* HFLAG = ' ' " Indicator for Hexadecimal Display - For Internal Use Only
IMPORTING
ALLDATA = "All Data was Read
TABLES
DATATAB = "Data Transfer
EXCEPTIONS
FB_CALL_HANDLE = 1 FB_ERROR = 2 FB_RSTS_NOCONV = 3 FB_RSTS_OTHER = 4
IMPORTING Parameters details for RSTS_READ
BUFFLG - Maximum Storage Length per Line
Data type:Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
FBHANDLE - Handle for Open Object
Data type: RSTSTYPE-FBHANDLEOptional: Yes
Call by Reference: No ( called with pass by value option)
MAXIX - Maximum Number of Lines to be Read (1000)
Data type:Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTS1BY1 - Only Part of TemSe Object Each Time
Data type: RSTSTYPE-PARTS1BY1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
SHOWLG - Every Line with Length Field
Data type: RSTSTYPE-SHOWLGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
HFLAG - Indicator for Hexadecimal Display - For Internal Use Only
Data type: RSTSTYPE-SHOWLGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSTS_READ
ALLDATA - All Data was Read
Data type: RSTSTYPE-ALLDATAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RSTS_READ
DATATAB - Data Transfer
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FB_CALL_HANDLE - Error with Handles at CALL Interface
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FB_ERROR - Function Module Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FB_RSTS_NOCONV - Required Conversion Not Possible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FB_RSTS_OTHER - Other Errors Reported by TemSe C System
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSTS_READ 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_bufflg | TYPE STRING, " '*' | |||
| lv_alldata | TYPE RSTSTYPE-ALLDATA, " | |||
| lt_datatab | TYPE STANDARD TABLE OF RSTSTYPE, " | |||
| lv_fb_call_handle | TYPE RSTSTYPE, " | |||
| lv_fbhandle | TYPE RSTSTYPE-FBHANDLE, " 0 | |||
| lv_fb_error | TYPE RSTSTYPE, " | |||
| lv_maxix | TYPE RSTSTYPE, " '*' | |||
| lv_fb_rsts_noconv | TYPE RSTSTYPE, " | |||
| lv_parts1by1 | TYPE RSTSTYPE-PARTS1BY1, " ' ' | |||
| lv_fb_rsts_other | TYPE RSTSTYPE, " | |||
| lv_showlg | TYPE RSTSTYPE-SHOWLG, " ' ' | |||
| lv_hflag | TYPE RSTSTYPE-SHOWLG. " ' ' |
|   CALL FUNCTION 'RSTS_READ' "Read from TemSe Object |
| EXPORTING | ||
| BUFFLG | = lv_bufflg | |
| FBHANDLE | = lv_fbhandle | |
| MAXIX | = lv_maxix | |
| PARTS1BY1 | = lv_parts1by1 | |
| SHOWLG | = lv_showlg | |
| HFLAG | = lv_hflag | |
| IMPORTING | ||
| ALLDATA | = lv_alldata | |
| TABLES | ||
| DATATAB | = lt_datatab | |
| EXCEPTIONS | ||
| FB_CALL_HANDLE = 1 | ||
| FB_ERROR = 2 | ||
| FB_RSTS_NOCONV = 3 | ||
| FB_RSTS_OTHER = 4 | ||
| . " RSTS_READ | ||
ABAP code using 7.40 inline data declarations to call FM RSTS_READ
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_bufflg) | = '*'. | |||
| "SELECT single ALLDATA FROM RSTSTYPE INTO @DATA(ld_alldata). | ||||
| "SELECT single FBHANDLE FROM RSTSTYPE INTO @DATA(ld_fbhandle). | ||||
| DATA(ld_maxix) | = '*'. | |||
| "SELECT single PARTS1BY1 FROM RSTSTYPE INTO @DATA(ld_parts1by1). | ||||
| DATA(ld_parts1by1) | = ' '. | |||
| "SELECT single SHOWLG FROM RSTSTYPE INTO @DATA(ld_showlg). | ||||
| DATA(ld_showlg) | = ' '. | |||
| "SELECT single SHOWLG FROM RSTSTYPE INTO @DATA(ld_hflag). | ||||
| DATA(ld_hflag) | = ' '. | |||
Search for further information about these or an SAP related objects