SAP BPC 10.1 – another version, another expensive upgrade project. Or is it?

5 February 2014

Sue Kirby

Sue Kirby

Global CoE Lead, Enterprise Performance Management

The new version of SAP BPC 10.1 is in ramp-up and there is much hype about BPC and BW-IP finally joining forces. If you want a quick rundown on the FAQ’s, it’s worth checking out The SAP BPC 10.1 FAQ by Tristan Colgate.

This blog post is the first of a series in which I’ll look at how to exploit particular areas of functionality. For organisations with existing SAP BPC or BW-IP planning solutions, this new version may  conjure up images of lengthy project plans and capital expenditure which could be better used elsewhere. However, this is not necessarily the case.

Dispelling the cost myth around SAP BPC 10.1 upgrades

There are four possible start points for any SAP BPC 10.1 upgrade. For each one I’ll explain how the migration can take place and give an idea of cost. Each of these assumes that you are doing an in place upgrade (using the existing server).

1) Existing SAP BPC 10 solution to BPC 10.1 Classic - £

  1. Run migration program
  • Very low cost upgrade project
  •  If the business would like a solution which is more suited to a BW-IP type of backend, then this migration would allow for the existing SAP BPC 10 solution to continue whilst a BW-IP solution is being developed in the backend which can utilise the same SAP EPM add-in functionality on the front end.

2) Existing BW – IP solution to SAP BPC 10.1 BPC / Pack Unified - ££

  1. Set up SAP BPC Environment on top of existing BW-IP solution
  2. Create new reports with SAP EPM add-in or  web client based on existing BEx Query
  • Low cost upgrade project
  • To utilise the capabilities of the EPM add-in, the reports and input schedules will need to be redeveloped. This will enable users to exploit the full blown functionality of SAP BPC on the front end
  • A typical business case for this type of upgrade would be if Financial Consolidation functionality was required. Financial Consolidation could be implemented using the "Classic" BPC view available in SAP BPC 10.1 whilst retaining your existing solution in SAP BW - IP

3) Existing SAP BPC 7.5 solution to BPC 10.1 Classic- ££££

  1. Run migration program
  2. Adjust task profiles (as 10.1 has greater granularity)
  3. Migrate Evdre reports to SAP EPM add- in reports
  4. Adapt BADI implementations
  • Costly upgrade project
  • There are numerous business benefits to upgrading from SAP BPC 7.5. The EPM add-in on SAP BPC 10.1 is far superior to BPC 7.5 and there are enhanced consolidation functions as well as tighter integration with the back end.E

4) Existing SAP BPC 10 solution to BPC 10.1 BPC / Pack Unified - £££££

  1. There is no migration tool and most of the development must be rebuilt
  • Very costly upgrade project
  • This is a full upgrade to utilise all the features of the new SAP BPC 10.1 version which will include moving the BPC data from account based to key figure based.  In order to use the unified model, SAP HANA must also be installed which is why this upgrade gets £££££

To conclude

As you can see, if you are already running SAP BPC 10, the migration to BPC 10.1 consists of simply executing one program. Similarly, if you’re already running SAP BW-IP, the migration strategy is again simple although the EPM reports will need to be created which is why it’s a slightly more costly approach.

Migrating to the full blown Unified model exploiting all functionality of SAP BPC 10.1 is a lengthier process but can be done while the classic SAP BPC solution is being used, thereby allowing the upgrade to take place on the same server.

In the next blog in this series, I’ll go through some of the immediate changes that we see in the Look & Feel of BPC particularly in the administration interface.

View comments

Comments

Blog post currently doesn't have any comments.

Bluefin and SAP S/4HANA - welcome to the one horse race

We use cookies to provide you with the best browsing experience. By continuing to use this site you agree to our use of cookies.