cancel
Showing results for 
Search instead for 
Did you mean: 

CCMS for Table monitoring not using Message Class

Former Member
0 Kudos

We are currently using a Table content monitor in CCMS to raise alerts for an ABAP monitoring program we have written. The program inserts records in a custom ABAP table and when a row is inserted with a certain value we raise an alert through CCMS.

The data collection method is using the "Red" function module SCSM_GEN_TAB_DS_R

The alerts are generating fine but the alert text is displaying <CCMS: no default text available>. We have configure a message class and number but it is not displaying this in alert. Does anyone know what could be the problem?

Here is the parameter settings for the data collection method

1. TARGET_TABLE ZTSPM_CH_STATUS

2. FIELDNAME CHANNELKEY

3. FIELDVALUE CCSTATUS

4. MAXROW 50

5. WHERECLAUSE1 CCSTATUS = 'FAIL'

6. WHERECLAUSE2

7. WHERECLAUSE3

8. TOP_FULL_NAME

9. RESCANFROMBEGIN REPORTTIMESTAMP

10. T100_MESS ZXI_CNB 023

The message class/number (ZXI_CNB 023) is

"Connectivity Heartbeat failed for &1, Status: &2"

I was expexting the values from the table for fieldname (CHANNELKEY) and Fieldvalue (CCSTATUS) to be replaced in the message string.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hey Mark!

I had a question about this topic. I had the problem, that method doesn't work. The following parameters have been set:

1. TARGET_TABLE           ZMON_ERROR

2. FIELDNAME              EF

3. FIELDVALUE             EV

4. MAXROW                 50

5. WHERECLAUSE1           EV='AU01'

6. WHERECLAUSE2

7. WHERECLAUSE3

8. TOP_FULL_NAME

9. RESCANFROMBEGIN       

10. T100_MESS            

Rescanfrombegin and Messageclass have not been set, because I read, that there are many problems.

In Technical Export Monitors under DataSupplier theres an alert:

Internal Error in method SCSM_GEN_TAB_DS_R, Error: SELECT, SY-SUBRC = 0.

I think the problem is the WHERECLAUSE, but it doesn't matter if I change everything. Do you know any solutions, maybe?

Former Member
0 Kudos

Like some many problems this was user error on our part (used incorrect message class name).