SAP CCMONITOR_EVAL_MON Function Module for









CCMONITOR_EVAL_MON is a standard ccmonitor eval mon 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 ccmonitor eval mon FM, simply by entering the name CCMONITOR_EVAL_MON into the relevant SAP transaction such as SE37 or SE38.

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



Function CCMONITOR_EVAL_MON 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 'CCMONITOR_EVAL_MON'"
TABLES
CT_RULES = "
ET_ALERTS = "

EXCEPTIONS
RELEASE_NOT_SUPPORTED = 1 FUNCTION_NOT_FOUND = 2
.



TABLES Parameters details for CCMONITOR_EVAL_MON

CT_RULES -

Data type: CCMON_ALERT_RULE
Optional: No
Call by Reference: Yes

ET_ALERTS -

Data type: CCMON_ALERT_STORAGE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

RELEASE_NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CCMONITOR_EVAL_MON 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:
lt_ct_rules  TYPE STANDARD TABLE OF CCMON_ALERT_RULE, "   
lv_release_not_supported  TYPE CCMON_ALERT_RULE, "   
lt_et_alerts  TYPE STANDARD TABLE OF CCMON_ALERT_STORAGE, "   
lv_function_not_found  TYPE CCMON_ALERT_STORAGE. "   

  CALL FUNCTION 'CCMONITOR_EVAL_MON'  "
    TABLES
         CT_RULES = lt_ct_rules
         ET_ALERTS = lt_et_alerts
    EXCEPTIONS
        RELEASE_NOT_SUPPORTED = 1
        FUNCTION_NOT_FOUND = 2
. " CCMONITOR_EVAL_MON




ABAP code using 7.40 inline data declarations to call FM CCMONITOR_EVAL_MON

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



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!