Show TOC

Background documentationTroubleshooting Tools Locate this document in the navigation structure

 

Note Note

This section is part of the technical documentation of the E2E Monitoring and Alerting Infrastructure reporting scenario (Interactive Reporting).

End of the note.

There are various tools available to check the data provision and processing for the E2E Monitoring and Alerting Infrastructure (MAI) reporting scenario.

Problem Message Display Report

You can display the problem messages from the following areas of MAI data reporting:

  • Data Loader (writing the data into BW data store objects)

  • Mapping (Adjusting Data Structures to Save in BW)

  • Further processing in BW (write DSO data into InfoCubes)

You can run the two following reports in transaction SE38

  • SMREP_PN_SHOW_MESSAGES

  • SMBI_PN_SHOW_MESSAGES

If there are problems in interactive reporting, you can check them with these reports.

Note Note

These messages are also in the self-check messages which are shown in the Self-Monitoring of BW-Based Reporting.

End of the note.

The differences between the two reports are largely historical. When saving and processing reporting data in BW, steps are performed in the software components ST (SAP Solution Manager) and ST_BCO (BI Content for SAP Solution Manager). Depend on whether your BW is in its own system or in the SAP Solution Manager system, as recommended, these steps run in one or two systems, so there are two message display reports.

Use SMREP_PN_SHOW_MESSAGES to display the messages from the SAP Solution Manager system, and SMBI_PN_SHOW_MESSAGES to display the messages from and in the associated BW system. All messages of both software components are displayed in both reports by default. The BW or SOLMAN flag is set in the reports by default.

Note Note

You can also call both reports from the SAP Solution Manager system, with the Monitoring and Alerting Infrastructure analysis tools. Proceed as follows:

  1. Call the transaction MAI_TOOLS.

  2. In the Logs and Traces tab, choose Problem Messages in SolMan or Problem Messages in BW.

End of the note.

You can restrict the problem messages to be displayed, to a date range (DAT_FROM to DAT_TO), in both reports.

The problem messages in the specified date range are displayed, with the following data:

Column Title

Meaning

PROBLEM_ID

Technical ID of problem message. If you cannot resolve the problem from its description, search for notes with this ID, to get SAP troubleshooting information. If there is no appropriate note, report an incident in the component SV-SMG-MON-REP.

DESCRIPTION

Short problem description

PROGRAM_OCCUR

Methods, programs, function modules or form routines in which the problem occurred.

TIME_LAST_OCCUR

Timestamp of last occurrence of problem

COUNT_TOTAL

Number of times the problem has occurred

COUNT_24H

COUNT_7D

COUNT_30D

Number of times the problem has occurred in the last 24 hours (COUNT_24H), last 7 days (COUNT_7D) and the last 30 days (COUNT_30D)

COUNT_CONF

How often you have already confirmed the problem in the BW-Based Reporting Self-Monitoring

If no problem messages are listed, interactive reporting usually works, so if problems still occur, they are probably in the monitoring data determination by DPC (see Getting MAI Data for Interactive Reporting).

Analyzing the Mapping Tables

Interactive Reporting has a mapping mechanism. It adjusts the data structures as they are used in MAI, to the BW data structures, because they can differ. Data saved in BW must be mapped, even if the metric names match. The mapping tables tell you which reporting data was sent to BW when.

For more information, see Using the Mapping Tabe Analysis Program.

Using MAI Trace Functions

MAI contains comprehensive trace functions, which show the details of the MAI processes. Using the MAI Trace Functions describes the use of the trace.

Note Note

As the trace can greatly reduce the performance of MAI, depending on the filter settings, only use the tool in consultation with SAP Support.

End of the note.

The mapping is in the reporting trace functions. There are two trace contexts:

  • DPC2BI_MAPPING (activates the general MAI trace for the mapping)

  • DPC2BI_MAPPING_ERROR (only activates the trace for occurring errors)

To activate the trace, proceed as follows:

  1. Start the transaction ngtrace, to display the trace.

  2. If you activate the trace context DPC2BI_MAPPING, specify trace filters to limit the additional system load. Choose Trace Filters (Trace Filters), go to change mode, and specify the filter values. There are the three following filters for the context DPC2BI_MAPPING:

    Name Trace Filter

    Meaning

    CONTEXT_ID

    GUID of the managed object in MAI

    BI_METRIC_TYPE

    technical name of the metric in BI (in the mapping table E2EREP_MAPPING, the entry SMD_METY)

    TRACE_SUBCONTEXT

    Subject areas for which the trace is to be written. This trace context has the following areas:

    • INPUT DATA Data passed to the mapping rule

    • PARAMETERS Further metric information (e.g. its path)

    • OUTPUT_DATA Data returned from the mapping rule

    • MAP_CURR_RECORD Processing the mapping: Mapping data record

    • DATA_RECORD Processing the mapping: Results of the mapping for BW

    Note Note

    You usually activate the trace when problems occur when mapping a metric type or the metrics of a managed object. Specify the trace filter.

    End of the note.

  3. To activate the trace, choose Trace Activation (Trace Activation), and, in the Checkpoint Group field, choose the trace context (DPC2BI_MAPPING or DPC2BI_MAPPING_ERROR).

  4. Choose Activate (Activate). You go to the Activate Checkpoint Group screen.

  5. In the Assertions group box, choose Log.

  6. Choose Users (Users), to specify the users to be traced.

  7. In the Activation by Users screen, enter the users to be traced. One important user is, for example, SM_EFWK. Also set Assert to Log for this user. Choose the Assert setting with the right-hand mouse key.

    Note Note

    Determine the users used by the mapping from the fact that the data loader SMD_DATA_LOADER_S is called by the same users by RFC (see Passing and Saving MAI Daten in Business Warehouse). Check which users call this function module. Proceed as follows:

    1. Start the transaction ST03 in the SAP Solution Manager system.

    2. Choose a time range in the navigation bar, under   System Load   Total  .

    3. Choose the Analyse View   RFC Profile   RFC Client Profile  

    4. Search for the function module SMD_DATA_LOADER_S, and double-click on a row. The users who have called this function module are listed.

    End of the note.

  8. Save your settings.

Other Tools

If the metric is not in reporting, or no longer exists (if there are no current entries in the mapping table), the problem may be in MAI. Use the MAI tools (see Monitoring and Alerting Infrastructure Tools).

You can also use the standard troubleshooting tools, for example:

  • ABAP Run-Time Errors (transaction st22)

  • Job Selection (transaction sm37)

    Check the following jobs in the Job Log:

    Job name

    Meaning

    Frequence

    E2EREP_MAPPING_CLEANUP

    Reorganizing the Mapping Tables

    weekly

    CCMS_CPH_RAW_DATA_UPDATE

    Writes the original data from DSO 0CCMBUFF into the InfoCubes

    hourly

    CCMS_CPH_AGGR_DATA_UPDATE

    Writes the aggregated data from DSO 0CCMAGGR into the InfoCubes

    daily