Financial Management Blogs by SAP
Get financial management insights from blog posts by SAP experts. Find and share tips on how to increase efficiency, reduce risk, and optimize working capital.
Showing results for 
Search instead for 
Did you mean: 

Here I am sharing some tips regarding the trouble shooting of upgrading issues (within 10.0 series or within 10.1 series). End users may face the following issues after SAP Strategy Management (SSM) upgraded to a higher service package within 10.0 series or 10.1 series.

Users could not access SSM End Users Interface.

For SSM 10.0, if users could not access the End User interface after upgrading, check if Chapter 3.5 and Chapter 4.6 of upgrading guide, regarding

exporting and importing roles, are strictly followed. If not, all the SSM roles need to be re-assigned SSM actions (referring to the installation guide Chapter 7).

Script errors and Undefined labels.

Check if the imported boostrap data ( or are from the same version of PAS, which should be also the same SP version level of the CPMSTRMGMAPCxx_xx.xxxxxxxx.SCA file. If a patch (eg. SSM 10.0 SP11 Patch01) is applied, try to recreate named queries (http://<ser>:<port>/strategy/tools/namedquery.jsp) to fix named query errors in Netweaver Java traces.

Entry and Approval or cubebuilder is not working.

After PAS upgraded, check if the procedure files located in the InternetPub folder are replaced with the files of the corresponding database type.

Application Server (PAS) isn't working.

If the PAS is running on Windows, check if its installation path is unchanged. If the installation path need to be changed, the directory paths in

the lssever.ini file (located in C:\Windows) needs to be modified to map to the new installation path.

Some statuses are missing from Strategy tab.

For SSM 10.0, check if the scheduled tasks (SSM Administration > Scheduler) are re-defined and re-enabled. Make sure "Calculate All Scorecard Objects" is scheduled to be executed regularly.

Duplicate scorecard objects appear on Scorecard.

It is strongly recommended to use an NW Java infrastructure which is officially supported by SSM. If running Netweaver Java on a load balancing environment on which SSM doesn't officially support, then please shut down all the other NW instances and only leave one active instance to import the boostrap data file and database files, otherwise, the importing process might fail or duplicated items (eg. duplicated scorecard items) might be imported to the database.

If the release note of the specific version and the upgrading guide are strictly followed, then usually most of these issues can be avoided.

The following lists some other check points during upgrade:

  • Check if all the SSM components, especially the Application Server (PAS) and the deployed CPMSTRMGMAPCxx_xx.xxxxxxxx.SCA file are on the same Service Package level. For SSM 10.1 SP5 and earlier, or SSM 10.0 series, check if versions of all the other components are exactly same as required in the release note.
  • If the PAS server is running on Unix/Linux, check if the necessary environment variables are added to the necessary PAS scritps (eg. runlss.ksh, runlss.csh, lsstcp.ksh, lsstcp.csh, etc). For the details of adding variables to scripts for Unix/Linux, please refer to the installation guide. Check if the OS
    user used in the definition of model connections has the permission to run the scripts and programs.
1 Comment