Skip to Content

What does the new EPM component mean for you?

Before November 22nd, any newly created error reports on the Support Portal for either SAP Business Planning and Consolidation or SAP Strategy Management used to use the high-level component CPM – either CPM-BPC or CPM-STM depending on the product.  Today, that has changed, as a new EPM high-level component has been created.  What does this mean, and how does this work?


What are the new components?

 The new components that have been created are as follows:


  – EPM Enterprise Performance Management

     + EPM-BPC Business Planning and Consolidations

        + EPM-BPC-MS Microsoft Version

        + EPM-BPC-NW NetWeaver Version

     + EPM-SCP Supply Chain Performance Management

     – EPM-SA Spend Analytics

     + EPM-SM Strategy Management


Note: there are now separate component hierarchies for the BPC NetWeaver and Microsoft releases, and each of these contain the same sub-components as the old CPM-BPC component. 


What does this change mean?

What this change does is group all of these Enterprise Performance Management products together under one high-level component.  Business Planning and Consolidation,  Strategy Management, and Supply Chain Performance Management used to be under the old CPM component, while Spend Analytics used to be listed under SRM-ESO-XSA.  They are now all available in one place.


Where are the Business Objects EPM products listed?

If you own a Business Objects EPM product, like Profitability and Cost Management or Planning Extended (formerly Cartesis), these are still listed under BOJ-EPM as they were previously.  The plan is to eventually include these products under the new EPM high-level component, but that change has not happened yet.


How does this change affect my existing reported problems, or Notes that I use?

Any messages or Notes created before November 22nd, and which were associated with one of the products for which the component name changed, have been automatically updated to the appropriate EPM-* component.  No change is needed before these can be referenced, and they now show up in queries made which include the new EPM high-level component.


The bottom line is that, apart from having to use EPM instead of CPM as a starting component, there should be no difference in the way new messages are created, or existing messages and Notes found.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.