Exceptions (remQ 6.0 and later)

Calendar Icon


April 20, 2021

Last Edited icon


June 2, 2021

Advanced Exceptions is a feature that allow to define more complex exceptions, including lists of values, ranges, both to include or exclude, wildcards, and use OR or AND logic to combine several conditions into one exception. Maintenance is easier than before, and with the advanced features, false positives can be reduced further.

The new Exceptions maintenance transaction is /n/REM/EXCEPTIONS and is also linked from the admin transaction.

The previous version of exceptions is still in use and both methods work in parallel. But the old version will be retired in a future remQ release and going forward, new exceptions should only be defined in the new transaction, and existing exceptions maintained in the admin transaction – Exceptions tab should be migrated to the new feature.

The following fields are available in the /n/REM/EXCEPTIONS transaction:

CHECK ID: Name of the check. You can use * for all checks. Other wildcards are not supported.
EXCEPTION ID: unique text that identifies the added exception.
PARAMETER NAME: Name of the parameter on which the exception will be added. It’s possible to use either PARAM1-PARAM15 and structured fields including Value-at-Risk.
Option: All the available options from the SAP standard. In order to use Pattern or Exclude Pattern, it is mandatory to use a wildcard ( ‘*’ ) in the text. When using range/outside range, both low and high values must be maintained.
LOWER LIMIT: can be either the lower part of the range, or a single value.
HIGHER LIMIT: Higher limit to be used only when ranges option is selected.
MULTIPLE: Here it is possible to add several single values, several ranges, or exclude several values/ranges in the same parameter.
AND ID: This field connects several conditions for the same check/CHECK ID with an AND condition, i.e. only if _all_ those conditions linked by the same AND ID are true, then the exception will be applied. Exceptions for the same CHECK ID with no link using an AND ID will work like an OR, i.e. if any of the conditions are true, an exception will be applied.
VALID FROM: Start date from which the exception is valid.
VALID TO: End date to which the exception is valid.
COMMENTS: Free text to add a short description of the exception.

There are some additional fields with information, not allowed for manual changes: created on/by, and last change on/by.

NOTE: the new exceptions are independent from your saved configuration of parameters. If you want to restrict certain exceptions, e.g. for a single company code, use the AND logic.