SAP CCMON_RULES_GET Function Module for









CCMON_RULES_GET is a standard ccmon rules get 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 ccmon rules get FM, simply by entering the name CCMON_RULES_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: CCMONITOR_RULES_ADMIN
Program Name: SAPLCCMONITOR_RULES_ADMIN
Main Program: SAPLCCMONITOR_RULES_ADMIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CCMON_RULES_GET 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 'CCMON_RULES_GET'"
EXPORTING
I_UNAME = "
I_EXC_TYPE = "

TABLES
ET_RULES = "

EXCEPTIONS
RELEASE_NOT_SUPPORTED = 1 FATAL_ERROR = 2
.



IMPORTING Parameters details for CCMON_RULES_GET

I_UNAME -

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

I_EXC_TYPE -

Data type: CCMON_ALERT_RULE-EXC_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CCMON_RULES_GET

ET_RULES -

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

EXCEPTIONS details

RELEASE_NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

FATAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CCMON_RULES_GET 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_uname  TYPE SYUNAME, "   
lt_et_rules  TYPE STANDARD TABLE OF CCMON_ALERT_RULE, "   
lv_release_not_supported  TYPE CCMON_ALERT_RULE, "   
lv_i_exc_type  TYPE CCMON_ALERT_RULE-EXC_TYPE, "   
lv_fatal_error  TYPE CCMON_ALERT_RULE. "   

  CALL FUNCTION 'CCMON_RULES_GET'  "
    EXPORTING
         I_UNAME = lv_i_uname
         I_EXC_TYPE = lv_i_exc_type
    TABLES
         ET_RULES = lt_et_rules
    EXCEPTIONS
        RELEASE_NOT_SUPPORTED = 1
        FATAL_ERROR = 2
. " CCMON_RULES_GET




ABAP code using 7.40 inline data declarations to call FM CCMON_RULES_GET

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 EXC_TYPE FROM CCMON_ALERT_RULE INTO @DATA(ld_i_exc_type).
 
 


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!