ABAP Systems

Aborted Jobs, Application Log, Runtime Errors, System Log, Update Errors

SAP NetWeaver ABAP systems do have several areas where exceptions can occur. You can integrate specific monitors in different exception areas (in brackets you can find the corresponding manual monitoring transaction):

  • Aborted Jobs (SM37)
  • Application Log (SLG1)
  • Runtime Errors (ST22)
  • System Log (SM21)
  • Update Errors (SM13)

Technical Prerequisites

    The following technical prerequisites have to be met in SAP Solution Manager release in order to monitor this scenario:

  • Aborted Jobs (since 7.1 SP12)
  • Application Log (since 7.1 SP10)
  • Runtime Errors (since 7.1 SP10)
  • System Log (since 7.1 SP10)
  • Update Errors (since 7.1 SP10)

Available Monitoring Content

In the following table the available filter criteria for the different use cases are listed:

Use Case Available Fields for Filtering Description
Aborted Jobs JOBNAME Job name
  USER User who released scheduled batch job
Application Log EXTNUMBER External ID
  MSGID Message Class
  MSGNO Message Number
  MSGTXT Message Text
  OBJECT Object
  PROGRAM Program triggering log
  SUBOBJECT Sub-object
  TCODE Transaction code triggering log
  USER User triggering log
Runtime Error DEST Destination of RFC Call
  ERRID Runtime Error
  FUNC Function Module of RFC Call
  HOST Host
  PROG Program Name
  USER User
System Log MESSAGE_ID <Msg area>-<Msg ID>
  PROG Program Name
  USER User
Update Errors CLIENT Client
  SUBCETEGORY <Program/Transaction>~<Update VB Mode>
  USER User name in update request

Configuration

For the configuration of the Exception Management functionality, go to transaction SOLMAN_SETUP → Application Operations → Exception Management:

  1. In the 'Define Scope' step, select the 'Technical Systems' tab and your SAP ABAP system. If you did not configure the system before, make sure to select 'All Systems' in the view drop-down. Click 'Configure' or click 'Next' two times. You will enter the 'Exception Configuration' step.
  2. In the 'Exception Configuration' step, click 'Add / Configure Log Store' → Standard then select the respective Log Store.
  3. Select the field(s) you want to filter. For the available fields, check the above table of available monitoring content.
  4. Maintain the filter values for the fields in the 'Filter Definition' panel under the log stores table. You can also add, remove or change filter fields and values later on in this area. You can use different operators for your filter value. You can add more than one filter field combination per log store. To add an additional filter field combination, click the 'Add Filter' button in the 'Configured Log Stores' panel.
  5. Once you are done with the Log Store setup, click 'Next' to go to next step 'Enable Alerting', where you can check the status of the Alerting Infrastructure configuration.
  6. Once you are sure that the Alerting Infrastructure is enabled, go to the next step 'Metric Configuration'.
  7. In the 'Metric Configuration', you are informed about the existing metrics and the new ones will be imported in the configuration. In this step you are able to enable/disable metrics by using the Enabled check box in each metric line. Once you've made your decisions, you can go to the next step 'Alert Configuration'.
  8. In the step 'Alert Configuration" you are now able to enable the alerts and change their severity. You can create or assign existing variants for Automatic Incident Creation, Automatic Notification, Forward to Third-Party Component, and Trigger Auto-Reaction. Once you press 'Save' the alerts will be activated.