On this page:

Error filter allows you to exclude specific errors that are automatically added to business transactions by the ABAP Agent. To access the Error filter UI, navigate to t-code /DVD/APPD_CUST → Instrumentation and select Error filter value tab.

This dedicated error filtering is needed because native agent (C++ SDK) used by ABAP Agent does not support error filtering via controller UI. The native agent also does not expose any error meta-data like exception types or message classes on the controller. To expose these meta-data, please activate debug mode with BT error flag checked. See Debug Mode.

Error Filter Types

The following error filter types can be created:

Error TypePrimary valueSecondary valueNotes
ExceptionException classException text IDWhen an exception is matched against this error filter type, the whole exception stack is discarded.

Message ID

Message class nameMessage number

Checked against SE91 message classes.

This filter type is also applied to exceptions that implement IF_MESSAGE interface and text IDs are linked to message classes.

Free textFree textN/AIntended for cases where exception or message ID cannot be used or is not available. Wildcard character '*' is supported by this type.

Error Filtering for Specific Business Transactions

All error filter types contain field 'BT Name Filter' for entering list of relevant business transaction names. When this field is empty, the filter is applied to every business transaction. When set, the error filter is only applied to the specified business transactions. Wildcard character '*' is supported.

Example for Setting Up Error Filtering

You can use this guide as a reference when errors associated with your business transactions need to be ignored:

  1. You have identified an error and have decided that it is not relevant as shown in the following example:

    Please note that 'C++ Error' text appears for all errors that originate from ABAP Agent, i.e. from the instrumented SAP system. This comes from the native agent used by ABAP Agent - C++ SDK. This does not mean that the error occurred in some C++ application. If the tier is associated with an SAP system, this error always originates from the SAP system.

  2. To expose meta-data for this error, navigate to t-code /DVD/APPD_STATUS and activate debug mode by clicking Error metadata flag set checkbox.
  3. Generate some traffic and check the business transaction error snapshot again. You will see technical meta-data added to the error string. The format in this example refers to an exception of type /IWFND/CX_ACCESS_CHECK at level 3 of an exception stack.

    Snapshot UI displays only the last error received by the business transaction. To see all please refer to data collector 'SAP Error' that is automatically added when ABAP Agent adds errors to a business transaction.

  4. Some business transactions can have more than one error added to it. Always check the data collector 'SAP Error' as it contains the full list of errors delimited by '|' character. To exclude this error completely, you need to create an error filter for all exceptions at the top of the exception stack (with number 1 next to the exception type) and message IDs that appear on the list. In this example, /IWFND/CX_ACCESS_CHECK/IWCOR/CX_DS_FORBIDDEN exception needs to be filtered. Message ID /IWFND/CM_CONSUMER with number 122 also needs to be filtered.

    Line breaks and other formatting is not supported for data collector values. This limitation can be addressed by copying the whole value of 'SAP Error' into a text editor and replacing '|' with a line break character. Individual errors will be listed on separate rows.

  5. One exception type can contain multiple text IDs. To filter out only a specific text and not affect the others, you can check the exception object using t-code SE24 and check for the right one. In this example, text ID /IWFND/NO_SERVICE_ACCESS is used by exception type /IWFND/CX_ACCESS_CHECK.

  6. Once the necessary filters are defined, the business transaction is not flagged as an error business transaction anymore. BT name filter is used to limit the effect of these error filter records to specific business transactions.

It is possible to skip several steps of this process and define free text filters for every message found in 'SAP Error' data collector, but there are several drawbacks to this approach:

  • One free text filter needs to be defined for every level of each exception stack
  • Free text comparison is more performance-intensive than comparing exception types or message IDs