SAP RIS_CALL_SCREEN_RESULT Function Module for
RIS_CALL_SCREEN_RESULT is a standard ris call screen result SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ris call screen result FM, simply by entering the name RIS_CALL_SCREEN_RESULT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RIS_UI_MODEL_DYNPRO
Program Name: SAPLRIS_UI_MODEL_DYNPRO
Main Program: SAPLRIS_UI_MODEL_DYNPRO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RIS_CALL_SCREEN_RESULT 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 'RIS_CALL_SCREEN_RESULT'".
EXPORTING
* IO_RESULT = "
* IT_RESULTS = "
EXCEPTIONS
CX_RIS_EXCEPTION = 1
IMPORTING Parameters details for RIS_CALL_SCREEN_RESULT
IO_RESULT -
Data type: CL_RIS_RESULTOptional: Yes
Call by Reference: Yes
IT_RESULTS -
Data type: RIS_T_RESULTSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
CX_RIS_EXCEPTION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RIS_CALL_SCREEN_RESULT 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_io_result | TYPE CL_RIS_RESULT, " | |||
| lv_cx_ris_exception | TYPE CL_RIS_RESULT, " | |||
| lv_it_results | TYPE RIS_T_RESULTS. " |
|   CALL FUNCTION 'RIS_CALL_SCREEN_RESULT' " |
| EXPORTING | ||
| IO_RESULT | = lv_io_result | |
| IT_RESULTS | = lv_it_results | |
| EXCEPTIONS | ||
| CX_RIS_EXCEPTION = 1 | ||
| . " RIS_CALL_SCREEN_RESULT | ||
ABAP code using 7.40 inline data declarations to call FM RIS_CALL_SCREEN_RESULT
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