SAP ARE_MONITOR_COMMAND_DISPATCH Function Module for









ARE_MONITOR_COMMAND_DISPATCH is a standard are monitor command dispatch 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 are monitor command dispatch FM, simply by entering the name ARE_MONITOR_COMMAND_DISPATCH into the relevant SAP transaction such as SE37 or SE38.

Function Group: BCA_ARCHIVNG_SERVICEMODULE
Program Name: SAPLBCA_ARCHIVNG_SERVICEMODULE
Main Program: SAPLBCA_ARCHIVNG_SERVICEMODULE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARE_MONITOR_COMMAND_DISPATCH 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 'ARE_MONITOR_COMMAND_DISPATCH'"
EXPORTING
P_OBJECT = "
P_COMMAND = "
.



IMPORTING Parameters details for ARE_MONITOR_COMMAND_DISPATCH

P_OBJECT -

Data type: TARCHENGINE01-OBJECT
Optional: No
Call by Reference: Yes

P_COMMAND -

Data type: SY-UCOMM
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ARE_MONITOR_COMMAND_DISPATCH 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_p_object  TYPE TARCHENGINE01-OBJECT, "   
lv_p_command  TYPE SY-UCOMM. "   

  CALL FUNCTION 'ARE_MONITOR_COMMAND_DISPATCH'  "
    EXPORTING
         P_OBJECT = lv_p_object
         P_COMMAND = lv_p_command
. " ARE_MONITOR_COMMAND_DISPATCH




ABAP code using 7.40 inline data declarations to call FM ARE_MONITOR_COMMAND_DISPATCH

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.

"SELECT single OBJECT FROM TARCHENGINE01 INTO @DATA(ld_p_object).
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_p_command).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!