The generic interface monitoring setup in SAP Focused Run is explained in this blog. This blog will zoom into monitoring of qRFC connections, which are frequently used in communication from ECC to EWM and SCM systems.
OSS notes for bug fixing
Please make sure bug fix OSS note 3014667 – Wrong parameter for QRFC alerts is applied before starting with qRFC monitoring.
Other OSS notes:
Data collection and alerting setup
In the configuration for interface monitoring in the Technical System settings, goto the monitoring part and activate the data collection for qRFC Errors:
In the monitoring settings, you can filter on specific queues, direction and RFC name, or leave everything blank to report on everything:
In the alerting part check you can choose between age of qRFC entries and number of entries:
And set the filters for which ones, and the metric threshold for CRITICAL errors:
The filter for monitoring and alerting can be different. It could be you want to monitor all errors, but only activate specific important ones.
Save your monitoring data collection and alerting settings.
Queued RFC’s are normally back and forth between 2 systems. If this is the case you have to make the settings for both systems.
In the graphical modelling add the filter between two systems for the qRFC monitoring:
Also here: first scroll down to see the OK button. Press first OK before pressing Save, or you might loose the data and have to re-enter it. This it bit annoying in the UI.
Queued RFC’s are normally back and forth between 2 systems. If this is the case you have to make the settings for both systems. You model first one direction and then model the direction back:
The end result in operations looks as follows:
You can see here qRFC is modelled back and forth between 2 systems. The blue line indicates messages in process. The red line is clicked on. Here you can see both messages in process and errors. Click on the red error number gives the details: