SAP RZL_STRG_READ_I Function Module for Read storage entry with type '10 integer'
RZL_STRG_READ_I is a standard rzl strg read i 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 storage entry with type '10 integer' 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 rzl strg read i FM, simply by entering the name RZL_STRG_READ_I into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAL2
Program Name: SAPLSAL2
Main Program: SAPLSAL2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RZL_STRG_READ_I 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 'RZL_STRG_READ_I'"Read storage entry with type '10 integer'.
EXPORTING
NAME = "Name of the storage entry
* SRVNAME = ' ' "Name of the application server, ' ' = own application server
IMPORTING
VALUE = "Value of the 1st storage entry
VALUE9 = "Value of the 8th storage entry
VALUE1 = "Value of the 2nd storage entry
VALUE2 = "Value of the 3rd storage entry
VALUE3 = "Value of the 4th storage entry
VALUE4 = "Value of the 3rd storage entry
VALUE5 = "Value of the 4th storage entry
VALUE6 = "Value of the 5th storage entry
VALUE7 = "Value of the 6th storage entry
VALUE8 = "Value of the 7th storage entry
EXCEPTIONS
ARGUMENT_ERROR = 1 NOT_FOUND = 2 SEND_ERROR = 3
IMPORTING Parameters details for RZL_STRG_READ_I
NAME - Name of the storage entry
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SRVNAME - Name of the application server, SPACE = own application server
Data type: SPFID-APSERVERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RZL_STRG_READ_I
VALUE - Value of the 1st storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE9 - Value of the 8th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE1 - Value of the 2nd storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE2 - Value of the 3rd storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE3 - Value of the 4th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE4 - Value of the 3rd storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE5 - Value of the 4th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE6 - Value of the 5th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE7 - Value of the 6th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
VALUE8 - Value of the 7th storage entry
Data type: SALSTINTG-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ARGUMENT_ERROR - Parameter error, for example, NAME too long or SPACE
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - Storage entry does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SEND_ERROR - Error in communication with the application server
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RZL_STRG_READ_I 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_name | TYPE STRING, " | |||
| lv_value | TYPE SALSTINTG-VALUE, " | |||
| lv_argument_error | TYPE SALSTINTG, " | |||
| lv_value9 | TYPE SALSTINTG-VALUE, " | |||
| lv_value1 | TYPE SALSTINTG-VALUE, " | |||
| lv_srvname | TYPE SPFID-APSERVER, " SPACE | |||
| lv_not_found | TYPE SPFID, " | |||
| lv_value2 | TYPE SALSTINTG-VALUE, " | |||
| lv_send_error | TYPE SALSTINTG, " | |||
| lv_value3 | TYPE SALSTINTG-VALUE, " | |||
| lv_value4 | TYPE SALSTINTG-VALUE, " | |||
| lv_value5 | TYPE SALSTINTG-VALUE, " | |||
| lv_value6 | TYPE SALSTINTG-VALUE, " | |||
| lv_value7 | TYPE SALSTINTG-VALUE, " | |||
| lv_value8 | TYPE SALSTINTG-VALUE. " |
|   CALL FUNCTION 'RZL_STRG_READ_I' "Read storage entry with type '10 integer' |
| EXPORTING | ||
| NAME | = lv_name | |
| SRVNAME | = lv_srvname | |
| IMPORTING | ||
| VALUE | = lv_value | |
| VALUE9 | = lv_value9 | |
| VALUE1 | = lv_value1 | |
| VALUE2 | = lv_value2 | |
| VALUE3 | = lv_value3 | |
| VALUE4 | = lv_value4 | |
| VALUE5 | = lv_value5 | |
| VALUE6 | = lv_value6 | |
| VALUE7 | = lv_value7 | |
| VALUE8 | = lv_value8 | |
| EXCEPTIONS | ||
| ARGUMENT_ERROR = 1 | ||
| NOT_FOUND = 2 | ||
| SEND_ERROR = 3 | ||
| . " RZL_STRG_READ_I | ||
ABAP code using 7.40 inline data declarations to call FM RZL_STRG_READ_I
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 VALUE FROM SALSTINTG INTO @DATA(ld_value). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value9). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value1). | ||||
| "SELECT single APSERVER FROM SPFID INTO @DATA(ld_srvname). | ||||
| DATA(ld_srvname) | = ' '. | |||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value2). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value3). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value4). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value5). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value6). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value7). | ||||
| "SELECT single VALUE FROM SALSTINTG INTO @DATA(ld_value8). | ||||
Search for further information about these or an SAP related objects