Skip to Content
Author's profile photo Raj Kandula

Migrating BPC Standard Solution to BPC Embedded – Points to Consider

In this blog, we will discuss the points that we need to consider while migrating your existing BPC standard solution to BPC Embedded.

If you are planning to migrate your existing BPC Standard Solution to BPC Embedded Solution, first you need to understand that there is no migration path. You need to re-implement your existing BPC standard solution into embedded solution.

Before, considering this option and proceeding further you need to remember that this re-implementation will completely change the way your end users will work/interact with the planning solution. Apart from this you will be hugely benefitted by this re-implementation because of below factors

  • BPC Embedded doesn’t required a separate transaction data flow/master data flow which will positively impact your month-end closing & less activities that business admin to perform
  • SAP is positioning BPC embedded as its main planning solution and working on lot of value add-ons
  • BPC Embedded security need not to be maintained at two places & can be fully controlled by your BW authorisation concepts
  • You can push down all the complex & time consuming calculations to HANA database which improves your performance significantly
  • Apart from these, you will also gets default support of HANA Views & HANA based mixed scenarios

In spite, of these advantages there are couple of challenges that business needs to address while moving their solution from standard to embedded

  • Re-implementation of  existing standard solution in embedded is a costly affair as you need spend lot of time & money for this re-implementation
  • Also, its going to be a big change for end users as in embedded solution, all front-end reporting will be in Analysis Office & this needs separate training for users
  • Unlike in standard,  the embedded solution cannot be owned & driven by business as it requires high level of IT support
  • Apart from all this, you need to set-up a implementation team which possess SAP BO/BW skills along with knowledge of FOX formula, Script Logic & ABAP

Now, we will look into few areas and understand how it will impact


  • As discussed earlier, we need to re-implement all the models in existing solution as real-time cubes/planning aDSOs followed by the required embedded objects inventory like aggregation levels, filters, planning functions, planning sequences, input-ready queries & Analysis office workbooks
  • Also, we might need make some tweaks or change entirely the existing BW staging layer that is supporting the existing BPC standard solution. You can now closely integrate the BPC relevant master data and transaction dataflows with your existing BW flows. Thus, we will be able to save data loading times, avoid data redundancy
  • During modelling we can significantly achieve architectural improvement by leveraging new modelling objects like Advanced Data Store objects, Composite Providers, Code Pushdown capabilities of HANA

Logic Design:

  • Need to develop all the logics in FOX(Formula Extension) based formulas
  • ABAP/HANA based stored procedures can be used to handle complex calculations

Report Design & Analysis:

  • Analysis Office along with Query designer will cater the needs of reporting & manual input
  • First, BW queries(input-ready queries for data input) needs to e developed for both reporting & data input needs
  • Analysis office workbooks will be created by consuming bw queries.
  • Creating Analysis Office workbooks & BW queries using BEX requires good amount of technical skills
  • EPM Add-in with limited functionality can be used on top of BW queries built on Planning infoproviders
  • We need to rely on BW’s standard feature of report broadcasting for workbook distribution & for collection process we need to built a VBA based custom solution
  • End users needs to be trained extensively on Business Objects Analysis Office & Bex Query Designer

Data Manager Package:

  • BPC embedded provides all the basic planning functions like Copy, Delete, Report, Forecast, Distribution etc..,
  • To match the required data manager packages of standard, here in embedded we need to create all the required planning functions explicitly by making use of delivered planning function types
  • These planning functions can be executed in backend using RSPLAN or by triggering a process chain
  • We need to create AO workbooks with buttons supported by VBA macros which in-turn can be Unlike in BPC standard, there will be no ready to use data manager packages for flat file upload and we need to build a custom solution for each required flat-file upload functionality

Data Migration:

  • All the existing data needs to converted from accounting based model to key figure based model
  • Required accounting logic for data sign viz.., AST, LEQ, INC & EXP needs to be developed
  • Also, we need to develop the required data/report based logic to support YTD, QTD & MTD
  • Time format also needs to be adjusted in data of existing planning solution
  • All these points needs to be considered while executing data conversion during this transformation

Other Features:

  • To use functionalities likes Work Status/ BPFs we need to create a planning model in BPC Web administration
  • Work status can be created on top of this planning model
  • Also, embedded bpc supports creation of business process flows & Analysis Office workbooks can be added to these process templates

Overall these are few main points that we need to consider or aware of while considering BPC standard to embedded migration. I will keep updating this blog with my observations going forward.

Thanks for reading and please leave your comments/feedback.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Informative blog, thanks for sharing ..


      Author's profile photo Former Member
      Former Member

      Thanks for providing this game plan for our BPC migration.  I've sent this to our team as the outline for our initial migration discussion.  There will certainly be some uncomfortable discussions as we go through this detail line by line.  Thank you -