ABAP runtime errors usually occur if an ABAP program terminates unexpected or unplanned. ABAP runtime errors can indicate different problems, from a ABAP kernel error, a programming error, installation or administration errors to a resource bottleneck. Hence it is import to monitor for runtime errors and address them in a timely manner.

SAP Focused Run can collect runtime errors and provide you with collection context to analyze the root cause. 

Available Monitoring Categories

The available monitoring categories are:

• ABAP Runtime: ABAP short dumps as found in ST22

Available Filter Options

ABAP Runtime

For ABAP Runtime errors, you can collect all ABAP dumps in the managed system. You can also use the following filter parameters, to restrict the data collection: 

• Runtime Error~Exception: Runtime Error (ST22) ~ Exception (ST22)
• Program: Terminated program (ST22)
• User: User (ST22)
• Host: Application Server (ST22)
• Destination: Call destination from Collection Context or RFC Caller Information
• Function: Function module from Collection Context or RFC Caller Information

Available Metrics

For ABAP Runtime errors the following metrics are collected:

ABAP Runtime

• ABAP Runtime exceptions: Indicates that ABAP runtime errors were collected during the last collection
  • Additional filter fields:
    • Process type: Batch, Dialog, HTTP, RFC or Update
    • Source IP Address: IP address of the source server if the runtime error was called by a remote caller
    • Source Server: server name of the source server if the runtime error was called by a remote caller
• Number of ABAP Runtime Errors over period: Number of ABAP Runtime Errors during the alert calculation period
  • Additional filter fields:
    • Process type: Batch, Dialog, HTTP, RFC or Update
    • Source IP Address: IP address of the source server if the runtime error was called by a remote caller
    • Source Server: server name of the source server if the runtime error was called by a remote caller