How-to

Using BP Analytics and BPO Dashboards after upgrading the Solution Manager

Please mind doing the post-upgrade steps as described in the following SAP-notes:

2140497 - BPImp: Recom. for upgrading from ST710 SP01-SP04 to ST710 SP05-SP11
2131954 - BPImp: Recom. for upgrading from ST710 SP5-SP11 to ST710 SP12-SP13

Authorizations for Using BP Analytics and BPO Dashboards

There are usually at least two kinds of user types for Business Process Analytics and Business Process Dashboards:

1) Business Process Analytics and Business Process Dashboards Administration: Allows to setup, and configure Business Process Analytics and Business Process Dashboards, allows to view Dashboards and key figures within Business Process Analytics, allows to execute certain admin functions as e.g. loading Master data or maintaining the connector repository.

2) Business Process  Analytics and Business Process Dashboards user: Is allowed to view Business Process Dashboards and analyze key figures within BP Analytics. There might be different kinds of Business Process Analytics and Business Process Dashboards users, which are e.g. allowed to only see certain key figures or key figure variant in Business Process Analytics and only certain dashboards in Business Process  Dashboards.

Rebuild the AKF repository for one key figure

In case of the appearance of inconsistencies for one single key figure, it is recommended to delete the AKF Repository only for this specific key figure.

To do that, go to transaction s38 and execute the report AGS_BPM_RI_CREATE_GAKF.

1) If you are on ST 710 SP09 or higher:

Select “Delete GAKF (only)”. The technical name of a key figure needs to be filled in the parameter “Technical Name of AKF” / “P_AKF”. After selecting “Execute” all entries for this key figure are deleted from the AKF Repository.

Afterwards select “Rebuild of GAKF (only)” to rebuild the AKF Repository for this one key figure.

2) If you are on ST 710 SP05 to SP08:

Set the parameters P_DELETE and P_DELRET to “X”. The technical name of a key figure needs to be filled in the parameter “Technical Name of AKF” / “P_AKF”. After selecting “Execute” all entries for this key figure are deleted from the AKF Repository.

Afterwards set both parameters to “ “ to rebuild the AKF Repository for this one key figure.

Rebuild the AKF repository for ALL key figures

In case of inconsistencies in multiple key figures, it is recommended to delete the whole AKF Repository.

To do that, go to the transaction s38 and execute report AGS_BPM_RI_CREATE_GAKF.

1) If you are on ST 710 SP09 or higher:

Select “Delete GAKF (only)”. After selecting “execute” the whole AKF Repository will be deleted.

Afterwards select “Rebuild of GAKF (only)” to rebuild the whole AKF Repository and execute.

2) If you are on ST 710 SP05 to SP08:

Set the parameters P_DELETE and P_DELRET to “X”. After selecting “execute” the whole AKF Repository will be deleted.

Afterwards set both parameters to “ “ to rebuild the whole AKF Repository and execute.

Activation of the BP Analytics TwinCubes

Please check chapter “Find out which Analytics cubes you are using” to make sure you are not already on the Business Process Analytics TwinCubes.

Switching from the Business Process Analytics Infocube to the Business Process Analytics TwinCubes provides the following benefits:

1. Better performance of Business Process Analytics / Business Process Dashboards
2. Value Benchmarking and Value Trend Analysis  in Business Process Analytics
3. Automatic housekeeping of the Business Process Analytics TwinCubes
4. Simplified Master Data load for Business Process Analytics and Business Process Dashboards

Using the TwinCubes is optional from SP12 on.

To use the TwinCubes, an activation plus optional migration of old data / dashboards (AKFIs) is required. This is a onetime decision with no way back: As soon as the TwinCubes are activated, there is no way back to the BP Analytics InfoCube.

Activating the TwinCubes:

1. On your solution manager system go to transaction SOLMAN_WORKCENTER
2. Go to tab “Business Process Operations”
3. On SAP Solution Manager 710 SP12 to SP14 use link “Maintain Business Process Reporting Infrastructure” and there tab “BP Analytics BW”
1. First you should check whether your user has enough authorizations to perform the activation. If the checks for “BW Connections Status (RFC Dest.)” and “BW User Status (User ID)” are green, the authorizations are sufficient. If they are red, you can check via “Display Details” which authorizations are missing.
2. In the next step you can activate the TwinCubes. If the activation fails you can check via the Job Log what went wrong.
3. If you have been using Business Process Analytics before, you can migrate old data from the Business Process Analytics Infocube to the new BP Analytics TwinCubes. Please mind that the migration can take a few hours depending on the amount of data in your Business Process Analytics InfoCube.
4.  If you have been using Business Process Dashboards based on data from BP Analytics you need to migrate the AKFI Directory. Afterwards the Dashboards can be used as before the migration.

Find out which analytics cubes you are using

To find out whether you are using the Business Process Analytics Infocube or the Business Process Analytics TwinCubes, please check the following:

1)    Which SAP Solution Manager Release are you on?

1. If you are on ST 710 SP5 to SP11 you are using the BP Analytics Infocube
2. If you are on ST 710 SP12 or higher:

                                          i.    Go to transaction SE16 on your solution manager system

                                         ii.    Enter table AGS_RI_BPA_CUST and view the content

                                        iii.    If the following entry exists, you are using the BP Analytics TwinCubes:

If the entry does not exist, the TwinCubes was not yet activated and you are using the Business Process Analytics Infocube

Please check the chapter “Activation of the BP Analytics TwinCubes” for further information.

How to debug a MAI collector

At first get the following information: MAI object ID of the monitoring object you want to debug. You get it from the technical information of the BPMon setup.

Then start the transaction MAI_TOOLS in the solman system.

At first choose the functionality Alerting Directory Browser (we need this to get an additional technical information, the metric ID).

A new window will open:

In the field ‘Navigation by’ choose the entry ‘Managed Object with Hierarchy’ from the F4-Help.

Then enter in the field Managed object ID the value of the MAI object ID you are interested in.

After pressing apply additional information about the object is shown. Mark the line with the object and additional info is shown in the right side of the window.

Mark the line of the object you are interested in:

A new window will open with a section called 'Details for Metric Type: …..'

Click on the tab named ‘Others’: Then you will see the value for the Metric ID.

Copy the values for the metric ID and the Managed Object ID and go back to the transaction MAI_TOOLS.

Back to transaction MAI_TOOLS choose the tool: Data Provider Check for PULL_RFC Metrics:

Here you have to enter the values for Metric ID and managed object ID.

Access the Analytics BW InfoCube

Display data via transaction LISTCUBE

• Open SAP GUI of the system where your Solution Manager BW is located. In general this is the SAP Solution Manager itself.
• Enter transaction LISTCUBE
• As InfoProvider please enter 0SM_BPMRH. This is the name of the InfoCube for Business Process Analytics.
• Press F8 (execute) and submit the info message.
• In the upcoming screen you have to select a set of InfoObjects. Choose: “Select Characteristics”
• Submit your selection
• Now you’re seeing the selection screen where you can enter selection criteria for the BW InfoCube query. Before you execute a query you have to select which fields have to be displayed in the result table.
  • Press “Fld Selectn for Output”
  • Now, press “Select all”
  • Press F8 (execute). You’ll come back to the selection screen.
• Here you can enter your selection criteria. I’ll give you some examples:
  • Sol.Monitoring ID: Enter a solution to see just cube entry's for this solution
  • Key Figure: Enter the technical key figure name e.g. KPSD000201 (Sales invoices not posted to FI) to see just data for this key figure
  • Monitoring ID: Enter a Monitoring ID to see the key figure results for that the Monitoring ID is collecting data
  • System ID: Enter a system ID e.g. QPT to see if there exist data for a specific system
  • Calendar Day/Month/Year: Enter a specific timeframe to see the data that was collected within this time
  • Max. no. of hits: If you’re expect a huge number of entries in the result list, then enter a higher value e.g. 100.000
  • For all fields is a F4 help available, where you can see which different values are stored in the cube
• After you entered the selection criteria press F8 (execute), dependent on your query it can take a while (several minutes) until you can see the result list
• You’ll now see a huge list. The strangest fields for you could be the field “Generic Parameter” 1 – 20. These are the group by characteristics of a key figure. We called these characteristics in the cube generic parameter because it depends on the key figure if the characteristic is a Sales Organization, a Plant or a Company Code. The cryptically strings that are stored in these fields is a hash key. In another InfoObject of your BW you can read which characteristic and description is belonging to this hash key.
• At the end of each line you’ll see the measured value belonging to exactly this distinct combination of characteristic values. To understand that I give you an example how the data is aggregated in the cube:
  • After the data collection, the data collector of a key figure is storing the result as a detail list on the managed system:
    
    
  • This detail list will afterwards be aggregated and stored in the cube in the following format:
    
    
• Now you can analyze the data in the cube with some nice practices. If you enable the flag “Use DB aggregation” in the selection screen, the output won’t display double entries. I give you an example how you can use it:
  • If you want to know in which backend systems data for key figure “Sales invoices not posted to FI” was collected, then press at first “Fld Selectn for Output” and ensure that you just check the field “System ID”, all other fields have to be disabled.
  • Go back to the selection screen and enter KPSD000201 for “Key Figure” and press F8 (execute query)
  • Now the result list could show like this: 
    
  • So you can imagine that with the help of transaction LISTCUBE you can analyze several things: Which Monitoring IDs are collecting data for a specific key figure?, Which key figure(s) have been set up for a specific Monitoring ID?, Which solutions had collected data in the month December 2012?, etc.

Troubleshooting Guide

Business Process Analytics

KBA's

Business Process Analytics is “empty”

1) Please make sure that your user in the SAP Solution Manager has either the role SAP_SM_BPOANA_ALL, SAP_SM_BPOANA_DISP, a copy of any of these roles or a custom created role with the authorization objects of this role assigned.

2) Please also ensure that also the corresponding role profile is assigned to your user.

3) In case the profile is not assigned to your user, please check whether the roles have been already generated.

 “No authorizations” exception when Calling Business Process Analytics

1) Please make sure that your user on the SAP Solution Manager has one of the following roles SAP_SM_BPOANA_ALL, SAP_SM_BPOANA_DISP, or a copy of one of these role or a custom createed role with the authorization objects of this role assigned.

2) Please also ensure that the corresponding role profile is assigned to your user.

3) In case the profile is not assigned to your user, please check whether the roles have been already actively generated.

“No data” exception when calling Business Process Analytics  

1) Please check whether monitoring objects were setup for Business Process Analytics in the Business Process Monitoring Setup in the Analytics Library of your solution and not in the Alerting Library.

2) Please carefully check the authorizations of your user (e.g. authorization trace in transaction ST01 or last status of authorization checks carried out SU53). Maybe you are lacking authorizations to see data in Business Process Analytics.

3) Check if the ST-A/PI or ST of the system was upgraded recently. If yes, remember to perform the post-upgrade steps for BPImp

4) Is the Twin Cube connector in the connector repository defined? Create the TwinCube connector in the connector repository

5) If the previous steps did not solve the issue, continue checking the steps suggested below “BP Analytics: Monitoring object / key figure does not show up in BP Analytics”

No free selection in BP Analytics possible

1) Please check whether your user has the role SAP_SM_BPOANA_ALL or the role SAP_SM_BPOANA_DISP assigned.

2) In case the user has the role SAP_SM_BPOANA_DISP assigned; the user has only Business Process Analytics end user rights. Business Process Analytics end users is usually not able to see the free selection.

3) In case you have SAP_SM_BPOANA_ALL assigned, the role needs to be enhanced as follows: The authorization Object SM_BPM_ANA-ANALYTFUNC needs to be enhanced by the value FREE_SELECTION.

Monitoring object / key figure does not show up in BP Analytics

1) In the solution manager: Check your monitoring object / key figure in the „Business Process Operations Setup“ (in the solman_workcenter, tab Business Process Operations):

1. Did you setup the monitoring object in the logical component (and not under the Business Process Step)?
2. Did you check at least one group by field for your key figure?
3. Was the time scheduled configured in a way that the monitoring object would have already been collected by now (also check the solution manager system time, it might be different from your local time)?
4. Did you save, generate and activate your key figure?

=> If you answer at least one of these questions with NO, adjust the setup, generate then deactivate & activate the monitoring object again. Now you don't have to wait until the data collection is triggered again.

2) In the managed system: Check your monitoring object / key figure in transaction ST13 report tbi_reports: Does the setup result in a data collection with more than 0 values found?

=> If no data collection comes back, carefully check the setup: Does it make sense, are there maybe spelling mistakes or wrong parameter filters? Adjust the setup, generate then deactivate & activate the monitoring object again and wait until the data collection was triggered again.

3) On the Solution Manager: Check table DSWP_BPM_TIMESCH. (Filter the table on the monitoring ID of your monitoring object). Was data collection for your key figure already triggered today? (is  the NEXTDATE / NEXTTIME in the future)

=> If the data collection for your monitor was not triggered yet, even it should have been triggered more than 30 minutes ago, check:

• Is the READ RFC to the managed system working?
• Is the framework maybe still waiting for the response of another monitoring object, which was setup in dialog, but was the data collection is taking very long?
• Check transaction RZ12: Is the logon group “parallel_generators” maintained completely and active

4) On the managed system: Check in transaction SE38, Report /SSF/PTABBROWSER. Was a detail list for your monitor created?

	Relid = TC

	Projectid = <Project of your monitor / key figure>

	Objkey = DI*<Monitoring ID (cut zeros at beginning and end)>*

• Maybe there was no data found on the managed system for the last collector run of your monitoring object. Check on the managed system in transaction ST13 that there would have been data collected with the last collector run of your monitoring object.
• Else try to deactivated and activated your monitoring object again (on the Solution Manager in the “Business Process  Operations Setup”). Check whether the next data collection is successful.
• The key figure might contain an error in its customizing. Check whether there is already a correction for the customizing available for this specific key figure (all customizing corrections are listed in note 1848622).
• Else the key figure collector coding might contain a mistake so that no data is collected (very rare for standard TBIs). Debug the data collection of the key figure.

5) On the managed system: Check in transaction SE38, Report /SSF/PTABBROWSER: Can you still see the aggregated packages (BW_PACK*/ BW_PROT) in the managed system?

	Relid = TC

	Projectid = IEF

	Objkey = BW_PACK*<technical name of the monitor><number of the key figure>* or BW_PROT*<technical name of the monitor><number of the key	figure>*

In general the extractor framework can take some minutes until it picks up packages from the managed system. In case the packages are already overdue for pickup for more than 30min, check the following:

• Check whether there are a lot of BW packages lying in the PTAB which were not yet picked up: maybe the extractor framework is not able to handle the load of so many packages at once.
• Check the content of the BW:PROT entries: Are the  Instno. and the SID correct?
• On solution manager check table  E2E_EFWK_STATUS (with F81* / SID = your managed system): maybe the extractor run into an erroneous status.

6) On the SAP Solution Manager: Check which Analytics Cube is active. Then go to transaction LISTCUBE: if you are using the Analytics Infocube enter MultiProvider = 0SM_BPAMA:

Select execute. A popup might come up, asking which Characteristics to display. Click “Select Characteristics” and then Ok.

On the next screen put the Monitoring ID of your Monitoring Object into the field “Monitoring ID”. Then select “Fld Selectn for Output” and choose “Select all”. Click execute, on the next screen click execute again.

If the Cube does not contain data for your monitoring object:

=> The key figure might contain an error in it’s customizing. Check whether there is a correction note available for the key figure for your ST-A/PI support package à all customizing corrections are listed in SAPNote 1848622.

7) Rebuild the AKF repository for the missing key figure

Graphical troubleshooting guide:

Dump when calling a monitoring object / key figure in BP Analytics“ 

1)    Rebuild the AKF repository for one key figure (if the exceptions is only happening for one key figure) or for all key figures (if the exceptions happens for all key figures)

2)    Check in note 1759233 whether all correction notes for the ST-A/PI on the managed system were implemented in the newest version

3)    Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure whether a dump occurs

"An exception occurred during getting data." Exception when calling a specific monitoring object / key figure in BP Analytics

1) Rebuild the AKF repository for one key figure (if the exceptions is only happening for one key figure) or for all key figures (if the exceptions happens for all key figures)

2) Check in note 1759233 whether all correction notes for the ST-A/PI on the managed system were implemented in the newest version

3) Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure whether a dump occurs

“No Age characteristic found. The Analysis Type "Age Analysis" cannot be used." Exception when calling a specific monitoring object / key figure in BP Analytics

1) For some key figure groups, e.g. lead time key figures or automation rates, no age analysis is intended.

2) Please verify if your key figure requires and intends an age analysis. If yes, probably wrong customizing for the monitor / key figure was delivered with the ST-A/PI. Please check whether this issue is already addressed in one of our SAP customizing notes summarized in SAPNote 1848622.

Warning “No target currencies were found for currencies in data set” in function Benchmarking or Trend Analysis when selecting “Document value”

As a workaround: It should be still possible to work with the document value in Advanced Benchmarking.

Within the managed system the function module AGS_BPM_RI_POST_ACTIVATION does not yet inform the SAP Solution Manager that a managed system was informed about the TwinCubes activation.

This is triggered in class CL_AGS_RI_CONN_BPA_TWCUBE_REM, method PROCESS_EXCHNG_RATE_CONVERSION.

The issue lies with the post-activation procedures of the monitoring object. Upon activation,
the solution manager system notifies the managed system of the TwinCubes activation, and in return,
the managed system is supposed to confirm receipt of the notification from SAP Solution Manager.
However, the managed system is failing to communicate the confirmation, despite the benchmarking
analysis still functioning correctly.

Solution:
Please implement the latest version of the collective note for your SAP Solution Manager release.

Exception when calling Advanced Benchmarking and Age Analysis

1) Rebuild the AKF repository for one key figure (if the exceptions is only happening for one key figure) or for all key figures (if the exceptions happens for all key figures)

2) Please implement the latest version of the collective note for your SAP Solution Manager release.

3) Check the authorizations of the User in the READ / TMW RFC connection on the managed system.

4) Check if the measure value in Benchmarking is displayed as “0”. Then the last data collection of this object returned with no documents à No Detail List on the managed system exists. In such a case it is not possible to use Advanced Benchmarking, Age Analysis and Detail Analysis as long as another data collection with results > 0 returns.

5) Check in note 1759233 whether all correction notes for the ST-A/PI on the managed system were implemented in the newest version

6) Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure where the dump occurs

Exception when jumping to the SAPGUI-Based detail list

1) If this issue occurs for all key figures within BP Analytics: 

1. Do a connection for the TRUSTED / LOGIN connection between SAP Solution Manager and managed system (transaction SM59)
2. It might be an authorization problem. Your user might be lacking authorizations on the managed system as well as on the SAP Solution Manager. It is recommended to do an authorization trace via transaction ST01.
3. Check whether the most recent BPImp notes are implemented on the managed system as well as on the SAP Solution Manager.

2) if this issue occurs only for specific key figures within BP Analytics

1. Check if the measure value in Benchmarking is displayed as “0”. Then the last data collection of this object returned with no documents à No Detail List on the managed system exists. In such a case it is not possible to use Advanced Benchmarking, Age Analysis and Detail Analysis as long as another data collection with results > 0 returns.
2. Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure where the dump occurs
3. Check whether the most recent BPImp notes are implemented on the managed system as well as on the SAP Solution Manager.

Exception when jumping to the WEB-Based detail list

1) If this issue occurs for all key figures within Business Process Analytics:

1. Rebuild the AKF repository for all key figures.
2. Check the authorizations of the User in the READ / TMW RFC connection on the managed system.
3. Check whether the most recent BPImp notes are implemented on the managed system as well as on the SAP Solution Manager.

2) If this issue occurs only for specific key figures within Business Process Analytics

1. Rebuild the AKF repository for the one key figure that is affected.
2. Check if the measure value in Benchmarking is displayed as “0”. Then the last data collection of this object returned with no documents à No Detail List on the managed system exists. In such a case it is not possible to use Advanced Benchmarking, Age Analysis and Detail Analysis as long as another data collection with results > 0 returns.
3. Check whether the most recent BPImp notes are implemented on the managed system as well as on the SAP Solution Manager.
4. Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure where the dump occurs

Exception when opening a key figure variant

Please note: It is not SAP’s recommended best practice to work with variants. Instead one of the Management UIs (Business Process Dashboards, Dependency Diagram or Progress Management Boards) shall be used.

1) Rebuild the AKF repository for one key figure (if the exceptions is only happening for one key figure) or for all key figures (if the exceptions happens for all key figures)

2) Check in note 1759233 whether all correction notes for the ST-A/PI on the managed system were implemented in the newest version

3) Check in note 1848622 whether customizing corrections for your ST-A/PI are required for the key figure whether a dump occurs

Business Process Dashboards

KBA's

“NO authorizations” to create Dashboards

1) Please check whether you have the role SAP_SM_DASHBOARDS_ADMIN assigned.

2) Please also ensure that the corresponding role profile is assigned to your user.

3) In case the profile is not assigned to your user, please check whether the role is already generated.

Dependency Diagrams

KBA's

Progress Management Board

KBA's

TwinCubes

Activation failed

Please make sure all SAPNotes listed in note 1759233 - BPO Dashboards/BP Analytics: requires.SAPNotes for SP05/higher are implemented in the newest version in the Solution Manager.

Ensure that the “BW Connection Status (RFC Dest.)” and the “BW User Status (User ID)” are green. Additionally check in the Job Log, whether there are any indicators why the migration failed and eventually resolve it.

Afterwards restart the migration

Migration remains “in process” forever

Depending on how much data is in the old Business Process Analytics Infocube, the migration can take several hours up to a few days.

Please check whether you have data insight the Business Process Analytics Infocube. You can do so via transaction se16 and enter table /BI0/F0SM_BPMRH. View the “Number of lines2 of the table. If the table has 0 lines, it means you have never been using the Analytics based on the BP Analytics Infocube. If you started the migration for data from the Business Process Analytics InfoCube into the BP Analytics TwinCubes, the migration might remain “In Process,” as there was never data which could be migrated.

Connector was not created

If the TwinCubes connector was not created automatically with the TwinCubes migration, you can create the connector manually. To do so, go to transaction SE80, Package AGS_BPM_RI and Web Dynpro Application. Right click on it and select “Test”:

A browser window will open up. In the new window select “Change Conn. Repo”.

Select “Add”.

Fill in the value for the new connector. It is important to fill in the parameters 1 to 1, otherwise Business Process Analytics will not work:

Technical Name = BPA_TwinCube
Description = Business Process Analytics Twin Cube
Implementing Class = CL_AGS_RI_CONN_BPA_TWCUBE

Afterwards select “Add”. The select “Save”. Refresh the browser window.
Finally check whether the Connector and Active Connector Instance were created correctly. This is how it should look like: