SAP RSAR_GET_INPUT Function Module for Display of a general popup for entry of various values
RSAR_GET_INPUT is a standard rsar get input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display of a general popup for entry of various values 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 get input FM, simply by entering the name RSAR_GET_INPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAD
Program Name: SAPLRSAD
Main Program: SAPLRSAD
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAR_GET_INPUT 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_GET_INPUT'"Display of a general popup for entry of various values.
EXPORTING
I_TYPE = "Type of the requested information
* I_METHOD = "
* I_FILE_DATASOURCE = "DataSource
IMPORTING
E_TYP = "
CHANGING
C_VALUE1 = "Value 1 (depending on type)
* C_VALUE2 = "Value 2 (depending on type)
* C_VALUE3 = "Value of 3 (depending on type)
* C_VALUE4 = "Value of 4 (depending on type)
* C_VALUE5 = "Value 5 (depending on type)
* C_VALUE6 = "Value 6 (depending on type)
* C_VALUE7 = "Value 7 (depending on type)
EXCEPTIONS
CANCELLED = 1 INVALID_TYPE = 2
IMPORTING Parameters details for RSAR_GET_INPUT
I_TYPE - Type of the requested information
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_METHOD -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FILE_DATASOURCE - DataSource
Data type: ROOSOURCEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSAR_GET_INPUT
E_TYP -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RSAR_GET_INPUT
C_VALUE1 - Value 1 (depending on type)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
C_VALUE2 - Value 2 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
C_VALUE3 - Value of 3 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
C_VALUE4 - Value of 4 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
C_VALUE5 - Value 5 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
C_VALUE6 - Value 6 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
C_VALUE7 - Value 7 (depending on type)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED - Cancellation by user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TYPE - Invalid Type Specification
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAR_GET_INPUT 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_e_typ | TYPE C, " | |||
| lv_i_type | TYPE C, " | |||
| lv_c_value1 | TYPE C, " | |||
| lv_cancelled | TYPE C, " | |||
| lv_c_value2 | TYPE C, " | |||
| lv_i_method | TYPE C, " | |||
| lv_invalid_type | TYPE C, " | |||
| lv_c_value3 | TYPE C, " | |||
| lv_i_file_datasource | TYPE ROOSOURCER, " | |||
| lv_c_value4 | TYPE ROOSOURCER, " | |||
| lv_c_value5 | TYPE ROOSOURCER, " | |||
| lv_c_value6 | TYPE ROOSOURCER, " | |||
| lv_c_value7 | TYPE ROOSOURCER. " |
|   CALL FUNCTION 'RSAR_GET_INPUT' "Display of a general popup for entry of various values |
| EXPORTING | ||
| I_TYPE | = lv_i_type | |
| I_METHOD | = lv_i_method | |
| I_FILE_DATASOURCE | = lv_i_file_datasource | |
| IMPORTING | ||
| E_TYP | = lv_e_typ | |
| CHANGING | ||
| C_VALUE1 | = lv_c_value1 | |
| C_VALUE2 | = lv_c_value2 | |
| C_VALUE3 | = lv_c_value3 | |
| C_VALUE4 | = lv_c_value4 | |
| C_VALUE5 | = lv_c_value5 | |
| C_VALUE6 | = lv_c_value6 | |
| C_VALUE7 | = lv_c_value7 | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| INVALID_TYPE = 2 | ||
| . " RSAR_GET_INPUT | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_GET_INPUT
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.Search for further information about these or an SAP related objects