SAP CCMSBI_MONI_REPORT_MTE_PROBLEM Function Module for CCMS / BW: Indicates an MTE-specific problem

Search SAP Function Modules

CCMSBI_MONI_REPORT_MTE_PROBLEM is a standard ccmsbi moni report mte problem SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CCMS / BW: Indicates an MTE-specific problem 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 ccmsbi moni report mte problem FM, simply by entering the name CCMSBI_MONI_REPORT_MTE_PROBLEM into the relevant SAP transaction such as SE37 or SE38.

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

Function CCMSBI_MONI_REPORT_MTE_PROBLEM 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 'CCMSBI_MONI_REPORT_MTE_PROBLEM'"CCMS / BW: Indicates an MTE-specific problem
  EXPORTING
   MONI_OBJECT =  "Alert: Short Name of Monitoring Type
   PATH =  "Path of a Monitoring Tree Element in the Monitoring Tree
   MONI_ATTRIBUTE =  "Alert: Short Name of Monitoring Type
*  PROBLEM_MSGID = 'CCMSBI_BCT_MESSAGES' "Messages, Message Class
   PROBLEM_MSGNO =  "Messages, Message Number
   LANDSCAPE =  "CCMS/BW: Landscape Name
   SYSID =  "R/3 System, name of R/3 System
   CONTEXT =  "Alert: Name of Monitoring Context
   OBJECTNAME =  "Alert: short name of MTE
   ATTRNAME =  "Alert: short name of MTE

EXCEPTIONS
   PROBLEM_MSG_ID_MISSING = 1    PROBLEM_MSG_NR_MISSING = 2    INVALID_OBJECT_ATTRIBUTE = 3    REPORTING_HAS_FAILED = 4 

.

IMPORTING Parameters details for CCMSBI_MONI_REPORT_MTE_PROBLEM

MONI_OBJECT - Alert: Short Name of Monitoring Type

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

PATH - Path of a Monitoring Tree Element in the Monitoring Tree

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

MONI_ATTRIBUTE - Alert: Short Name of Monitoring Type

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

PROBLEM_MSGID - Messages, Message Class

Data type: SYMSGID
Default: 'CCMSBI_BCT_MESSAGES'
Optional: Yes
Call by Reference: Yes

PROBLEM_MSGNO - Messages, Message Number

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

LANDSCAPE - CCMS/BW: Landscape Name

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

SYSID - R/3 System, name of R/3 System

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

CONTEXT - Alert: Name of Monitoring Context

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

OBJECTNAME - Alert: short name of MTE

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

ATTRNAME - Alert: short name of MTE

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

EXCEPTIONS details

PROBLEM_MSG_ID_MISSING - Message-ID. for the description of problem is missing

Data type:
Optional: No
Call by Reference: Yes

PROBLEM_MSG_NR_MISSING - Message-Nr for the description of problem is missing

Data type:
Optional: No
Call by Reference: Yes

INVALID_OBJECT_ATTRIBUTE - Monitoring Object / Attribute does not exist

Data type:
Optional: No
Call by Reference: Yes

REPORTING_HAS_FAILED - Nofitying the problem has failed

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CCMSBI_MONI_REPORT_MTE_PROBLEM 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.

ABAP code using 7.40 inline data declarations to call FM CCMSBI_MONI_REPORT_MTE_PROBLEM

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