Upgrading and Migrating SAP Smart Business Entities

KPIs modelled using versions of the SAP Smart Business KPI modeler released between Q4/2013 and Q3/2014 should be migrated from the old SAP Smart Business KPI modeler to the new SAP Smart Business modeler apps version.

Delta List

The following list describes the differences between the old and the new frameworks that are relevant for migration:

Variant
The evaluation and the variant are merged into a single object (the evaluation). The migration tool makes this change automatically.
Percent
If you have a percentage based KPI, you must do the following:
- Use the scaling factor Percent in the evaluation
- Add an extra measure in your SAP HANA Live views that provides the percent value as a fraction of 1 and not as a fraction of 100 (for example, this can be a calculated measure).
Trend
The trend has been simplified. Previously, to establish a trend you had to define two evaluations (one for the current value and another for an earlier time period).

You can now use one evaluation (and one request to the backend) to retrieve the current value in one measure and the value that the trend is derived from in a separate measure (for example, a measure that provides the current value as of two weeks ago). This means that you must later extend your SAP HANA Live views by this measure. We recommend that you add an input parameter that provides the timeframe in your query.
Unit of Measure
You can no longer specify or overwrite the unit of measure (UoM) in the KPI Modeler. Instead, the SAP HANA Live view should expose the UoM.
Decimals
You can no longer specify the decimal in the modeler. Instead, this is provided in the OData service. For decimals that are not currency-based but UoM-based, you can provide the number of decimals directly in the SAP HANA Live view. For currency-based apps, the backend automatically generates results with the default number of decimals for that currency (if it is configured correctly).
App to App Navigation
The URL schema has changed. Custom apps now must deal with a chip (tile) ID and the evaluation ID instead of the KPI ID and the variant ID as was previously the case.
Navigating from Drill-Down Application for KPI 1 to Drill-Down Application for KPI 2
This feature has been replaced by the feature that lets you add associated KPIs to the drill-down application and click them to navigate to them.

Prerequisites

You have installed both the old version and the new version of the modeler in the same system before starting the migration process. The Migration Tool assumes that both the old tables and the new tables are available in the same backend system.

Note You should migrate all content at once and not use the old and the new framework at the same time other than during the migration itself. If you have built custom apps that integrate with the SAP Smart Business framework we recommend adjusting the custom apps such that they support the new framework and then switch over productive use only to the new version of your custom app.

Upgrade and Migration Process

Launch the Migration Tool app and select the KPIs that you want to migrate. A message lets you know if some or all of the KPIs are already migrated. If you choose to migrate again, forced migration occurs.
If the KPIs contain evaluations and drill-downs, the details are displayed.
Adjust the IDs generated for the new evaluations. The Migration Tool app proposes a new ID for each evaluation. You must adjust this proposal to suit your requirements. We recommend the following naming convention: KPI_ID.shortEvaluationID (for example, sap.hba.ecc.ProjectCompletion.ProjectPercentageofCompletion).
Adjust the IDs generated for the new drill-downs. Under IDs after Migration, click Configured Drill-Down and edit the ID in the dialog box. Click Save and Close.
Choose Migrate to start the migration process.
Create new tiles using the Configure KPI Tiles app. The tile visualizations associated with the KPI are not migrated. As a result, you must create and activate new tile visualizations using the Configure KPI Tiles app after you migrate a KPI.

Note You can repeat the migration, however this overrides the already migrated content.

Migrating Custom Apps that Interface with SAP Smart Business Apps and Tiles

To migrate your custom app so that it works with the new SAP Smart Business KPI tile and drill-down, your custom app must react to different parameters in the URL provided by the KPI tile. Previously, the KPI ID and the variant ID were required; now, a newly generated chip ID that refers to the metadata in the KPI tile is required along with the evaluation ID (and optionally the view ID). When navigating to another app, you must provide the chip ID that refers to the KPI tile and the evaluation ID. When being called, you can use the services offered by the SAP Smart Business repository to retrieve metadata for the evaluation based on its ID.

Post Upgrade and Migration Steps

When migration is complete, you can use the KPI Workspace app to search for the migrated KPIs and their associated entities. Bring up the KPI, evaluation, and drill-down and check that all field values are correct.
Note The new SAP Smart Business application deals with percentage values differently, for this reason you must add a measure to your calculation view that divides your original value by 100.
If you have custom navigation options, re-establish them for the new tile and drill-down and check that they function as before.
If you had built a custom drill-down app, re-build the drill-down app based on the new architecture.
Check which of the new configuration options in the KPI (related KPIs, backend target, and thresholds), evaluation (filters optional), tile, and drill-down configuration benefit your use case and adjust them accordingly.
If you have migrated all of the KPIs, users cannot access the old KPIs and you should delete the following roles:
- PFCG role SAP_KPI_FRW_TCR_S and SAP_KPI_FRW4_TCR_S
- The role in SAP HANA is sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_RUNTIME
Retest the entities.