Skip to main content

# SAP System - Built-in Checks

Here you will find detailed information about Built-in checks for SAP System monitored objects.

Built-in checks are deployed automatically for a monitored object type. Once Avantra has detected a specific monitored object, each of the relevant built-in checks will be auto-deployed to the agent to begin check execution and status reporting. Built-in checks can be configured using Monitoring Parameters (e.g. to set threshold values) and can also be disabled if they are not relevant to your landscape.

note

Starting from Avantra 20.2.0, no enhancements have been made to the checks for SAP Releases lower than 7.30 SP5. It means that if you are running SAP Releases lower than 7.30 SP5, some of the checks below will not be supported and, therefore, will either not be displayed or be shown with an UNKNOWN status and a message highlighting that the check requires a higher SAP release

## ABAP_DD_DB​

Runs an ABAP data dictionary / database consistency check inside SAP and displays the results. If there are no inconsistencies the check is Ok, otherwise, a Warning will be reported. Certain indexes may be excluded from the check by using the monitoring parameter ABAP_DD_DB_Exclude.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | ABAP_DD_DB_Exclude

## BATCH_INPUT​

This check verifies erroneous, long-running, and outdated batch input sessions and consists of three sub-checks.

- The SAP System is queried for batch input sessions older than BatchInputMaxAge days. The check result will be Warning if records are found. To turn this sub-check off, you may set BatchInputMaxAge to 0. The result of this sub-check is indicated with a message like: `Number of batch input sessions older than 60 days: 85`.
- The SAP System is queried for running batch input sessions older than BatchInputMaxRunTime. The check result will be Warning if such records are found. You cannot turn this sub-check off. The result of this sub-check is indicated with a message, e.g.: `Number of batch input sessions in state processing older than 24 hours: 7`.
- The system is queried for erroneous batch input sessions of the previous day. If records are found, the check result will be Critical and a table with erroneous batch input sessions will be displayed. The result of this sub-check is indicated with a message, e.g.: `No erroneous batch input sessions starting from 2010-02-16 07:00:00 found` or

    Cli. Session name  St. User   Date/Time           Creation Program   TA.tot   TA.err
    ------------------------------------------------------------------------------------
    001  MY_SESSION    E   BATCH  2010-02-17 06:00:44 Z_MY_PROG          28       28

For all three sub-checks, you may use BatchInputClientExclude to exclude clients, and BatchInputQIDExclude to exclude sessions by Queue-ID. By default client `000` and `066` are excluded.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | BatchInputMaxAge, BatchInputMaxRunTime, BatchInputQIDExclude, and BatchInputClientExclude

## BatchManStat​

This check verifies the status of BatchMan, a 3rd-party product of HONICO. (If installed in your ABAP SAP System.)

BatchManStat will first look if BatchMan is active. If so it will further check if the BatchMan job is active. Additionally, it will output the date and time of the last run of the BatchMan job. The check status is OK if both, BatchMan itself and its BatchMan job are active. Otherwise, the check status is Critical.

If you are not using BatchMan but the Avantra Agent has found it in your SAP System and the BatchManStat check is Critical you may want to disable the check completely.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | None

## BCS_OutboundErrors​

This check queries for erroneous outbound Business Communication Services records and retrieves erroneous outbound business communication services records as displayed by SAP transaction `SOST`. This check works exactly as the RealTime Monitoring check BCS_OutboundErrStat, except that the timespan is always to the previous Daily check record. Please see BCS_OutboundErrStat for a description.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | BcsOutboundClientMode, BcsOutboundClientList, BcsOutboundErrorsNumWarn, BcsOutboundErrorsNumCrit, and MaskUserPersonalDetails

## BCS_OutboundErrStat​

This check queries for erroneous outbound business communication services records (RealTime Monitoring) and retrieves erroneous outbound business communication services records as displayed by SAP transaction `SOST`. This check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, this check checks in all clients except `000` and `066`. You may change this behavior using BcsOutboundClientMode, which can be set to deny or allow. Denylisted or allowlisted clients are specified by BcsOutboundClientList.

If the number of erroneous records in last BcsOutboundErrStatTimeSpan minutes is above configurable thresholds BcsOutboundErrStatNumWarn or BcsOutboundErrStatNumCrit, the status of the check is set to the corresponding status. This check is accompanied by daily check BCS_OutboundErrors, which checks erroneous records back to the previous Daily Check schedule.

Each client is checked separately against the thresholds. The client column of the result table is either colored with no color, meaning there are erroneous records but the number is below Warning and Critical thresholds, yellow, meaning the number of erroneous records are equal to or above the Warning threshold, or red, i.e. above the Critical threshold. The worst result per client will give the overall status of the check.

note

The amount of records being selected is limited by a maximum number of 500 per client.

Due to technical reasons, the column Sender will be blank if the RFC user (see Avantra Agent) is not in the same client as the BCS record.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | BcsOutboundClientMode, BcsOutboundClientList, BcsOutboundErrStatNumWarn, BcsOutboundErrStatNumCrit, MaskUserPersonalDetails, and BcsOutboundErrStatTimeSpan

## BCS_OutboundWaitStat​

This check retrieves waiting outbound business communication services records as displayed by SAP transaction `SOST`. This check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. If the number of waiting records is above configurable thresholds BcsOutboundWaitNumWarn and the wait time of these records exceeds BcsOutboundWaitTimeWarn minutes, the status is set to Warning. If records are found that exceed BcsOutboundWaitNumCrit in number and BcsOutboundWaitTimeWarn in time, the status is set to Critical.

By default, this check checks in all clients except `000` and `066` and you may change this behavior using BcsOutboundClientMode, which can be set to deny (`Blacklist`) or allow (`Whitelist`). Denylisted or allowlisted clients are specified by the BcsOutboundClientList parameters.

Each client is checked separately against the thresholds. The client column of the result table is either colored in green, meaning there are waiting records but the wait time of each record is below BcsOutboundWaitTimeWarn. This can be normal behavior, for instance, if waiting records are sent by a scheduled job. If the client column has no color at all, this means that there are waiting records above BcsOutboundWaitTimeWarn or BcsOutboundWaitTimeCrit but the number of them is below thresholds BcsOutboundWaitNumWarn or BcsOutboundWaitNumCrit. Yellow and red color means that there are waiting records above the corresponding time and number thresholds.

Since different send methods may require different time thresholds, for instance, if outbound requests using FAX are only sent at a certain schedule, you may use exception parameter BcsOutboundWaitTimeExceptions to define special thresholds. If an exception threshold is used for a record, a small info icon will be displayed beneath the waiting time.

note

The amount of records being selected is limited by a maximum number of 500 per client.

Due to technical reasons, the column Sender will be blank if the RFC user (see Avantra Agent) is not in the same client as the BCS record.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | BcsOutboundWaitTimeWarn, BcsOutboundWaitTimeCrit, BcsOutboundClientMode, BcsOutboundClientList, BcsOutboundWaitTimeExceptions, MaskUserPersonalDetails, BcsOutboundWaitNumWarn, and BcsOutboundWaitNumCrit

## BG_RFC_ERROR​

This check monitors bgRFC queues for any errors. The monitoring parameter BgRfcErrorClientList configures the clients to include in this check.

This is available for SAP NetWeaver 2004s (SAP Basis 7.0), and is based on the SAP transaction `SBGRFCMON`, which exposes errors and locks.

### Reference Data​

Managed System | SAP System
Check Cycle | RealTime Monitoring
Depends on | RFCCONNECT
Monitoring Parameters | BgRfcErrorClientList

## BG_RFC_LOCK​

This check monitors bgRFC queues for any locks.

This is available for SAP NetWeaver 2004s (SAP Basis 7.0), and is based on the SAP transaction `SBGRFCMON`, which exposes errors and locks.

### Reference Data​

Managed System | SAP System
Check Cycle | RealTime Monitoring
Depends on | RFCCONNECT
Monitoring Parameters | None

## BW_PROCESSCHAINS​

The BW_PROCESSCHAINS check retrieves the status and runtime of all Process Chain runs during the last day. If one of the Process Chains terminates with status red, the check turns Critical. If one of the Process Chains exceeds the runtime thresholds, the check status turns to Critical or Warning, respectively.

Certain Process Chains may be excluded from the check by using BWProcessChainsExclude, the Check Result for canceled (status X) Process Chains may be defined with BWProcessChainsCancelledStatus as well.

note

To run this check, the Avantra RFC User must be defined in the standard client of the SAP BI System.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | BWProcessChainsRTCrit, BWProcessChainsCancelledStatus, and BWProcessChainsExclude

## BW_QUERYRUNTIME​

The BW_QUERYRUNTIME check lists queries within an SAP BI System that exceed a configurable runtime threshold.

note

To run this check, the Avantra RFC User must be defined in the standard client of the SAP BI System.

Next, it's necessary to enable statistics: proceed to transaction RSA1, choose Tools BW statistics for InfoCubes. See also SAP Note 557870 - FAQ: BW Query Performance.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | BWQueryRuntimeWarn, BWQueryRuntimeCrit, and BWQueryRuntimeExclude

## DIALOGPERF​

The DIALOGPERF check reports the performance of dialog steps in an ABAP SAP System.

The check returns an alert if a certain ratio of the dialog steps runs longer than a configurable threshold (e.g. 1 second).

The ratio, as well as the runtime threshold, can be configured.

The results are listed during a time period of one day (as provided by the underlying SAP System; cannot be configured).

A minimum number of steps can be defined also. So, if there are fewer dialog steps in the monitoring period these values are not considered for the Check Result. This is to take into account that only a reasonably large number of data can provide some valuable statistics.

Example of the DIALOGPERF daily check

    Overview of dialog steps below 1 sec runtime, time range: 00-24 h
    Minimum number of dialog steps (status is OK if below): 1000

    Date: Thu Jan  6 2005
    Status        Time  # Total   # >=1s   % >=1s    # <1s    % <1s
    ---------------------------------------------------------------
    OK           00-06       10        0      0.0       10    100.0
    WARNING      06-07     1326      146     11.0     1180     89.0
    WARNING      07-08     2053      220     10.7     1833     89.3
    WARNING      08-09     3322      338     10.2     2984     89.8
    WARNING      09-10     3991      344      8.6     3647     91.4
    WARNING      10-11     5368      369      6.9     4999     93.1
    WARNING      11-12     3157      254      8.0     2903     92.0
    OK           12-13     2465      116      4.7     2349     95.3
    WARNING      13-14     2880      319     11.1     2561     88.9
    WARNING      14-15     3934      294      7.5     3640     92.5
    WARNING      15-16     5193      493      9.5     4700     90.5
    WARNING      16-17     2302      278     12.1     2024     87.9
    WARNING      17-18     1083       74      6.8     1009     93.2
    OK           18-19       26        0      0.0       26    100.0
    CRITICAL->OK 19-20        6        2     33.3        4     66.7
    OK           21-24        4        0      0.0        4    100.0
    ---------------------------------------------------------------
    TOTAL        00-24    37120     3247      8.7    33873     91.3

The leftmost column displays the status for a particular time period. The next column displays the time period followed by the total number of dialog steps, the number of dialog steps running longer than DialogPerfRespTimeLimit, the ratio of those, the number of dialog steps running less or equal than DialogPerfRespTimeLimit, and the ratio of those.

Due to the defined DialogPerfRespTimeLimit value, the period 19-20 is not considered Critical.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | DialogPerfTimePeriod, DialogPerfRespTimeLimit, DialogPerfMinStepCount, DialogPerfPctCumulatedWarn, and DialogPerfPctCumulatedCrit

## DigitalNotesCompliancy​

This check performs a test digital note download and alerts if this fails.

note

This check will download SAP Note 2424539 - SAP Note Assistant: Test Note for Digital Signature Verification of SAP Note in order to test that the SAP System can download notes with digital signature correctly. In the note logs (for example, in transaction `SNOTE`) you will see the Avantra monitoring user downloading the note each day at the time of the daily check cycle. If that behavior is unwanted, please deactivate the check.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## FULLCHECK​

This check returns the overall status of all Checks executed during the Daily Check for the specified SAP System.

For instance, if the connection attempt to the SAP System failed, this check type returns a Critical message. If this check fails, all other dependent checks will have status Unknown.

In Ok status, the check explains which checks have been executed on the particular SAP System, which profiles have been collected, etc.

### Reference Data​

Managed System | SAP System
Check Cycle | Fullwe
Depends on | None
Monitoring Parameters | DailyCheckStart, DailyCheckSendTimeRange, and RunDailyCheckOnWE

## IDOCS​

This check gives an overview of IDOCs status and the corresponding group during the previous Full Check Cycle. If there are IDOCs in status group red, the check returns Warning. Additionally, a Warning message appears if IDOCs are found that are older than a configurable threshold.

This way, Avantra verifies if IDOCs are organized correctly.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | IdocsAgeWarn, and IdocsGrpRedDailyCountCrit

## IDOCSTAT​

This check monitors the number of modified IDOCs with a status in the status group red is monitored over a configurable period of time (default is one hour). Thresholds Warning and Critical can be defined.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | IdocsGrpRedCountCrit, IdocsGrpRedCountWarn, and IdocsGrpRedTimeSpan

## JavaJobs​

Monitors the status of jobs in the Java Scheduler that have run in the last 1 day (configurable by JavaJobsSelectRange). Shows a table of all jobs found, limited to 1000 entries. A job in status "Error" will turn the check to CRITICAL, a job in status "Cancelled" will turn it to WARNING.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | J2EECONNECT
Monitoring Parameters | JavaJobsSelectRange

## JavaJobStat​

Monitors the status of jobs in the Java Scheduler which have run in the last 60 minutes (configurable by JavaJobStatTimeSpan). Shows a table of all jobs found, limited to 1000 entries. A job in status "Error" will turn the check to CRITICAL, a job in status "Cancelled" will turn it to WARNING.

### Reference Data​

Managed System | SAP System
Check Cycle | Basic
Depends on | J2EECONNECT
Monitoring Parameters | JavaJobStatTimeSpan

## JavaSSLCertificatesValidity​

This check verifies if SSL certificates are valid, considering the information of the Keystore Views configured in the NetWeaver keystore service.

If certificates are found which are about to expire, the check status will be Critical if the remaining validity period is equal to or below SSLCertificatesValidityCrit. If the remaining validity period of one or more certificates is above SSLCertificatesValidityCrit but equal to or below SSLCertificatesValidityWarn, the check status will be Warning.

Expired certificates are reported for SSLCertificatesValidityIgnore days. After SSLCertificatesValidityIgnore days they will be ignored and no longer contribute to the check status, however, they are still reported in the check result output.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | SSLCertificatesValidityWarn, SSLCertificatesValidityCrit, and SSLCertificatesValidityIgnore

## JOBS​

This check verifies aborted SAP Jobs. All aborted jobs within the last Full Check Cycle; are counted, unless excluded by the JobAbortExclude Monitoring Parameter or excluded by JobUsersExclude Monitoring Parameter.

If the number of aborted jobs exceeds JobsDailyCountWarn or JobsDailyCountCrit the check will return the corresponding check status.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | JobsDailyCountWarn, JobUsersExclude, JobsDailyCountCrit, and JobAbortExclude

## JOBSTAT​

This check verifies aborted and delayed SAP Jobs. It consists of two sub-checks to get the number of aborted jobs and the number of delayed jobs.

- The number of aborted SAP jobs is detected over a configurable period of time (by default one hour). Warning and Critical thresholds may be defined, and there is also an option to exclude certain Jobs from being considered. The result is indicated with a message like

    OK - Number of aborted jobs in last 60 minutes: 1
    Aborted jobs are [#]: SLCA_LCK_SYNCHOWNERS [1]

The result includes the names of aborted jobs and the number in square brackets.

The number of delayed jobs is detected over configurable periods of time.

- The status of this sub-check is Warning if JobDelayedCountWarn or more jobs are delayed for more than JobDelayedTimeWarn minutes. The status is Critical if JobDelayedCountCrit or more jobs are delayed for more than JobDelayedTimeCrit minutes.

The result is indicated with a message like

    CRITICAL - Number of jobs being delayed for more than 2 minutes: 3, for more than 10 minutes: 2
    Delayed jobs are [h:mm]: /BDL/TASK_PROCESSOR [2:38], SAP_RSICFDLT [2:35|4:31],
    SAP_CCMS_MONI_BATCH_DP [10:05], SAP_COLLECTOR_FOR_NONE_R3_STAT [12:42]

The result includes the names of delayed jobs and the delay time. If more than one job with the same name is delayed, the individual delay times are displayed in a list separated by `|`.

The Monitoring Parameter JobDelayedIncludeExpired controls if expired jobs, i.e., jobs with configured and expired No start after date/time are considered as delayed jobs or not.

warning

This check might display jobs with a very long delay time, e.g. `Delayed jobs are [h:mm]: SAP_COLLECTOR_FOR_PERFMONITOR [18213:13]. This is no error!`

You will find this orphaned job in your system if you query for it the following way:

Run SAP transaction Job overview (i.e. SM37).

Query for the jobname, user name *, job status Released or Ready, and clear all job start condition from the selection.

The job will then be displayed in the result list.

The delay time may be so long, that it's not displayed in the job overview table of SM37 for whatever reason.

In order to clean up, you will usually delete the orphaned job.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | JobDelayedCountCrit, JobDelayedCountWarn, JobDelayedExclude, JobUsersExclude, JobDelayedIncludeExpired, JobAbortCountCrit, JobDelayedTimeWarn, JobAbortCountWarn, JobAbortExclude, JobAbortTimespan, JobDelayedTimeCrit, and JobMaxSelect

## LOCKTABLE​

This check verifies that all entries within the lock table are analyzed for their age. If entries are older than the configurable thresholds a corresponding Warning or Critical alert is raised.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | LockExclude, LockAgeWarn, and LockAgeCrit

## MII_Connect​

This check verifies whether the SAP MII (Manufacturing Integration and Intelligence) is up and running.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | J2EECONNECT
Monitoring Parameters | TimeoutMIIConnect

## MII_DataServers​

This check verifies whether the SAP MII (Manufacturing Integration and Intelligence) data server is available.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | MII_Connect
Monitoring Parameters | MIIDataServerNames, and MIIDataServerConnectorTypes

## MII_Schedules​

This check verifies whether SAP MII (Manufacturing Integration and Intelligence) has any long-running transactions. A long running transaction is one that is currently running, and the current runtime is longer than a threshold.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | MII_Connect
Monitoring Parameters | MIIScheduleStatus, and MIIScheduleNames

## MII_FailedTransactionStat​

This check verifies whether the SAP MII (Manufacturing Integration and Intelligence)has failed transactions (RTM). An SAP MII transaction is considered as failed if the transaction STATUS is either `Invalid`, `Failed`, `Terminated`, or `Exception`.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | MII_Connect
Monitoring Parameters | MIIFailedTransactionTimeSpan, MIIFailedTransactionNames, and MIIIgnoreTerminatedTransactions

## MII_FailedTransactions​

This check verifies whether the SAP MII (Manufacturing Integration and Intelligence)has failed transactions (Daily Check). An SAP MII transaction is considered as failed if the transaction STATUS is either `Invalid`, `Failed`, `Terminated`, or `Exception`.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | MII_Connect
Monitoring Parameters | MIIFailedTransactionNames, and MIIIgnoreTerminatedTransactions

## MII_LongRunningTransactions​

This check verifies whether SAP MII (Manufacturing Integration and Intelligence) has any long-running transactions. A long running transaction is one that is currently running, and the current runtime is longer than a threshold.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | MII_Connect
Monitoring Parameters | MIILongRunningTransactionWarn, and MIILongRunningTransactionCrit

## MII_FailedMessageStat​

This check verifies whether SAP MII (Manufacturing Integration and Intelligence) has any failed messages (Real-time monitoring).

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | MII_Connect
Monitoring Parameters | MIIFailedMessageServers, MIIFailedMessageTimeSpan, MIIFailedTransactionTimeSpan, MIIFailedMessageNames, and MIIFailedMessageTypes

## MII_FailedMessages​

The MII_FailedMessageStat check verifies whether SAP MII (Manufacturing Integration and Intelligence) has any failed messages (Daily Check).

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | MII_Connect
Monitoring Parameters | MIIFailedMessageServers, MIIFailedMessageNames, and MIIFailedMessageTypes

## NumberRanges​

This check verifies the Number Ranges of an ABAP system for its usage. It works similar to SAP standard report RSNUMHOT, however, the check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, NumberRanges checks in all clients except 066, so client 000 is included per default. You may change this behaviour using NumRangesClientMode, which can be set to deny (`Blacklist`) (default) or allow (`Whitelist`). Denylisted or allowlisted clients are specified by the NumRangesClientList parameter.

Per default, all Number Ranges are checked against thresholds NumRangesUsageWarn and NumRangesUsageCrit. If the usage of a Number Range exceeds the corresponding threshold, the check result will be either Warning or Critical. Per default, rolling number ranges are included in the check as well. You may change this behavior by unchecking NumRangesRollingIntervals.

To even further individualize the check behavior, you can use exclude number ranges from being checked and you can as well instruct the check to use individual thresholds as defined in SAP transaction `SNUM`. To exclude Number Ranges, you list them in NumRangesExclude. Excludes always work on all clients. To use individual thresholds already defined in your SAP System, you use NumRangesUseObjectDef. If you want to define individual thresholds specifically, you use the advanced NumRangesUsageEx parameter.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | NumRangesUsageEx, NumRangesUsageWarn, NumRangesUsageCrit, NumRangesClientMode, NumRangesClientList, NumRangesExclude, NumRangesUseObjectDef, NumRangesRollingIntervals, NumRangesStartYear, and NumRangesInclude

## PI_AdapterEngine​

This check verifies the PI Adapter Engine on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIReportOKMessages

## PI_AdapterFramework​

This check verifies all PI Java-based Adapter Engines (central and non-central) of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures, and PIReportOKMessages

## PI_AEMessages​

This check verifies for erroneous XML messages of the PI Adapter Engine as displayed by the Message Monitor of an SAP NetWeaver PI system. PI_AEMessages works exactly as the RealTime Monitoring check PI_AEMessagesStat, except that the timespan is always to the previous Daily Check record. Please see PI_AEMessagesStat for a description.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | PI_CONNECT
Monitoring Parameters | PIAEMessagesUseHttps, PIAEMessagesNumWarn, PIAEMessagesReceiverExclude, and PIAEMessagesNumCrit

## PI_AEMessagesStat​

This check verifies for erroneous XML messages of the PI Adapter Engine as displayed by the Message Monitor of an SAP NetWeaver PI system for the last PIAEMessagesStatTimeSpan minutes.

If the number of erroneous messages is above configurable threshold PIAEMessagesStatNumWarn, the status is set to Warning. If the number of messages found exceeds PIAEMessagesStatNumCrit, the status is set to Critical.

note

This check supports displaying the first 1000 results returned.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIAEMessagesUseHttps, PIAEMessagesStatNumCrit, PIAEMessagesReceiverExclude, PIAEMessagesStatTimeSpan, and PIAEMessagesStatNumWarn

## PI_BusinessProcessEngine​

This check verifies the PI Business Process Engines of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | PIExcludeSelftestFeatures, and PIReportOKMessages

## PI_CACHE​

The check message and status corresponds to the status of the XI Cache, i.e. a red light will be displayed as Critical and yellow as warning and green as Ok.

The following table lists the check results:

Check Result | Check Message
--- | ---
Ok | Cache contents are up-to-date
Warning | Cache update is in progress
Warning | Unknown state
Critical | Cache contents are obsolete
Critical | Cache contents are inconsistent

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | None

## PI_CommChannels​

The PI_CommChannels check verifies the status of PI communication channels. If a channel's status is `INACTIVE`, `UNKNOWN`, or `UNREGISTERED`, Avantra will report a Warning check status. If a channel's status is `ERROR`, Avantra will report a Critical check status. For the remaining possible status `OK`, Avantra's check status will be Ok, of course. The overall check status of PI_CommChannels will be the worst status of all channels.

note

Please note that per default, all communication channels with status INACTIVE are excluded, so if you want to receive a Warning for the same, you first need to change Monitoring Parameter PICommChannelsExclude.

Furthermore, you can use Monitoring Parameters PICommChannelsErrsWarn and PICommChannelsErrsCrit to delay the time an error is reported as Warning or Critical state. Per default, an error will be reported immediately as Critical since PICommChannelsErrsCrit is set to 1. If you change the parameters, e.g. to PICommChannelsErrsWarn 2 and PICommChannelsErrsCrit 3, a channels check status will be still Ok after the first error is detected. If the error persists to the next check cycle, check status will be Warning. If it still persists to the third check cycle in sequence, check status will be Critical.

Monitoring parameter PICommChannelsExclude is used to exclude certain communication channels from being checked. You can exclude on all information provided by the check's result table, i.e., Party, Service, Channel, Activation State, and Channel State.

note

To use this check, you'll have to make sure the action `xi_af_channel_admin_display` is assigned to the SAP Java user.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PICommChannelsTimeCrit, PICommChannelsCountCrit, PICommChannelsTimeWarn, PICommChannelsCountWarn, PICommChannelsErrsWarn, PICommChannelsErrsCrit, and PICommChannelsExclude

## PI_CONNECT​

This check verifies if the basic infrastructure for PI/XI monitoring is up and running.

This check returns Critical when the SAP Runtime Workbench is not accessible using the Avantra J2EE user. This can be due to a lack of permissions of the user or due to an incompletely configured PI system.

Additionally, PI_CONNECT serves as a overview check for all other PI checks (except PI_CACHE), so if this check fails, all the other dependent checks will return Unknown.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | J2EECONNECT
Monitoring Parameters | None

## PI_IEMessages​

This check looks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction `SXMB_MONI`. PI_IEMessages works exactly as the RealTime Monitoring check PI_IEMessagesStat, except that the timespan is always to the previous Daily Check record. Please see PI_IEMessagesStat for a description.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | PIIEMessagesNumWarn, PIIEMessagesNumCrit, PIIEMessagesClientMode, and PIIEMessagesClientList

## PI_IEMessagesStat​

This checks looks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction SXMB_MONI when queried for XML messages in status group Errors for the last PIIEMessagesStatTimeSpan minutes.

PI_IEMessagesStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, PI_IEMessagesStat checks in all clients except 000 and 066. You may change this behaviour using PIIEMessagesClientMode, which can be set to deny (`Blacklist`) or allow (`Whitelist`). Denylisted or allowlisted clients are specified by the PIIEMessagesClientList parameter.

If the number of erroneous messages is above configurable threshold PIIEMessagesStatNumWarn, the status is set to Warning. If the number of messages found exceeds PIIEMessagesStatNumCrit, the status is set to Critical.

Each client is checked separately against the thresholds. The client column of the result table hash either no color, meaning there are erroneous messages but the number for this client is still below PIIEMessagesStatNumWarn. Yellow and red color means that the number of erroneous messages exceeds the corresponding thresholds.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | PIIEMessagesStatTimeSpan, PIIEMessagesStatNumWarn, PIIEMessagesStatNumCrit, PIIEMessagesClientMode, and PIIEMessagesClientList

## PI_IntegrationDirectory​

This check verifies the PI Integration Directories of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## PI_IntegrationEngine​

This check verifies the PI Integration Engines of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## PI_IntegrationRepository​

This check verifies the PI Integration Repositories of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## PI_J2SEAdapterEngine​

The PI_J2SEAdapterEngine check verifies all J2SE-based adapter engines of all PI Domains accessible on the current instance for availability and selftest errors

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System (ABAP+Java PI/XI with kernel release ≥ 6.40 and < 7.30)
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures, PIReportOKMessages, MediumCheckCycleTime

## PI_MappingRunTime​

This check verifies the PI Mapping Runtimes of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## PI_RuntimeWorkbench​

This check verifies the PI Runtime Workbench of all PI Domains accessible on the current instance for availability and selftest errors.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## PI_SystemLandscapeDir​

This check verifies the PI System Landscape Directory of all PI Domains accessible on the current instance for availability.

The check works corresponding to the Component Monitoring in the SAP Runtime Workbench. If features report a not OK status, but this is not of concern, you can exclude these features from contributing to the check status by PIExcludeSelftestFeatures.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | PI_CONNECT
Monitoring Parameters | PIExcludeSelftestFeatures

## QRFC_IN​

This check verifies the number of queued records for all inbound qRFC queues as done with SAP qRFC Monitor (SAP transaction `SMQ2` for inbound queues). If the number of waiting records is above the Warning or Critical threshold a corresponding alert is raised.

The queue state is not monitored with this check, but with QRFC_IN_ERRQ.

It is possible to exclude queues from being monitored by defining QRFCInQueueExclude.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | QRFCInQueueExclude, and QRFCInRecQueuedWarn

## QRFC_IN_ERRQ​

This check verifies inbound qRFC queues as done with SAP qRFC Monitor (SAP transaction `SMQ2` for inbound queues).

If the number of hanging or erroneous queues is equal to or above QRFCInQueueHangWarn but below QRFCInQueueHangCrit, the check status will be Warning. If the number of hanging or erroneous queues is higher than QRFCInQueueHangCrit, a critical alert is raised.

It is possible to exclude queues from being monitored by defining QRFCInQueueExclude.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | QRFCInQueueExclude, QRFCInQueueHangCrit, and QRFCInQueueHangWarn

## QRFC_OUT​

The QRFC_OUT check verifies the number of queued records for all outbound qRFC queues as done with SAP qRFC Monitor (SAP transaction `SMQ1` for outbound queues). If the number of waiting records is above the Warning or Criticalthreshold a corresponding alert is raised.

The queue state is not monitored with this check, but with QRFC_OUT_ERRQ.

It is possible to exclude queues from being monitored by defining QRFCOutQueueExclude.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | QRFCOutQueueExclude, QRFCOutRecQueuedWarn, and QRFCOutRecQueuedCrit

## QRFC_OUT_ERRQ​

The QRFC_OUT_ERRQ check verifies outbound qRFC queues as done with SAP qRFC Monitor (SAP transaction `SMQ1` for outbound queues).

If the number of hanging or erroneous queues is equal to or above QRFCOutQueueHangWarn but below QRFCOutQueueHangCrit, the check status will be Warning. If the number of hanging or erroneous queues is higher than QRFCOutQueueHangCrit, a critical alert is raised.

It is possible to exclude queues from being monitored by defining QRFCOutQueueExclude.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | QRFCOutQueueExclude, QRFCOutQueueHangCrit, and QRFCOutQueueHangWarn

## RTCCTool​

The RTCCTool check is to access the SAP support backbone and monitor whether the current SAP system meets all necessary prerequisites. It forms a list of the actions to allow support services delivery to the given SAP system. This includes note installation, software patches, etc. It is executed only on systems with ABAP component ST-A/PI.

note

This check is not available for SAP Systems lower than 7.30 SP5.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## SAPActiveServerProfiles​

If a user profile has been changed, you can perform extensive checks for it, e.g., the profile's semantics, syntax, and parameter names. The system displays the result of the profile checks as a log containing either warnings or error messages. The SAPActiveServerProfiles check is performed via transaction RZ10 and displays the results in the report. Any lines where the entry type is error (E) will be shown as CRITICAL, and any lines where the entry type is warning (W) will be shown as WARNING. If no warning (W) or error (E) entry types were found, then the check has the status OK.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | IgnoreProfileParametersPatterns

## SAPBufferSummary​

The SAP Buffer (transaction `ST02`) is displayed in Avantra showing the Hit ratio, Swap and Yesterdays Swap. For different buffers, you can set the parameters individually in Avantra UI. The user can define WARNING and CRITICAL thresholds for the Hit ratio (below a certain percentage) and for Swap delta (today - yesterday) The hit ratio is the total number of cache hits divided by the total number of cache lookups over the last chosen period of time. The lower the percentage, the slower the system performance. The swap is the process of exchanging/updating the data in the buffer from outside. The more swaps are performed, the slower the system performance.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | SAPBufferSummaryHitCrit, SAPBufferSummaryHitWarn, SAPBufferSummarySwapDeltaCrit, SAPBufferSummarySwapDeltaWarn, and SAPBufferSummaryIgnoreSwap

## SAPControlConnect​

This check monitors the connection:

- Of remote monitored systems when a `SAP Control` URL is defined.
- Of SAP Systems when a `sapcontrol` credential has been set.

In other words, it checks the connection status to SAP Control for a SAP System.

If a connection cannot be made, SystemAlive will be set to Critical, and RFCCONNECT / J2EECONNECT will be set to Unknown.

### Reference Data​

Managed System | SAP System
Check Cycle | Basic
Depends on | AGENTALIVE
Monitoring Parameters | None

## SAPLicense​

This system check retrieves information about SAP Licences through the SLICENSE transaction that can contain permanent or temporary licenses. The results display the SAP licenses with their validity dates.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | SAPLicenseIgnore, SAPLicenseCrit, SAPLicenseWarn, and SAPLicenseIgnoreMaintenance

## SAP_Notes​

This check collects the information about SAP Notes implemented in the system. The data includes the note number, note version, implementation status, etc. If at least one note is in the Incompletely implemented status, the check result is Critical. If such notes are not found, but there are some in the Obsolete version implemented status, then the check result is Warning. If all notes are in the Completely implemented or Obsolete status, then the result is Ok.

note

This check is not available for SAP Systems lower than 7.30 SP5.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | SAPNotesCanBeImplStatus, SAPNotesExclude, SAPNotesComponentExclude, and SAPNotesComponentInclude

## SAPInitialConsistency​

The SAPInitialConsistency check determines inconsistencies in the SAP System. The initial consistency check determines whether:

- The release number in an SAP kernel matches the release number stored in the database system.
- The character set specified in the SAP kernel matches the character set specified in the database system.
- Critical structure definitions defined in the data dictionary and the SAP kernel are identical. The structures to be checked include `SYST`, `T100`, `TSTC`, `TDCT` and `TFDIR`.

Avantra executes the report `RSICC000`. If errors occur, then the result is Critical. Otherwise, the result is OK.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## SAPInternalRFCConsistency​

The SAPInternalRFCConsistency check performs the RFC consistency check via transaction SM59, checks the Internal Connections, and displays the results in the report. The report has a status WARNING if any returned status has the text "RFC destination can be deleted" otherwise the status is OK.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## SAPSegmentOverview​

This check monitors the segments of the SAP database and retrieves the data about the segments. The SAPSegmentOverview check is performed via transaction `RZ21` and displays the results in the report. Any ONLINE segment status will be shown as OK, and any SHUTDOWN status will be shown as WARNING.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## SAPTemSeConsistency​

TemSe is a store for temporary sequential data; that is, objects that are not normally permanently held in the system are stored in the TemSe. The spool system uses TemSe to store output data temporarily. The SAPTemSeConsistency check retrieves the data to see whether entries in the TemSe data store are consistent. The report executed is RSICC000 (transaction SP12). If this report returns no data, the status of the check is OK. If there are issues detected, the check result is CRITICAL.

### Reference Data​

Managed System | SAP System
Check Cycle | Daily
Depends on | RFCCONNECT
Monitoring Parameters | None

## SAPOpModeConsistency​

Operation modes let the system configuration adapt to varying requirements, maximizing the use of available system resources. An operation mode defines a resource configuration for the instances in your system. You can use it to determine which instances are started and stopped and how the individual services are allocated for each instance in the configuration. Define the operation modes to suit specific system requirements, for example, to provide additional dialog or background processing resources during a particular period of time without restarting the system. The SAPOpModeConsistency check performs the operation mode consistency check via transaction RZ04, checks the Instances/Operation modes, and displays the results in the report. The report has the status OK if no error (E) types exist in the results - otherwise, the status is CRITICAL. Any error type lines will be shown as CRITICAL (Colour Red).

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | IgnoreProfileParametersPatterns

## SAPSpoolConsistency​

You use the SAP Spool Consistency check to see whether tables that contain spool requests, output requests, and output data are inconsistent. If necessary, you can delete inconsistencies. Along with deleting old spool requests, this check is one of the most important functions for maintaining the SAP spool database. We strongly recommend performing this check in the background regularly. The SAPSpoolConsistency check is performed via transaction SPAD and displays the results in the report. The report has the status OK if the message 'No inconsistent objects found' is output. The status is CRITICAL if the message 'No inconsistent objects found' is NOT output.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## ServiceDataCCN​

This check monitors the connection between the SAP System and SAP Solution Manager. If the connection is established, its information will be displayed in a new tab under SAP System Detail > Relations.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | None

## SHORTDUMPS​

This check consist of two sub-checks:

- All short dumps within the last Full Check Cycle are reported except they are excluded by ShortDumpExclude.
  If the number of short dumps to be reported exceeds ShortDumpDailyCountWarn but does not exceed ShortDumpDailyCountCrit the check results as Warning. If the number exceeds ShortDumpDailyCountCrit the check results as Critical.
- It is also checked if there are short dumps older than a configurable period of time (i.e. if short dumps are reorganized correctly). If there are old short dumps found, the check turns to Warning unless the check status is Critical already in the first sub-check.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | ShortDumpCountMaxSelect, ShortDumpExclude, ShortDumpDailyCountWarn, ShortDumpDailyCountCrit, and ShortDumpAgeWarn

## ShortDumpStat​

The check verifies the number of short dumps over a configurable period of time (default one hour).

If Warning or Critical thresholds are exceeded, a corresponding Warning or Critical Check Result is returned.

You can define a list of short dumps that shall be excluded from this check by using ShortDumpExclude, e.g. you may want to suppress `TIME_OUT` short dumps which may happen once a user maximum dialog idle time has been exceeded.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | ShortDumpCountWarn, ShortDumpCountMaxSelect, ShortDumpCountCrit, ShortDumpTimeSpan, and ShortDumpExclude

## SLT_SrcTrgt​

The check compares the number of records in the source and target tables. It is generated for each configuration name/MTID found in the SLT system, however, you can use the SLTSrcTrgtConfigName and SLTSrcTrgtMtId parameters to filter them. You can also set a WARNING/CRITICAL threshold for the difference between the source and target line numbers.

We currently only support a combination of an SAP source system and a HANA HDB target system. Therefore, if the SLT configuration has unsupported source and target types, an error message will be returned.

### Reference Data​

Managed System | SAP System
Check Cycle | (../../Glossary/#check-cycle)
Depends on | RFCCONNECT
Monitoring Parameters | SLTSrcTrgtRecordDiff, SLTSrcTrgtConfigName, SLTSrcTrgtMtId, SLTSrcTrgtWarn, SLTSrcTrgtCrit, and SLTDisableInactiveConfig

## SLT_Status​

The check returns the status for each corresponding SLT configuration - `SLT_Status_<Configuration_name>` - along with the available sub-check statuses. Considered configurations can be filtered using the SLTStatusConfigName parameter. If the connection to the replication source or (and) replication target is broken, then the check result is CRITICAL, otherwise - OK. If the connection is inactive, the check result will be UNKNOWN with the message “Configuration `<configuration name>` is not inactive”.

### Reference Data​

Managed System | SAP System
Check Cycle | (../../Glossary/#check-cycle)
Depends on | RFCCONNECT
Monitoring Parameters | SLTStatusConfigName, SLTStatusMtId, SLTStatusIgnored, and SLTDisableInactiveConfig

## SLT_UnprocessedRecords​

The check retrieves the number of unprocessed records for each table to be replicated. A separate check entry is created for each SLT configuration available in SLT system - SLT_UnprocRecs_`<configuration_name>`. In case the configuration is inactive, the check result will be UNKNOWN with the message “Configuration `<configuration name>` is not inactive”.

### Reference Data​

Managed System | SAP System
Check Cycle | (../../Glossary/#check-cycle)
Depends on | RFCCONNECT
Monitoring Parameters | SLTUnprocRecsConfigName, SLTUnprocRecsMtId, SLTUnprocRecsLimit, SLTUnprocRecordsClient, and SLTDisableInactiveConfig

## SLT_IUCJobs​

The check allows you to get the number of SLT jobs completed over the time periods defined by parameters SLTIucJobsMinutesWarn and SLTIucJobsMinutesCrit. If there are no finished jobs during the SLTIucJobsMinutesCrit period, the check result is CRITICAL. If there are no finished jobs during the SLTIucJobsMinutesWarn period, the check result is WARNING. Currently, only finished jobs are taken into account, active jobs are not selected.

### Reference Data​

Managed System | SAP System
Check Cycle | (../../Glossary/#check-cycle)
Depends on | RFCCONNECT
Monitoring Parameters | SLTIucJobs, SLTIucJobsMinutesWarn, and SLTIucJobsMinutesCrit

## SM_LMDBConsistency​

The check retrieves the Solution Manager LMDB consistency status. The check status is set dependent of the rating number where 1 = Ok, 2 = Warning and 3 = Critical. This check is enabled automatically when a Solution Manager system is detected.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | None

## SM_SolmanSetup​

This check reflects the statuses of the mandatory scenarios of SAP Solution Manager (i.e. System Preparation, Infrastructure Preparation, Basic Configuration). The overall check status will show Critical if some of the mandatory configurations contain errors or Warning if some contain warnings or configurations that were not performed. This check is enabled automatically when a Solution Manager is detected.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | SMClient

## SPOOL​

This check consist of two sub-checks:

- All erroneous or unprocessed output requests within the last Full Check Cycle are reported except they are excluded by SpoolOutAccessMethodExclude, SpoolOutDevExclude, or SpoolOutDevTypeExclude.
  If the number of output requests to be reported exceeds SpoolNOkDailyCountWarn but does not exceed SpoolNOkDailyCountCrit the check results as Warning. If the number exceeds SpoolNOkDailyCountCrit the check results as Critical.
- It is also checked if there are output requests older than a configurable period of time (i.e. if short dumps are reorganized correctly). If there are old output requests found, the check turns to Warning unless the check status is Critical already in the first sub-check.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | SpoolOutDevTypeExclude, SpoolOutAccessMethodExclude, SpoolOutStatusInclude, SpoolReqAgeWarn, SpoolOutDevExclude, SpoolOutDevInclude, SpoolNOkDailyCountWarn, and SpoolNOkDailyCountCrit

## SPOOLSTAT​

This check consists of two sub-checks:

- The number of unprocessed or erroneous output requests is detected over a configurable period of time (default one hour). Warning and Critical thresholds may be defined. You may define output devices excluded from this check by using SpoolOutAccessMethodExclude, SpoolOutDevExclude, or SpoolOutDevTypeExclude.
- Verifies the current number of spool requests in the system as a percentage of the maximum possible defined by the corresponding number range.
- If the usage in the ratio is higher than the SpoolNumRangeUsageCrit or SpoolNumRangeUsageWarn thresholds, a corresponding Critical or Warning check status is returned.

You may set SpoolNumRangeUsageEnable to 0 if you want to disable this part of the check.

### Reference Data​

Managed System | SAP System
Check Cycle | Medium
Depends on | RFCCONNECT
Monitoring Parameters | SpoolNOkTimeOffset, SpoolOutDevTypeExclude, SpoolOutAccessMethodExclude, SpoolNumRangeUsageEnable, SpoolOutStatusInclude, SpoolNOkCountWarn, SpoolNOkCountCrit, SpoolOutDevExclude, SpoolNOkTimeSpan, SpoolOutDevInclude, SpoolNumRangeUsageCrit, and SpoolNumRangeUsageWarn

## CRM_BDOC_MONITOR​

This check monitors the SAP system and retrieves information about CRM BDOC errors.

### Reference Data​

Managed System | SAP System
Check Cycle | (../../Glossary/#check-cycle)
Depends on | RFCCONNECT
Monitoring Parameters | BDOCMonitorClients, BDOCMonitorDays, BDOCMonitorWarn, BDOCMonitorCrit, and BDOCMonitorType

## SSLCertificatesValidity​

This checks if SSL certificates are valid, just the same way as transaction STRUST or the report `SSF_ALERT_CERTEXPIRE` would do.

The output of the check is similar to report `SSF_ALERT_CERTEXPIRE`. If certificates are found, which are about to expire, the check status will be Critical if the remaining validity period is equal to or below SSLCertificatesValidityCrit. If the remaining validity period of one or more certificates is above SSLCertificatesValidityCrit but equal to or below SSLCertificatesValidityWarn, the check status will be Warning.

Expired certificates are reported for SSLCertificatesValidityIgnore days. After SSLCertificatesValidityIgnore days they will be ignored and no longer contribute to the check status, however, they are still reported in the check result output.

note

Currently, this check can only read certificates that are accessible to the main RFC user. For certificates that are client-specific, you need to set the RFC credential to the correct client that can view all certificates.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | SSLCertificatesValidityWarn, SSLCertificatesValidityPSEErrors, SSLCertificatesValidityCrit, and SSLCertificatesValidityIgnore

## SXMB_Messages​

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction `SXMB_MONI`. SXMB_Messages works exactly as the RealTime Monitoring check SXMB_MessagesStat, except that the timespan is always to the previous Daily Check record. Please see SXMB_MessagesStat for a description.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | SXMBMessagesClientMode, SXMBMessagesClientList, SXMBMessagesNumWarn, and SXMBMessagesNumCrit

## SXMB_MessagesStat​

Checks for erroneous XML messages of the PI Integration Engine as displayed by ABAP transaction `SXMB_MONI` when queried for XML messages in status group Errors for the last SXMBMessagesStatTimeSpan minutes.

SXMB_MessagesStat check is designed to retrieve data of all clients found in an SAP system, no matter which client is used for RFC by the Avantra Agent. Per default, SXMB_MessagesStat checks in all clients except `000` and `066`. You may change this behaviour using SXMBMessagesClientMode, which can be set to deny (`Blacklist`) or allow (`Whitelist`). Denylisted or allowlisted clients are specified by the SXMBMessagesClientList parameter.

If the number of erroneous messages is above configurable threshold SXMBMessagesStatNumWarn, the status is set to Warning. If the number of messages found exceeds SXMBMessagesStatNumCrit, the status is set to Critical.

Each client is checked separately against the thresholds. The client column of the result table hash either no color, meaning there are erroneous messages but the number for this client is still below SXMBMessagesStatNumWarn. Yellow and red color means that the number of erroneous messages exceeds the corresponding thresholds.

### Reference Data​

Managed System | SAP System
Check Cycle | Basic
Depends on | RFCCONNECT
Monitoring Parameters | SXMBMessagesClientMode, SXMBMessagesClientList, SXMBMessagesStatTimeSpan, SXMBMessagesStatNumWarn, and SXMBMessagesStatNumCrit

## SystemAlive​

The check verifies if the minimum requirements for the technical operation of a SAP System are fulfilled from a monitoring perspective.

These requirements depend on the nature of the SAP System, but basically there has to be a minimum number of SAP Instances available, i.e. they have to be detected and the corresponding connect checks have to succeed. If one of the required SAP Instances is not available SystemAlive will report an error message.

The following list describes the conditions that have to be fulfilled for the SystemAlive check to be OK](../../Glossary/#check-status):

- ABAP only with classical Central SAP Instance
  - At least one Central SAP Instance has to be discovered and monitored with the RFCCONNECT and ASCS_MSGSRV checks being OK.
  - The SAP Database instance has to be discovered and monitored with the [DBCONNECT]built-in-checks#dbconnect) check being OK.
- ABAP only with Abap_Scs SAP Instance
  - At least one ABAP Dialog SAP Instance has to be discovered and monitored with the RFCCONNECT check being OK.
  - An Abap_Scs SAP Instance has to be discovered and monitored with the ASCS_MSGSRV check being OK.
  - The SAP Database instance has to be discovered and monitored with the [DBCONNECT]built-in-checks#dbconnect) check being OK.
- Java only SAP System
  - At least one Java SAP Instance has to be discovered and monitored with the J2EECONNECT check being OK.
  - A Java_Scs SAP Instance has to be discovered and monitored with the SCS_MSGSRV check being OK.
  - The SAP Database instance has to be discovered and monitored with the [DBCONNECT]built-in-checks#dbconnect) check being OK.
- ABAP+Java (double stack) SAP Instance
  - At least on Central SAP Instance has to be discovered and monitored with the RFCCONNECT and ASCS_MSGSRV checks being OK, or at least one Dialog SAP Instance with RFCCONNECT and an Abap_Scs SAP Instance with ASCS_MSGSRV being OK.
  - At least one Java SAP Instance has to be discovered and monitored with the J2EECONNECT check being OK.
  - A Java_Scs SAP Instance has to be discovered and monitored with the SCS_MSGSRV check being OK.
  - The SAP Database instance has to be discovered and monitored with the [DBCONNECT]built-in-checks#dbconnect) check being OK.

note

Although the SystemAlive may report OK, your system may face e.g. performance problems if one or multiple SAP Instances are not available. From Avantra 23.1, when one of the mandatory checks is not OK, i.e. Critical or Unknown, the SystemAlive will also switch to Critical.

The Monitoring Parameter SysAliveIncompleteTimeCrit plays an important role once it comes to a cluster switch. If a cluster does switch, one of the required SAP Instances may vanish until the cluster switch has finally finished. To cover these situations the SystemAlive check first turns to Warning. If the SAP Instances does not come up SysAliveIncompleteTimeCrit minutes, the check turns to Critical.

Example: SystemAlive OK

- Classical Central SAP Instance with double-stack and Database instance on the same host.

    DDatabase server is basel
    DBCONNECT check is OK for C11
    Central instance is basel_C11_00
    ABAP central services instance is basel_C11_00
    J2EE central services instance is basel_C11_01
    RFCCONNECT check is OK for basel_C11_00
    J2EECONNECT check is OK for basel_C11_00
    ASCS_MSGSRV check is OK for basel_C11_00
    SCS_MSGSRV check is OK for basel_C11_01

- Java-only system, all components on a single host

    Database server is colmar
    DBCONNECT check is OK for P01
    Central instance is colmar_P01_01
    J2EE central services instance is colmar_P01_02
    J2EECONNECT check is OK for colmar_P01_01
    SCS_MSGSRV check is OK for colmar_P01_02

Example:SystemAlive not OK

- No active instances found.

    No active instances found since 00:05 [hh:mm]

Status is Warning or Critical depending on SysAliveIncompleteTimeCrit.

- System is incomplete. This happens if there are instances available but Avantra can no longer determine the type of the SAP System. The status again depends on the time expired and the SysAliveIncompleteTimeCrit setting.

    The system is incompletely monitored since 00:05 [hh:mm].
    Not all components of a fully operational system have been found.

### Reference Data​

Managed System | SAP System
Check Cycle | Basic
Depends on | None
Monitoring Parameters | SysAliveIncompleteTimeCrit

## TMS_Imports​

Checks the return code of imported transport requests and works exactly like the RealTime Monitoring check TMS_ImportStat, except that the timespan is always to the previous Daily Check record and non-imported transport requests are shown. Please see TMS_ImportStat for a description. Please note that TMS_Imports uses its own Monitoring Parameters TMSImportReturnCodeCrit and TMSImportReturnCodeWarn.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | TMSImportReturnCodeWarn, TMSImportReturnCodeCrit, TMSNotImportedCrit, and TMSIncludeNotImported

## TMS_ImportStat​

Checks the return code of imported transport requests of last TMSImportStatTimeSpan minutes. If one or more imports are finished with return code ≥ 8, the check status will be Critical. If no import with return code ≥ 8, but one or more ≥ 4 are found, the check status will be Warning. Otherwise, the check status will be OK.

This default behaviour can be changed by Monitoring Parameters TMSImportStatReturnCodeCrit and TMSImportStatReturnCodeWarn. For example, you might not want to have warning return codes to contribute to the check result. To do this, you simply change Monitoring Parameter TMSImportStatReturnCodeWarn from the default value 4 to off. Or you might not want to have erroneous return codes starting from 8 be reported as critical result for development or quality assurance systems but as warning. To achieve this, you would change TMSImportStatReturnCodeCrit from `8` to `off` and TMSImportStatReturnCodeWarn from `4` to `8`. See more examples in table below.

Monitoring Parameters Examples for TMS_ImportStat

Return Codes and Check Status | Monitoring Parameters setting
--- | ---
Warning RC 4 → Warning, Error RC ≥ 8 → Critical (Default) | TMSImportStatReturnCodeWarn 4, TMSImportStatReturnCodeCrit 8 (Default)
Warning RC 4 ignored → OK, Error RC ≥ 8 → Critical | TMSImportStatReturnCodeWarn off, TMSImportStatReturnCodeCrit 8
Warning RC 4 ignored → OK, Error RC ≥ 8 → Warning | TMSImportStatReturnCodeWarn 8, TMSImportStatReturnCodeCrit off
All Warning and Error RC ignored → OK (not recommended) | TMSImportStatReturnCodeWarn off, TMSImportStatReturnCodeCrit off

This check is accompanied by Daily Check TMS_Imports, which checks transport request imports back to the previous Daily Check schedule.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | TMSImportStatTimeSpan, TMSImportStatReturnCodeWarn, and TMSImportStatReturnCodeCrit

## TMS_Status​

This check performs various TMS-related tests.

note

This check is not available for SAP Systems lower than 7.30 SP5.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | RFCCONNECT
Monitoring Parameters | TMSStatusIgnoreSid, and TmsStatusIncludeImportOverview

## TMS_UserCompliance​

Checks transport requests on the general compliance rule that owner and importer of a transport request are different users. If transport requests are found with the owner of the transport request equal to the user importing it, the Check Result will show the corresponding transport requests and the status will be Warning.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | None

## TRFC_IN​

Displays an overview of all incoming tRFC records (see SAP transaction `SM58`) and displays the amount of records and the date / time of the oldest record for each different tRFC state.

The check will return a Warning if there are incoming tRFC records older than a configurable period of time (default one day).

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | TRFCAgeWarn

## TRFC_OUT​

Displays an overview of all outgoing tRFC records (see SAP transaction `SM58`) and displays the amount of records and the date / time of the oldest record for each different tRFC state.

The check will return a Warning if there are outgoing tRFC records older than a configurable period of time (default one day).

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | TRFCAgeWarn

## TRFCInStat​

Retrieves the status of incoming transactional RFC records over a configurable period. If the sum of records with the status `CPICERR`, `SYSFAIL`, or `SYSLOAD` is greater than the Warning or Critical threshold, a corresponding alert is raised.

note

This check is not available for SAP Systems lower than 7.30 SP5.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | TRFCInTimeSpan, TRFCInCountWarn, TRFCInCountCrit, TRFCInExcludeFunction, TRFCInExcludeUser, and TRFCInTimeOffset

## TRFCOutStat​

Checks the status of outgoing transactional RFC records (see SAP transaction `SM58`) over a configurable period of time (default is one hour). If the sum of records with status `CPICERR`, `SYSFAIL`, or `SYSLOAD` is greater than the Warning or Critical threshold, a corresponding alert is raised.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | TRFCOutTimeOffset, TRFCOutTimeSpan, TRFCOutCountWarn, TRFCOutCountCrit, TRFCOutExcludeFunction, and TRFCOutExcludeUser

## UPDATEQUEUE​

If the number of unprocessed update records older than UpdateQueueAgeCrit seconds exceeds UpdateQueueCountCrit the check turns Critical.

Otherwise, if the number of unprocessed update records older than UpdateQueueAgeWarn seconds exceeds UpdateQueueCountWarn the check turns Warning. Otherwise, the check is Ok.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | UpdateQueueAgeWarn, UpdateQueueAgeCrit, UpdateQueueCountWarn, and UpdateQueueCountCrit

## UPDATERECERR​

All erroneous or unprocessed update requests within the Full Check Cycle are reported as Warning messages.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | None

## UpdateRecErrStat​

The number of erroneous update records is checked during a configurable period of time (default is one hour). Warning and Critical thresholds may be defined.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | UpdateErrCountCrit, UpdateRecErrTimeSpan, and UpdateErrCountWarn

## UpdateStat​

If the SAP System's global update switch as displayed in transaction `SM13` is deactivated, the check turns Critical. The reason why the updating has been deactivated is reported in the check message.

### Reference Data​

Managed System | SAP System
Check Cycle | medium
Depends on | RFCCONNECT
Monitoring Parameters | None

## USER_PWD_AUDIT​

Checks SAP standard users `SAP*`, `DDIC`, `SAPCPIC`, `TMSADM`, and `EARLYWATCH` for well-known standard passwords.

If the basis release of your SAP system is 7.00 onwards, the results of the original SAP report `RSUSR003` are reported using the advanced check result format including tabular details for each checked user.

note

For SAP basis release 7.00 it depends on the patch level of the report `RSUSR003`. If recent SAP notes are not applied, Avantra Agent falls back to a simpler check procedure producing plain text output only.

The table displayed corresponds to the one displayed by `RSUSR003`, except that a new column Excluded is added to show which users have been excluded by Monitoring Parameter UserPWDAuditExclude.

If the Password Status of one or more users is reported in red color by `RSUSR003`, the check result will be Critical. If a user with red color Password Status is locked, USER_PWD_AUDIT will return a Warning status and the user is marked in yellow color in the result table.

Furthermore, the lock status is checked. If one of the standard users is locked due to unsuccessful login attempts, by default a Warning is raised. This behaviour can be controlled by Monitoring Parameter UserPWDAuditFailedLogonSeverity: if this parameter is set to `Critical` a user locked due to unsuccessful login attempts will be reported as Critical.

If UserPWDAuditFailedLogonSeverity is set to `OK` (not recommended), a user locked due to unsuccessful login attempts will not contribute to the check result.

For SAP systems prior to 7.00, the check result will use a text table presentation and the following check logic which does not depend on `RSUSR003`. If a users password is set to a well-known standard password, the check will return a Warning status, unless the user is excluded by parameter UserPWDAuditExclude.

This check additionally verifies if the users exist in each client. If the user `SAP*` does not exist, the check will return a Warning status (unless the profile parameter `login/no_automatic_user_sapstar` is set to 1) since login with password pass may still be possible.

The `user does not exist` message is suppressed for user `EARLYWATCH` for all clients other than `066`.

### Reference Data​

Managed System | SAP System
Check Cycle | Full
Depends on | None
Monitoring Parameters | UserPWDAuditFailedLogonSeverity, and UserPWDAuditExclude

## WORKLOAD​

The average dialog response time of the SAP System during the last Full Check Cycle is reported and compared with the Warning (default 1000 ms) and Critical (default 2000 ms) thresholds. If responses times are higher than the defined thresholds, the check will return the corresponding Check Result.

Only transactions with at least DialogPerfMinStepCount steps are considered.

### Reference Data​

Managed System | SAP System
Check Cycle | Daily
Depends on | None
Monitoring Parameters | DialogPerfMinStepCount, DialogRespTimeWarn, and DialogRespTimeCrit