SAP BPC 10.1 Embedded – Integrating Planning Function

This blog describes about how to create and integrate planning objects like planning function/sequences in the EPM Addin Excel Interface in BPC 10.1 Embedded model.

Introduction

Overview

SAP has introduced the new version of SAP BPC (“Embedded”) as part of new release 10.1. SAP BPC 10.1 comes with two separate versions:

• SAP BPC 10.1 Standard
• SAP BPC 10.1 Embedded

This whitepaper covers details of BPC 10.1 Embedded model and describes how to integrate planning function/sequences with EPM Addin Report. SAP BPC 10.1 Embedded version is not extension of SAP BPC 10.0 but can be considered as extension of BI-IP PAK where SAP has tried to integrate best of both worlds (SAP BPC and BI-IP). SAP BPC 10.1 Embedded is still new and not all functionality has been integrated in current version. However, there are many advantages of Embedded model.

Advantages of Embedded Version

• Optimized planning functions leveraging SAP HANA for better, more timely decisions
• Leverages existing the SAP Business Warehouse (SAP BW) application’s integrated planning models and benefit from SAP HANA acceleration in addition to new capabilities
• New HTML5 UI for easier navigation and cross-platform readiness
• New modeling capabilities with tighter integration into SAP BW and SAP ERP

BPC Embedded Architecture

With SAP BPC NW 10.1 a new architecture has been introduced that combines the strengths of both worlds. As shown below, the “Embedded Model” architecture is different from that of a standard BPC model. Embedded Model uses reporting and planning capabilities of BW as well as its data warehousing and data management. The collaboration-capabilities are that from SAP BW (orange component). The BPC HTML5 web-client has also moved to SAP BW and connects ‘Embedded’ models for modeling and runtime. In addition a new interface is contained in SAP BW to connect to the EPM add-in, in addition to the existing connections to Analysis Office and Design Studio. Finally SAP HANA is mandatory for the BPC ‘embedded’ model to facilitate best performance on highly flexible data models.

  Figure: BPC 10.1 Architecture

*http://scn.sap.com/community/data-warehousing/business-planning/blog/2013/12/23/unifying-bpc-nw-and-bw-ip

BPC Embedded Pre-requisites

SAP BPC Embedded model requires SAP NetWeaver BW 7.4 SP05 as a basis for the software installation as well as SAP UI5 1.16. SAP EPM 10.0 add-in is still used with the new SAP BPC 10.1 back-end, although SP18 onwards should be used to connect from EPM Addin. Windows XP through to Windows 8 are supported, with MS Office 2003, 2007, 2010 and 2013.

   For the Embedded version, a different EPM Add-in connection is used – INA Provider

SAP BW (INA Provider)

For Connecting the EPM Add-in we used SP 19 Patch 1

Figure : EPM Add-in SAP BW (INA Provider) Connection

The SAP BW (INA Provider) connections can be used to

• Work with BW queries (with or without variables).
• Retrieve data, using reports.
• Enter and save data, using input forms.
• Execute planning function for BW Integrated Planning.

Each time INA Provider connection is used, a query needs to be selected. Once selected, the

Report is automatically displayed with the query definition as it is defined in Bex Analyzer.

Modeling

Embedded Environment

Figure : Embedded Environment Type

Embedded Model

 As shown below, embedded environment created, next steps is to create the Models

Figure :  Embedded Model

In embedded world, realtime info-cube and corresponding aggregation levels needs to be created before creating the BPC Embedded Model

Figure :  Real Time Info cube

Figure :  Aggregation Level

Note: Use Transaction RSPLAN for creating unified objects like aggregation level, filters, planning functions, planning sequences

The next step is to create the BPC Model. While doing so, aggregation level or Info-cube needs to be selected which was created in the previous step

Figure : Embedded Model

Embedded Planning Objects

Transaction RSPLAN is used for creating Embedded planning objects. Planning objects are of following types:

1. Info Providers
2. Aggregation Levels
3. Filters
4. Planning Function
5. Planning Sequence

Info Providers

Figure : RSPLAN Info provider

Filters

Figure : RSPLAN Filters

Planning Functions

BPC embedded has pre-built in functions that can be configured based on requirement. For custom codes/scripts, separate planning type like Formula/Exits can be used. Fox code is similar to BPC scripts.

Figure : RSPLAN Planning Function (COPY)  

Planning Functions

Planning sequence is used to combine multiple functions to be executed in sequential manner. Planning sequence requires aggregation level, filter and planning function. Planning functions are executed based on the sequential steps.

Figure : RSPLAN Planning Sequence

Embedded Query

For integrating Embedded planning objects created above with EPM Addin, an input ready query needs to be created on the aggregation level. The query can be called from the Excel front end along with other planning objects like planning sequences or planning functions

Figure : Input Ready Query

  EPM Add-In Connection:

Integrating Report

  For EPM Addin integration, Input ready query created from previous steps can be searched and displayed in the EPM Add-in excel interface.

Figure : EPM Addin Query Selection

Figure : EPM Addin Query Selection

Figure :Report Layout based on Query

Integrating Planning Functions

Planning sequences/functions can be integrated using the new tab “Planning Objects Tab”. The planning objects can be searched and easily integrated in EPM Addin excel interface using planning objects Tab.

Figure : EPM Addin Planning Objects

Figure : Search Planning Function

Based on the planning function definition, variables and filters can be modified at run time. As shown below, variables (Source, Target) for planning function (copy) is changed

Figure : Planning Variables

Filters used can also be changed at runtime.

Figure :Planning Filters

  Planning function can be executed using new EPM API’s ExecutePlanningFunction. In this example a macro is used to call the API and the Marco is assigned to a button created in Excel Interface

Figure :Planning Function Macro

Macro for Run the planning function:

Sub PlanningFun() Dim api As Object

Set api = Application.COMAddIns(“FPMXLClient.Connect”).Object api.ExecutePlanningFunction”PF_1″

End Sub

Once button is clicked, the planning function is executed successfully

Planning Function Execution

Figure :EPM Addin Menu

Integrating Planning Sequences

Figure :Planning Sequence

Integrating Planning Sequences

Figure :Planning Sequence Execution

Macro for Run the planning sequence:

Sub PlanningSeq() Dim api As Object

Set api = Application.COMAddIns(“FPMXLClient.Connect”).Object api.ExecutePlanningSequence “PS_1”

End Sub

References:

• .sap.com/businessobject/product_guides/…/EPMofc_10_user_en.pdf
• http://scn.sap.com/docs/DOC-51897
• http://scn.sap.com/community/epm/blog/2014/03/20/sap-business-planning-and-consolidation-101-nw-faqs
• http://scn.sap.com/community/data-warehousing/business-planning/blog/2014/01/10/sap-bpc-101-unified-live-demo-chapter-01–edw-model
• http://scn.sap.com/docs/DOC-58899
• http://scn.sap.com/community/data-warehousing/business-planning/blog/2013/12/23/unifying-bpc-nw-and-bw-ip
• https://websmp106.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1998624&_NLANG=E
• https://help.sap.com/saphelp_nw73/helpdata/en/4c/b8332354182102e10000000a42189e/content.htm?frameset=/en/4c/acf4b354423b9fe10000000a42189b/frameset.htm&current_toc=/en/44/1f81d8cb5f0d1ae10000000a114a6b/plain.htm&node_id=53&show_children=false

Glossary:

• BPC Embedded: New BPC unified environment
• BPC Classic: Standard BPC environment as in previous versions like 10.0
• Aggregation Level: An aggregation level is defined by a set of characteristics and key figures of the underlying Info Provider
• Planning Filter: A filter is an object that describes a multidimensional extract of data from a data set
• Planning Function: A planning function describes how the transaction data of a specific aggregation level is changed
• Planning Sequence: Planning sequences are used in BW-Integrated Planning to group planning

functions

• Variables: Variables act as placeholders for characteristic values, hierarchies, hierarchy nodes, texts, and formula elements, and can be processed in many different ways
• Input Ready Query: Input-ready queries are used to create applications for manual planning. These can

range from simple data entry scenarios to complex planning applications

• Info-Providers: Info Providers contain real-time Info Cubes and Data Store objects for direct updates in planning mode
• API: Perform some tasks (such as reporting and input tasks or user interface actions) by using the

provided APIs in Microsoft Visual Basic for Applications (VBA)

• PAK: Planning Application Kit