Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert
Focused Insights now lets you create reusable catalogs of metrics which can be consumed from the Service Level Reporting Dashboard and Strategic Dashboard. The content of the catalogs is built with the OCC Dashboard.

The Service Manager can use the content of the catalog to create the Service Level Reports. It no longer needs to worry about all technical details required to build a metrics (OCC query). Instead, it can rely on user-friendly naming for the metrics (for example "Average ABAP Dialog Response Time in milliseconds" or "Average ABAP System Availability in percent") and focused on the important aspects of the report like the SLAs and the time periods.

Build a Catalog

A catalog instance is built with OCC Dashboard, it corresponds to one OCC Dashboard Instance.

There isn't any restriction to build your catalog instance, you can benefit from all capabilities of OCC Dashboard. The gadget in this context becomes a way to structure your catalog, like a folder.

Once the catalog is ready, you need to publish it so that it becomes visible from SLR dashboard. To do this, simple check the "Discoverable" box.

The "Final" checkbox is not required to publish your catalog; this flag makes your dashboard no longer editable and indicates that this instance should be treated with care.

Consume a catalog from SLR

The Catalog is  attached to the user's personalisation menu.

In the SLR dashboard, published catalog instances are accessible from the right side of the screen when you are in edit mode.

Here you'll find the complete structure of your catalog instance, with the name of the OCC dashboard instance at the root level, the gadgets at the first level, then the metrics at second level.

You can select one or more metrics in a catalog and press "Add metric(s) selected" to add them in your SLR dashboard.

You have the option to edit the added metrics immediately or to return later edit them one by one using the edit button of the metric tile (little pen).

To easily identify the added metrics, the dashboard keeps the existing metric tiles collapsed and expand the tiles corresponding to added metrics.

If you decide to edit the added metrics immediately, an editable table is displayed with the following information:

  • Name of the metric corresponding to the legend of the OCC query

  • Chart type for detail view, by default it's always "Line Chart"

  • Type of SLA retrieved from  property "SLA" of OCC query; by default, the value is "Average"

  • Unit which is an optional free text displayed in the SLR dashboard

  • Target, the value of the SLA for the metric. It is retrieved from property "Y2R" of the OCC query and has no default value

  • Type of SLA target. It is a "Maximum" (such as a response time) or a "Minimum" (such as an average percentage of availability). It is retrieved from property "Trend" of OCC query and by default has the value "Maximum"

  • Group is an optional parameter for the metric in the SLR

The following properties are not configurable from the table, for those, you need to open the metric configuration pop-up window accessible from the metric tile:

  • Period and resolution

  • Metric's parameter when relevant (see after)


  • It is no longer possible to create a metric from scratch in the SLR dashboard; only catalog metrics can be added.

  • The metrics are copied from the catalog into SLR dashboard. No reference is kept between the catalog and the dashboard. Therefor if you update the metric in the catalog it won't be updated in the SLR dashboard, you must delete the metric from the dashboard and add it again to get the changes.

Metric parameter

In some cases, the metric is provided with a parameter you can modify in the SLR dashboard. It depends on the data provider used by the OCC metric:

  • System monitoring metrics (DP_SYSMON) for which you can change the system id

  • Transaction metrics (DP_TRANSACTION) for which you can change the system id

With parameters, you don't need to create a catalog instance that contains all the variances of a metric. You can create a template metric like "Maximum number of ABAP Dialog Users" or "Average response time of transaction VA01" and adapt the parameter (system) in the SLR dashboard itself.

The metric parameter might not be editable from the mass configuration table described above. To change the parameter of a metric, you must open the metric edit pop-up window accessible from the edit/pen button on the metric tile. It can also be the opportunity to change the title of the metric to include the parameter (system).

Period and resolution

Three periods are available for automatic report generation:

  • Last Month : a new report instance is created every first Monday of the month

  • Last Week : a new report instance is created every Monday

  • Yesterday : a new report instance is created daily except for the days marked not relevant for data collection (see property "Not schedule collection day")

At creation time, when a metric is added to the SLR dashboard, it is set to "Auto" period, which means that the metric uses the same period as the report itself. At creation time, the resolution of the metric is configured with the resolution found in the catalog (that is, the resolution of the gadget containing the metric in the catalog).

When relevant, it is also possible later to change the metric period and the resolution from the metric configuration pop-up window. For example, you could have a daily report (report period is "Yesterday") with a metric "Last 7 Days/Hour".


  • In order to get the automatic report generation, make sure the metric instance is configured correctly (the "Define schedule collection" property is set to true) and that the daily SLR job runs correctly (/STDF/SLR_REPORT_AUTO_JOB).


The Service Level Reporting Catalog is available from ST-OST 200 SP4 for SAP Solution Manager 7.2 SP9.

You can also get it with ST-OST 200 SP3 for SAP Solution Manager 7.2 SP8, if you implement the wave 4.4 and the SAP note 2765146