Skip to Content

  If your Production system contains lot of servers then it becomes very tedious to manually monitor all the systems, CCMS alerts can prove to be handy in such scenarios. Although these alerts don’t actually give the crystal clear picture about the issue but might give some pointers to the problem in such kind of scenarios we have to properly setup the CCMS alerts. 

In this blog I have tried to enlist different aspects of these alerts and in the latter part, I have briefly given ways to check whether alerts are properly configured or simple validation

CCMS(Computing Centre Management System) alerts can be configured through RZ20 under BI Monitor(it is the integral part of CCMS) and in case one doesn’t have authorization for the same a possible workaround can be via Monitors in t-code RSMON, there BI CCMS option can be selected.CCMS collects logs from agent using Methods which in turns calls function module. For example a common Function Module RSPC_CCMS_MA_UPDATE which is called by method RSPC_CCMS_AGENT when we check the same in RZ21 under methods option or in Method allocation in RSMON we can also define the retention period for holding logs with the help of parameter option and in control tab one can define nature of job whether background or foreground.

If one tries to explore further BI monitors we can find out it monitors various other transactions like:

1) RSPC it gives the summarized picture of all the process chain in the system and corresponding chain is highlighted with color code that depicts the current state of chain at that moment

2) DB02: Information is related to table spaces for tables like PSA, temp, undo and also the most/least allocates segments in the option Space Management. In SAP consistency, under object missing option it checks out for missing primary, secondary indexes and similarly inconsistent objects can be checked out as well

3)RSRV: We get  consolidated list of the consistency for various BI objects like PSA table, DSO, Infocube, DTP, SID values, Flags, Bex, Infoobjects, etc.

4) RFC: Through CCMS one can easily analyze the communication failures at the system level which can be attributed due to either scarcity of system resources or errors. You can see for both transactional and Queued RFCs.

5)Background processes: They can be handy while monitoring the background processes of multiple server system (SM37/SM51) and other background services at one place ,you can easily view which job got aborted/completed(that is signified by color codes again) and at which server

6) ALE IDocs: It gives detailed information on the IDOC movements happened, that is it has logs of each and every step which is involved in IDoc movement 

So with these options in hand when you are working in support projects, from the system level you can easily monitor things without having fear of number of application severs or remembering the t-codes

In case of any error/shout alerts can be configured accordingly. For example when generating alert for say process chain is done by method, in case of chains it is RSPC_CCMS_ANALYZE after starting the analysis and the alert to be configured for a particular email id can be done with help of SCOT t-code while sending of alert to a shared distribution list can be done by SO04 or from business workplace in Main menu

We can easily verify the alert for a particular error entries in more simpler way with ALRTCATDEF there you can configure the email ids like before but do remember while using this option just check “Send alerts if errors occur” in Alerting which is Attribute option of process chain. Also mail notification can be also done through program RSPC_MONITOR, it all depends how you want things to be done

SAP note 1528906, 28538 can be helpful.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply