Show TOC

Function documentationUsing the BW Mapping Tables Analysis Program


E2E Monitoring and Alerting Infrastructure (MAI) Reporting, which is used in Interactive Reporting, has a mapping mechanism. The metrics are saved in the SAP Solution Manager Business Warehouse, the data is provided by the MAI Data Provider Connector (see Getting MAI Data for Interactive Reporting). The mapping mechanism is integrated Into this data capture. It adjusts the data structures as they are used in MAI, to the BW data structures, because they can differ, for historical reasons.

The mapping is for the following reasons:

  • The name of a metric in BW should be independent of the technical collection infrastructure if it has the same semantic meaning. There are metrics in MAI which were already collected in CCMS, but have different technical names in the two infrastructures. To ensure data continuity, the MAI names of these metrics are mapped onto the old CCMS names when they are saved in BW.

  • If there is no data for a metric for a long time, the mapping mechanism creates gap data records for this period, for display in reporting.

  • Host metrics are copied to the data records of the systems which run on this host.

  • The availability, taking account of downtimes, is calculated.

  • Data targets in BW, the BW objects in which the data is written, are specified.

This data is written in mapping tables. Until SP11 of SAP Solution Manager 7.1, this is the table E2EREP_MAPPING.

This mapping mechanism has been optimized for SP12 of SAP Solution Manager 7.1, to improve performance and reduce database load. The original table E2EREP_MAPPING is now only used for metric master data. There are two additional tables:


    This table contains the current period of uninterrupted data provision for each metric.


    This table contains the metric data provision period history. If the data provision for a metric is interrupted, an entry from the table E2EREP_MAPP_CURR is copied into this table, and an interruption counter in the table E2EREP_MAPP_CURR is incremented.

They contain the following columns:

Technical Field Name



Hash value calculated from the metric master data.


HCI is the Hash Collision Index. A hash collision is when the hash values of two metrics are the same. The value is incremented by one, and there are two HCIs for one hash value. This only occurs in extremely improbable situations, so the index value is nearly always 1.


Start timestamp of the interval of uninterrupted data provision of the metric


End timestamp of the interval of uninterrupted data provision of the metric If the metric is only measured once, LOAD_FROM = LOAD_TO for the interval.


Metric data source. There are currently two possibilities:

  • DPC (Data Provider Connector) – the metric comes from the E2E Monitoring and Alerting Infrastructure.

  • CCM – the metric comes from the CCMS infrastructure.



Number of gaps in the metric.

Note Note

This value is never reset, so it contains the number of gaps since the metric was first read. It does not necessarily indicate current problems with the metric.

End of the note.



Gap index.

When there is a gap in the data provision of the metric, the uninterrupted data provision interval of the metric is closed and moved from E2EREP_MAPP_CURR to E2EREP_MAPP_HIST, and the gap index is incremented. After reorganization of the table, the indexes IND are ususally no longer available.

All mapping tables are reorganizied regularly, obsolete entries are deleted. This is done weekly by the job E2EREP_MAPPING_CLEANUP.

This analysis tool was created during optimization of the mapping mechanismus, to output mapping table data. This was necessary because the optimization distributed the data among several tables, so it is no longer convenient to check them with transaction SE16. It is for experts who need information about the mapping and those metrics with frequent data provision interruptions or other technical problems.


Call Program

To display the contents of the metric tables, call the transaction MAI_TOOLS. Go to expert mode, and, in the Analysis tab, choose Analyze BW Mapping Tables.

Display information

When you call the program, a selection screen, in which you can make the following entries, appears:

Report selection

In the group box Report Selection select the information to display. These are the following radio buttons:

  • Data Source Analysis E2EREP_MAPPING and E2EREP_MAPP_CURR, all entries which contain uninterrupted data for all metrics in the current interval:

    • Number of Entries in MAPP_CURR

    • Display Entries in MAPP_CURR

    • Entries with HCI>1 in MAPP_CURR

      HCI is the Hash Collision Index (see above).

  • Data Source Analysis E2EREP_MAPPING and E2EREP_MAPP_HIST, all entries which contain uninterrupted data for all metrics in previous intervals: These are interval after which data provision was interrupted and restarted at least once.

    • Number of Entries in MAPP_HIST

    • Display Entries in MAPP_HIST

    • Top X Metrics by Gaps

      This radio button determines which metrics in your BW data have the most gaps, i.e. whose data collection is unreliable.

    • Top X Systems by Gaps

      This radio button determines which systems in your BW data have the most gaps, i.e. whose data collection is unreliable.

    • Metrics with the Most DB Space

  • Data source analysis by E2EREP_MAPPING, E2EREP_HIST and E2EREP_MAPP_CURR, all entries of all metrics in the mapping tables. This option searches for metrics which have only been read once, or seldom.

    • Metrics which were only written once

      This option finds metrics which were measured once and never again. Such metrics are usually the result of an incorrect implementation, and can considerably increase the size of the mapping tables. This can happen if the metric path contains a GUID or timestamp.

    • Unique Metrics with Gaps

      This option finds flickering metrics, i.e. metrics for which there is a gap after every measurement. This occurs, for example, if the measurement frequency and data collection do not match, because of incorrect configuration.

Note Note

When you display the contents of E2EREP_MAPP_CURR or E2EREP_MAPP_HIST, the associated master data in the table E2EREP_MAPPING is also output; you can specify which in a Filter (see below).

End of the note.

Show additional data

You can also set flags to show the following further information for the metrics:

  • Show Mapping Rule

    A mapping rule is technically a BAdI implementation which performs the mapping. This is in the table ACMEACONSUMERDIR, not in the table named above.

  • Display Maximum Number of Gaps (Display in the table, in the Max. IND column)

    Set this flag to display the number of gaps for the metric. This value is never reset (see above).

In the Report Selection and Filter, choose which entries (metrics) in the mapping tables are to be output. In the Max. no. of Data Records/Top X field, you specify how many entries at most are to be output.


You can further restrict the data output in the Filter group box.

Make the required entries, and choose (Execute). The specified entries are output in the table displayed.