SAP RFC_F_SCMA_RFC_MONITOR Function Module for Calls the monitor for RFC-Calls
RFC_F_SCMA_RFC_MONITOR is a standard rfc f scma rfc monitor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls the monitor for RFC-Calls 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 rfc f scma rfc monitor FM, simply by entering the name RFC_F_SCMA_RFC_MONITOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCMA_RFC
Program Name: SAPLSCMA_RFC
Main Program: SAPLPFM2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RFC_F_SCMA_RFC_MONITOR 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 'RFC_F_SCMA_RFC_MONITOR'"Calls the monitor for RFC-Calls.
EXPORTING
* I_SCHED_ID = "Scheduler ID
* I_WF_ID = "Work item ID
EXCEPTIONS
WRONG_ID = 1
IMPORTING Parameters details for RFC_F_SCMA_RFC_MONITOR
I_SCHED_ID - Scheduler ID
Data type: TZNTSTMPLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WF_ID - Work item ID
Data type: SWD_API_WIOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_ID -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RFC_F_SCMA_RFC_MONITOR 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_wrong_id | TYPE STRING, " | |||
| lv_i_sched_id | TYPE TZNTSTMPL, " | |||
| lv_i_wf_id | TYPE SWD_API_WI. " |
|   CALL FUNCTION 'RFC_F_SCMA_RFC_MONITOR' "Calls the monitor for RFC-Calls |
| EXPORTING | ||
| I_SCHED_ID | = lv_i_sched_id | |
| I_WF_ID | = lv_i_wf_id | |
| EXCEPTIONS | ||
| WRONG_ID = 1 | ||
| . " RFC_F_SCMA_RFC_MONITOR | ||
ABAP code using 7.40 inline data declarations to call FM RFC_F_SCMA_RFC_MONITOR
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