If we want to monitor process chains first transaction that comes to our mind would be RSPC or RSPCM. RSPC shows isolated chains where a person needs to click on each chain to get the data loading status, whereas RSPCM provides the up to date status of the all the process chains in the system but it is only limited to the monitoring of process chains. This blog sheds some light on the Computing Center Management System also called as CCMS which consists of alert monitor, together with the BW monitor, which contain SAP BI relevant monitoring trees and monitoring trees for process chains and consistency checks in the analysis and repair environment.
To get to the CCMS go to RSMON -> Monitors -> BI CCMS or transaction RZ20 -> SAP BI Monitors -> BI Monitor.
Small things to know:
SAP BI CCMS monitor is basically divided into three categories named as BI accelerator monitor, Key performance indicator and BI Monitor. In this blog we will talk about BI monitor.
SAP BI CCMS monitor is basically divided into three categories named as BI accelerator monitor, Key performance indicator and BI Monitor. In this blog we will talk about BI monitor.
To collect the logs, CCMS agent uses number of Methods. Each method calls Transaction/ Function Module/ Report or URL to collect the logs. Methods can be accessed from RZ21 -> methods -> Definition OR on CCMS BI monitor screen go to views -> Method Allocation. Later option will populate relevant methods against its corresponding nodes in the tree.
E.g.
Method: RSPC_CCMS_AGENT.
Function module used: RSPC_CCMS_MA_UPDATE
We can define number of days CCMS should hold logs for. It is decided by the parameter DAYS_TO_KEEP_LOGS which is set to 7 by default. This means that CCMS shows process chain runs from the last seven days. In addition we can also define whether method should be executed in the background or foreground under Control tab.
Transactions monitored in BI monitor:
I. RSPC: CCMS provides a consolidated log view of all the process chains in the system. It gives clear picture of whether process chain is in progress, successful or failed by indicating the chain in Yellow, Green and Red colors respectively. By default CCMS agent for process chain is scheduled to run after every 1 hour. It uses job SAP_CCMS_MONI_BATCH_DP to collect all the logs from the system. We can easily change the scheduling in transaction SM37
II. DB02: This transaction keeps the log of the system space management, Performance, Backup and Health of the system also.
a) Space Management: As shown below, it gives how much free space is available, how much PSA table, Temporary table, UNDO table space is available. These spaces need to be potentially analyzed before starting any data loads.
b) SAP Consistency: It gives list of all missing/inconsistent objects in the database like Primary index, secondary index, tables, views etc. This especially helps support team while monitoring the reports performance as missing secondary indexes strongly impacts performance of the query.
In addition to above it also provides the details about Health of the system, Performance of the system.
III. RSRV (Consistency checks in the analysis and repair environment): It is one of the most essential transaction to check the consistency of all the BI objects like Cube, DSO, Hierarchies, PSA tables, BEx objects, Documents, aggregates, DTP, BIA, Cache, Transaction data, Master data etc. CCMS provides the consolidated view of consistency of all of the above mentioned objects.
IV. Transactional RFC and Queued RFC: CCMS also proves to be beneficial to monitor SM58 (Transactional RFC), SMQ1 (Outbound queue), SMQ2 (Inbound queue).It provides details of the calls that failed due to the communication errors, execution errors or lacking server resources. Qout scheduler which can be used to change/analyze number open RFC connections between different systems can also be checked from CCMS.
V. SM37 & SM51 (Background Processing): CCMS is also useful to monitor the background jobs in the system. It provides all the details of which job got aborted on which server.
VI. ALE Idocs Monitoring (BDMO): As shown below CCMS also provides the facility to monitor status of Outbound and Inbound ALE Idocs of the system. It gives step by step update on the status of Idocs which means if Idoc is failed at Idoc interface or if Idoc is dispatched successfully it will be shown in the monitor in the corresponding Status Group.
From above it seems that SAP has found the best way for any BI consultant especially support team member to monitor the whole system without having to remember any of the system transactions or any extra efforts.
Viren Devi is Certified SAP BI consutant at Capgemini.
