Random issues faced during Business Process Monitoring (BPM) configuration on Solman 7.2

In this blog i will try to note some issues I faced during configuration of Business Process Operations. Issues are peculiar and might not be relevant for everyone.

A. Issue with Solman_setup -> Basic Configuration -> Activation of BW content (For UPL, RCA…)

During this i faced issue activating BW content. Error is as below. No other logs in SLG1 or ST22 in the system.

bw content error

Solution: I had to restore the logical BW system from RSA1 to fix the issue.

RSA1 -> Modeling -> Source System -> BW -> Logical System

Ran activation again from Solman_Setup and everything went fine.

bw content error1

Probable Cause: We did a client copy to create a new client and something went wrong while running BDLS.

B. Issue with Solman_Setup -> Basic BPO Configuration -> Configure Solution Manager -> Configure Automatically

Activity “Activate BW Cubes” runs into error “BW content not activated”

bw content error2

Solution: Activated the related cubes ( 0SM_BPM, 0SM_BPMRH, OSM_BPMRD) manually from RSA1 as suggested by SAP Note 2434326.

bw content error3

C. Business process monitoring tile is not visible in Solman_workcenter.

Follow the below SAP Note:

2338589 – Troubleshooting for Blank Business Process Monitoring workcenter applications in SAP Solution Manager 7.2

  1. Check and ensure that the user profile used has the following roles applied:
    i.    Run transaction SU01 and display the user profile.
    ii.   Navigate to the Roles tab and confirm that the following roles have been applied:
    –  SAP_SMWORK_BPO
    –  SAP_SMWORK_SM_ADMIN
  2. Check and confirm that the necessary UI5 services are active:
    i.    Run transaction SICF.
    ii.   Enter /sap/bc/ui5_ui5 within the service path field and select Execute.
    iii.  Confirm that the following services are active:
    –  sap_bpm_alrep
    –  sap_bpm_hier
    –  sap_bpm_search
  3. Clear the system cache and internet browser cache:
    i.    Complete all steps contained in the following SAP KBA:
    2319491 – How to clean up the cache after applying changes that affect SAP Fiori apps.
    ii.   Delete the browsing history of the workstation’s internet browser.

 

Advertisements

Usage and Procedure logging (UPL/SCMON) on Solution Manager 7.2

Usage and Procedure logging (UPL) also know as SCMON enables you to monitor you custom code usage and make informed decisions on the same.

You can either enable it either from the managed system directly or from SAP Solution Manager.

On the managed system the data is by default available only for 14 days after which it is overwritten.

Of course this is not enough data when you are looking at long term decision making.

In such case Solution Manager can be used to store the data in BW objects for longer duration.

Below are some points for configuring the UPL with Solution Manager 7.2.

System Preparation, Infrastructure Preparation and Basic Configuration has to be finished successfully.

Among these most import steps are:

1. Solution manager central note is applied in System Preparation

2. Infrastructure Preparation (Set up SAP BW)

3. Basic Configuration (BW Content activation (UPL) under configure basic functions)

It is very important that this step is complete.

4. Managed System Configuration (Maintain RFC’s)

All the required RFC’s (Especially read RFC to the Managed system of required client ) have to be maintained.

5. Custom Code management.

cc1

Steps 1, 2 and 3 are automatic activities and required to be completed successfully.

Under step 3 be careful to select the granularity of the data required while scheduling the house keeping jobs.

Most important steps are 4, 5 and 6 where you select the scope (SID, Client of Managed system) and enable the extractors and jobs to collect data.

If your Managed system setup is completed successfully, the system and client should be available here.

This completes all the actions required to activate UPL on Managed system and collect data on Solution Manager.

Now to verify that UPL is activated successfully, flowing can be done.

On the Managed system:

Execute Program /SDF/SHOW_UPL. This should show you data and available from date (Which is by default 14 days)

If available from data is empty, its time to recheck your configuration.


On Solution Manager:

Check if the extractor framework is is running fine.

SOLMAN_WORKCENTER

 

Check data in UPL Day DSO (0SM_UPLDD). You should find more than 14 days of data here for your managed system.

Note that from Solution Manager 7.2 SCMON extractor will not be filling the UPL day cube (0SM_UPL).