SAP RSBM_SHOW_REQUEST Function Module for Monitor DTP Request
RSBM_SHOW_REQUEST is a standard rsbm show request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Monitor DTP Request 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 rsbm show request FM, simply by entering the name RSBM_SHOW_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSBM_REQUEST_GUI
Program Name: SAPLRSBM_REQUEST_GUI
Main Program: SAPLRSBM_REQUEST_GUI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSBM_SHOW_REQUEST 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 'RSBM_SHOW_REQUEST'"Monitor DTP Request.
EXPORTING
I_REQUID = "Data Transfer Process Request
* I_R_NAVIGATOR = "Access to AWB Navigator
EXCEPTIONS
CX_RS_NOT_FOUND = 1
IMPORTING Parameters details for RSBM_SHOW_REQUEST
I_REQUID - Data Transfer Process Request
Data type: RSBKREQUIDOptional: No
Call by Reference: Yes
I_R_NAVIGATOR - Access to AWB Navigator
Data type: IF_RSAWBN_NAVIGATOROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
CX_RS_NOT_FOUND - Object Not Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSBM_SHOW_REQUEST 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_i_requid | TYPE RSBKREQUID, " | |||
| lv_cx_rs_not_found | TYPE RSBKREQUID, " | |||
| lv_i_r_navigator | TYPE IF_RSAWBN_NAVIGATOR. " |
|   CALL FUNCTION 'RSBM_SHOW_REQUEST' "Monitor DTP Request |
| EXPORTING | ||
| I_REQUID | = lv_i_requid | |
| I_R_NAVIGATOR | = lv_i_r_navigator | |
| EXCEPTIONS | ||
| CX_RS_NOT_FOUND = 1 | ||
| . " RSBM_SHOW_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM RSBM_SHOW_REQUEST
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