From availability perspective, you want to detect as quickly as possible if you are suffering from locking errors of table TBTCO. TBTCO table is used for printing. If the locking error situation occurs the printing function will fail, and even worse, it can impact the complete SAP ABAP system.
You can create a custom monitoring metric to measure and act on this.
Creation of the custom metric for errors in table locking of TBTCO
Create a custom metric following the steps in this blog. The template to be adjusted is the technical instance SAP ABAP 7.10 and higher template.
Don’t forget to tick it on for monitoring otherwise it is not active.
In expert mode create a custom metric.
Create technical name Z_METRIC_ERR_LOCK_TBTCO:
In the data collection:
Data to enter: RFC on diagnostics agent (push). Select ABAP System Log Stats. Filter on message text *TBTCO*. This captures severe errors for TBTCO like the locking error.
Define the threshold for alerting:
And assign the metric to the ABAP Instance not available alert group: