Traditionally SAP BPC came with 2 flavors;
With the release of SAP BPC 10.1, two product variations were introduced in the SAP NetWeaver version, namely: Standard and Embedded (prior to support package 3 of release 10.1; Classic and Unified respectively).
While the Standard Model does not differ much from the BPC 10.0 for NetWeaver, the Embedded model provides a planning suite that is based technologically on SAP BW 7.4/7.5 on HANA and combines the planning components of SAP BW Integrated Planning and SAP BPC. There is also a BW/4HANA version available which is an evolution of BW that is completely optimized and tailored to SAP HANA. This version supports only Embedded models and no Standard models.
This means there are about 4 different versions of SAP BPC available today, depending on how you count:
First of all, let’s define more precisely what comprises each product:
When we compare the SAP BPC Netweaver Standard and Embedded version we see the following differences:
1)At the moment there are two separate client options; Analysis Office and the EPM Add-In. Analysis for Office is a single Add-In with two Plug-Ins available (Analysis and EPM).
2)This simple example shows how the terms key figure model and account model are defined: if you want to assign several key figures (sales price, manufacturer price, mean price) to a characteristic (product P1). The key figures have the same unit (currency EUR). The key figure model includes all the key figures in one data record:
However, in the account model, you add a new characteristic which separates the key figures (here: price types) within the data record, and which you can use to determine which key figure is being used for planning.
In particular, the introduction of the Embedded Model offers opportunities. The opportunity to include complex Sales & Operations Planning in SAP BPC has become much closer. Where SAP BPC was originally a fully financially oriented product, the Embedded Model opens up to any planning process (particularly the non-financial planning processes). Benefits can particularly be found in calculating large data volumes (both master data and transaction data) e.g. complex operational and commercial planning, rolling forecasts, driver based planning, real-time financial planning, scenario planning and consolidation.
The decision to obtain for a specific version of SAP BPC will depend on quite some different factors and goes mostly hand in hand with several ‘pros’ and ‘cons’. Below are some factors (not exhaustive) of what should be taken into account are discussed, followed by a (simplified) decision tree.
Elements to be taken into account:
Disclaimer: this article is based upon the information and releases available today. Software develops rapidly and new updates and release will be expected in the (near) future which will clearly lead to the introduction of new functionalities and opportunities and therefore outdated the information in this article.