Skip to Content

SAP had released a two versions for BPC 10.1; they are BPC 10.1 Classic and BPC 10.1 Embedded.

The Classic version can be considered an extension of previous versions in the BPC family, and can be used to implement both planning and consolidations solutions.


The Embedded version utilizes Integrated Planning and BPC features, and is designed for planning only. Integrated Planning (IP) is a planning tool introduced by SAP before BPC came into effect.

/wp-content/uploads/2015/11/img_5637d1a5a9056_823992.png


Let’s look some of the differences between the Classic and Embedded versions from a configuration perspective:


1. Master and transactional data objects


Classic Embedded
This version utilizes BPC objects i.e., Dimensions for master data and Models for transactional data. When data is saved in BPC, it will be stored in the SAP BW system under the namespace /CPMB. This method is similar to that used in earlier versions of BPC. This version uses the SAP Business Warehouse (BW) system and its objects directly. Characteristics are used for master data, and data providers like Info Cube, multi providers, and so on are used for transactional data

2. Data loads


Classic Embedded
Master and Transactional data must be loaded to the BPC system. Source data can be loaded either from SAP Business Warehouse (BW) or from other external systems, such as flat files. Unlike the classic version, the embedded version uses the SAP Business Warehouse (BW) system directly, so we don’t need to add another layer of data loads for our project implementations.

3. Custom scripts


Classic Embedded
In addition to using the predefined scripts provided by SAP (e.g., Copy and Allocations), we can develop custom code to perform calculations using the Logic Script component. This version also provides a few predefined functions, but custom code must be developed using the FOX (Formula Extension) component.

4. Template development


Classic Embedded
Input schedules and reports are developed using the EPM Excel Interface. Schedules are used to develop templates which allow users to view and save data to the BPC system, whereas reports are used only to view and analyze data. BEX Query designer is used to developed schedules and reports. The resulting templates are accessed from BPC’s EPM Excel interface and presented to business users.

5. Security


Classic Embedded
This version uses both SAP BW and BPC system for security configuration. Users are created in the BW system, then granted permissions for objects and data via BPC. Most security features are configured in the SAP BW system directly, including creating users and granting permissions for objects. Data access can be configured in both the BW and BPC systems.
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply