Skip to Content

BPC 10.1 Model Deployment Selection and Options

SAP’s Business Planning and Consolidation version for Netweaver 10.1 (BPC 10.1) achieved General Availability in June 2014.  With this newest release of BPC, SAP offers two models that can be deployed to meet your business needs.  I will attempt to provide some clarity around the pros and cons of each model selection:


Standard Model - the architecture and function of this design is the same as the previous BPC version, BPC 10.0.  The standard model is deployed within a host Business Warehouse’s protected namespace (“/CPMB/”).   SAP designed this protected area to satisfy customer s who wanted to carve out a planning area for their department without having to coordinate or share resources with the greater BW (EDW) community of users.  By segregating the BPC relevant transactional and master data directly within the protected namespace, the processes associated with the standard model are isolated and tightly controlled by the department running the application.  
The code set of the standard model has been coordinated with the code set supporting BPC 10.0.  Changes to BPC 10.0 are reflected in the BPC 10.1 Standard model, and changes to the BPC 10.1 Standard model are reflected into BPC 10.0.  As a result of this code compatibility, customers can enjoy easy migrations while performing upgrades from 10.0 to 10.1 standard models.

Embedded Model – the architecture of the embedded model has similar roots to previous planning applications from SAP as well.  In the case of the embedded model, the earlier versions were SAP BW Integrated Planning (BW-IP) and Planning Application Kit (PAK).   This model uses a different paradigm on data access:  master and transactional data from the entire host EDW environment is accessible by the application.  This model allows easy access to all data within the host BW, but this data is typically shared with many other users and the control of this data is usually provided through a centralized administration group.
Migration from earlier versions of BW Integrated Planning to the embedded model is easy.   However migration from earlier versions of BPC (10.0 and earlier) is typically a reimplementation.

Both models have their strengths and weaknesses.   There is not one best model for all customers.  Model choice should be based upon the business requirements mapped to each model’s characteristics.  To help with this analysis I have assembled the following comparison matrix between the two models:

CharacteristicSTANDARD MODELEMBEDDED MODEL
Data Modeling
  • Single key figure
  • protected name space
  • Multi-key figure
  • full EDW access
  • Using ‘Local Provider’ concept, embedded model can also have protected name space model
Master Data
  • Master Data must be copied into BPC namespace
  • Cannot utilize compounded master data
  • Master data from the host EDW can be utilized
  • Ability to use compounded master data definitions
  • Supports time-dependent attribute
  • Local master data (within local provider).
Transactional Data
  • All transactional records must be copied into BPC namespace
  • Transactional records can be sourced directly from host EDW

Security

  • Standard BPC security
  • Supports standard BW analysis authorization with matrix security
  • Supports combination of BW analysis authorization and BPC LoB owned DAP (Directory Access Protocol)
Functions
  • Script Logic – no current plans to execute script logic directly within HANA
  • SAP HANA Optimized functions:  Dimension Member Formulas  , Top Down Planning Using SAP HANA, Allocations using SAP HANA
  • FOX Formula logic  - many functions capable to execute directly in HANA
  • SAP HANA Optimized functions:  Copy, Repost, Revaluation, Delete, Deletion of Invalid Combinations, Set Key Figure Values, Distribution by Reference Data, Generate Combinations, repost on basis of Characteristic Relationship, Distribution with Keys, and Formula (many restrictions).
SQL push down to HANA
  • Technically possible with custom BAdI
  • Capability is delivered functionality
Data Locking
  • If two users access the same data: both users can modify a record’s value.  Any changes made are preserved, when both users exit the system the last change remains in the database.
  • “Last in wins”
  • If two users access the same data: only the user accessing the record first may modify the data set.  The data set is locked.  The second user is limited to read only.
  • “First in wins”
Additional Functions
  • Work Status
  • Validation
  • Characteristics Relationship
  • Work Status
  • Data audit
  • Comments are not yet available with BPC embedded
Consolidation
  • Full function consolidation functionality
  • Minimal consolidation functionality – more capability on current roadmap
User Interface
  • EPM Add-In, Web, and EPM Unwired
  • EPM Add-In, Analysis for MS Office, BPC Web, and EPM Unwired
EPM Add In
  • Direct access to BPC model and data
  • EPM Add In supported functions available:
    • drill thru
    • disaggregation model selection
    • disaggregation
  • Requires a BEx query acting as a data provider to support EPM Add In
  • EPM Add In supported functions available:
    • drill thru  (on roadmap for future release)
    • disaggregation model selection (on roadmap for future release)

In addition to each model’s characteristics, SAP currently has plans to provide Standard-to-Embedded and Embedded-to-Standard data movement capability (on roadmap for future release).

Note: All “roadmap/future release” referenced items are subject to change and may be changed by SAP at any time for any reason without notice. The information in this document is not a commitment, promise or legal obligation to deliver any material, code or functionality.

Sheldon Edelstein   sheldon.edelstein@sap.com

SAP Platform Solution Group

Tags:
Former Member