SAP ISU_MDUS_CALL_RQ_MONI Function Module for Call Monitoring
ISU_MDUS_CALL_RQ_MONI is a standard isu mdus call rq moni SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call Monitoring 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 isu mdus call rq moni FM, simply by entering the name ISU_MDUS_CALL_RQ_MONI into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMDUS_RQ_MONI
Program Name: SAPLEMDUS_RQ_MONI
Main Program: SAPLEMDUS_RQ_MONI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_MDUS_CALL_RQ_MONI 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 'ISU_MDUS_CALL_RQ_MONI'"Call Monitoring.
EXPORTING
IM_REQUEST_TAB = "MDUS Request
* IM_SIUMLATION_MODE = "Edit mode
IMPORTING
EX_SIMU_REQUEST_TAB = "Table Type for Structure EMDUSRQ
IMPORTING Parameters details for ISU_MDUS_CALL_RQ_MONI
IM_REQUEST_TAB - MDUS Request
Data type: EMDUSRQ_TABOptional: No
Call by Reference: Yes
IM_SIUMLATION_MODE - Edit mode
Data type: E_MDUSRQSIMUMODEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_MDUS_CALL_RQ_MONI
EX_SIMU_REQUEST_TAB - Table Type for Structure EMDUSRQ
Data type: EMDUSRQ_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_MDUS_CALL_RQ_MONI 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_im_request_tab | TYPE EMDUSRQ_TAB, " | |||
| lv_ex_simu_request_tab | TYPE EMDUSRQ_TAB, " | |||
| lv_im_siumlation_mode | TYPE E_MDUSRQSIMUMODE. " |
|   CALL FUNCTION 'ISU_MDUS_CALL_RQ_MONI' "Call Monitoring |
| EXPORTING | ||
| IM_REQUEST_TAB | = lv_im_request_tab | |
| IM_SIUMLATION_MODE | = lv_im_siumlation_mode | |
| IMPORTING | ||
| EX_SIMU_REQUEST_TAB | = lv_ex_simu_request_tab | |
| . " ISU_MDUS_CALL_RQ_MONI | ||
ABAP code using 7.40 inline data declarations to call FM ISU_MDUS_CALL_RQ_MONI
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