For smooth running operation in CRM proactive middleware monitoring is very important. CRM Middleware Monitoring Cockpit provides centralized monitoring of following key items:
SMQ1/SMQ2 -Queue – Errors
Business Document -BDOC – Errors or unprocessed
Remote function call – Connectivity – RFC destination status
Generation – Error within object generation
Parameters – Inconsistent control table settings
Table indices – Missing indices
It uses traffic light scenario to quickly alert about errors encountered in the middleware data transfer process. Also provide status information on generation and runtime environment as well as further status information and system settings are displayed in a tree structure. You can expand the nodes of this tree.
The displayed information is updated after a certain period of time. But you can also update the information of an individual node manually.
CRM Middleware Monitoring Cockpit can be access by using txn SMWP. System will prompt “Monitoring Cockpit Background Collector is not running!” If you are running Txn SMWP first time.
Collector job will be scheduled in background.
Do you need to do some prerequisite in ECC table to bring the master data from ECC to CRM ? like we do in SRM
Muthu
Creation of logical system
Assigning logical system to client
Setting of RFC connection
setting parameters in CRMCONSUM and CRMRFCPAR tables
Muthu
1. CRMPAROLTP
2. CRMCONSUM
3. CRMRFCPAR