XPRA upgrade check is a report, which is executed automatically after importing a transport to a system. The report checks the software for most common inconsistencies, which are affecting the functionality of Insights.

Inconsistencies could arise, for example, from an incorrect definition in customizing, which could be allowed in previous versions or from the development of some new features (newly developed features can sometimes use existing DB tables with a changed structure), or for some other, unexpected, reasons. If some inconsistencies are found, the report brings the problem definitions into a consistent state or changes the data structure into a new one.

In short, XPRA check is a program, which is updating, controlling, and fixing master data, transactional data, and customizing.

The 'XPRA upgrade check' consists of the following independent checks:

DETSYS table consistency

Checks, if the new table with detail table version for each system is consistent with the table of all detail table versions. If the new table is empty, the check will fill it with correct entries. Otherwise, it will check the creation- and last change timestamp for each entry and fix them, so they are in the correct time order. Each older version of a detail table must have also an older time of creation.
If the check finds an older detail table version with a time of creation newer than some other, higher version of this table, the creation time of the older version is set 1-hour earlier before the creation of the newer version of this table.

Deleting BTC configuration

The check deletes obsolete BTC properties from all relevant database tables.

Update of system status

The check goes through all collector jobs and verifies, whether there is some job scheduled for a collector job. When the collector job is not running, the status of the affected system in the System status table is set to stop.

Correction of system definition

Checks the IP address of all monitored SAP systems with valid RFC destination. If the IP address doesn't match the standard pattern (4 blocks of max. three-digit numbers separated by a dot), it tries to derive some information from a satellite system by the RFC call and fix the entry in the System definition table.

Update of system type

Checks defined systems in the System definition table with an unspecified system type. The report considers all systems with an undefined type as SAP systems and fills in the SAP system type.

Update of the collector job status

Checks the status of a collector job defined in the Collector job table and marks it as 'Running', 'Stopped' or 'Paused'.

KPI definition update

The check fills columns 'chart lower limit mode' or 'chart upper limit mode' in the KPI definition table. If the 'chart lower limit mode' or 'chart upper limit mode' are not specified, the value in the corresponding column will be set to 'AUTO' (Limit will be calculated from min/max values). Also, the KPI chart type is checked. When the chart type isn't defined for a KPI, the chart type is set to 'LINE' as default.

Update alert definitions for a KPI

The check fills information about a KPI assigned to an alert defined in the Alert definition table. All redundant alerts with unassigned KPIs are deleted.

Update an empty Monitoring area

In the case the system type is not specified, the check fills a system type for each KPI defined in the KPI definition table. If the technical name of a KPI starts with 'Z', 'Y' or 'X', the system type is set to 'CUST', otherwise it is set to 'OLD'.

Check of multiple KPIs assigned to one alert

One alert must be defined only for one KPI. In the case one alert is defined for multiple KPIs, the check finds this alert and creates copies of it, and assigns the newly created alerts to KPIs which were originally not correctly assigned to the one alert. The name of the newly created alert is created as prefix 'X' + name of the original alert + '_order number of the erroneous KPI'.

XPRA upgrade check execution

Go to the transaction SE38 and execute the report /DVD/MON_UPGRADE_CHECKS.

The Test mode (first checkbox) doesn't perform any DB changes.

Output

Based on the option selected in the section Logs, you can display written or logged output.

If you execute the report while importing a transport to a system, we recommend using the write option.

_{Write output (marked checkbox)}

_{Log output (empty checkbox)}

Output from this check is available right after the report execution or in SLG1 after selecting:

Object: /dvd/mon

Subobject: /dvd/mon_checks

External ID: name of the check (can be empty to display all checks)

Double-click on the log to display further information.

Browser not supported