Show TOC

Function documentationTroubleshooting in the KPI Catalog

 

This section summarizes possible problems, their cause, and their resolution for the KPI catalog; it also contains technical information on the catalog's log and trace functions.

Features

Troubleshooting Using the Application Log

If errors or problems occur in your SAP Solution Manager system when calling the KPI catalog, you have log and trace functions available for troubleshooting. Both present important information in such a case, in particular for SAP support.

The KPI catalog uses the application log for its log messages; to display these messages, proceed as follows:

  1. Start the application log (transaction SLG1).

  2. Enter the value SMKPI_LOG as the object and have the log output for the desired period.

Troubleshooting Using Trace Functions

A trace function exists for the KPI catalog for further information.

Caution Caution

Before you activate a trace, note the following: Since the trace can have a negative effect on the performance of the KPI catalog and generates a large amount of data in trace files, only use the tool in collaboration with SAP support. Therefore, this documentation only describes the aspects of the trace that you need to activate the trace with SAP support, and store the corresponding data in a file to transfer this to SAP.

End of the caution.

To activate a trace, proceed as follows:

  1. Start transaction SAAB.

  2. In the Checkpoint Group group box, enter the name SMKPI_CAT_TRACE and choose the Activate (Activate) pushbutton.

  3. Switch to the Activation tab page, and in the Assertions group box, choose the Log radio button.

  4. Save your settings and specify the maximum amount of time for which the activation of the trace is to remain valid.

    Note Note

    To deactivate the trace immediately, choose the Inactive radio button in the Assertions group box.

    End of the note.

To display a trace or download a trace file, proceed as follows:

  1. Start the report SMKPI_TRACE_VIEWER in transaction SE38, restrict the trace file to be output to suit your requirements, and choose the Execute (Execute) pushbutton.

  2. The traces are displayed in a table. If an entry in the table is not displayed fully, or an additional XML file exists for this entry, double-click this row to display this entry.

  3. Choose the corresponding pushbutton to export the trace entries to a Microsoft Excel file.

Start the report SMKPI_TRACE_DELETE to delete trace entries that are no longer required.

Possible Errors, Their Cause and Their Resolution

Problem

Cause

Resolution

You call the KPI catalog in an application and the KPI catalog is displayed in the same way as for SAP Solution Manager without Internet access even though your SAP Solution Manager has access to the Internet.

To determine whether the cloud-based KPI catalog can be called, two checks are performed:

  • A ping to the URL of the KPI catalog is performed. If an issue arises during this, this is written to the application log.

  • It is checked whether the RFC connection to SAP Support Portal has been set up. This is done in the configuration of SAP Solution Manager (transaction SOLMAN_SETUP, step Start of the navigation path Overview Next navigation step System Preparation Next navigation step Set Up Connections to SAP Next navigation step RFC Connectivity End of the navigation path).

Only if neither of these two conditions are fulfilled is a local copy of the KPI catalog displayed.

Check the step mentioned in the configuration of SAP Solution Manager and use the network settings of your SAP Solution Manager system to check the Internet access.

If at least one of these conditions is fulfilled yet only a local copy of the KPI catalog is displayed, create a message under the component SV-SMG-CA-KPI.

You call the KPI catalog and the Usage tab in the detail view does not contain an SAP Solution Manager application for a KPI and you are certain that the application uses this KPI.

The usages of the KPI in your system landscape are transferred from your SAP Solution Manager system to the SAP Support Portal using the hub connectivity in a job scheduled every half hour. If an error occurs, the corresponding usage is transferred again the next time this job is run. Therefore, a possible error cause in addition to connection problems is that you have not configured the hub connectivity.

To configure the hub connectivity in the system of your SAP Solution Manager, start transaction SOLMAN_SETUP, and perform the step Start of the navigation path Overview Next navigation step System Preparation Next navigation step Set Up Connections to SAP Next navigation step Support Hub Connectivity End of the navigation path.

You call the KPI catalog from an application and choose a KPI there. However, this KPI is not returned to the calling application.

The synchronous connection to SAP is not set up properly, or does not work correctly.

To configure the synchronous connection to SAP in the system of your SAP Solution Manager, start transaction SOLMAN_SETUP, and perform all activities in the step Start of the navigation path Overview Next navigation step System Preparation Next navigation step Set Up Connections to SAP Next navigation step RFC Connectivity End of the navigation path.

You use the browser Google Chrome to call the KPI catalog and receive the following error message:

HTTP Status 500 - An internal application error occurred

The browser does not accept any cookies from the domain hana.ondemand.com, in which the KPI catalog is located.

Change the Google Chrome settings such that the browser accepts cookies from the domain hana.ondemand.com. To do so, choose Start of the navigation path Settings Next navigation step Display Advance Settings Next navigation step Data Protection Next navigation step Content Settings Next navigation step Manage Exceptions End of the navigation path, and allow cookies from the domain hana.ondemand.com.