Archive for the ‘BPC’ Category

A solution vision for SAP Business Objects BPC v7.5 NetWeaver

Tuesday, January 1st, 2013

With the introduction of SAP BusinessObjects Planning and Consolidation 7.5 version for SAP Netweaver, there is ample opportunity for significant improvements of the workflow and consolidation of data for planning processes and applications. Having had the opportunity to provide a solution for our client using BPC Netweaver version 7.5 along with SAP BW v7.01 we can share the vision and the solution design we implemented. The vision is to provide a common infrastructure for centralized planning, forecasting, and reporting. The new netweaver 7.5 version provided us with the opportunity to migrate from the currently unsupported Microsoft 5.2 version to the NetWeaver technology stack. Here is what our solution looks like and some of the opportunities we took to implement enhanced process improvements and functionality.

Solution for BPC v7.5 and BW v7.01

Why does this solution work? First, by standardizing on a common technology stack you gain leverage of existing knowledge and skillsets. While there is plenty of BPC upskilling needed, BW integration is critical and leveraging known BW skillsets will take you a long way in an implementation. Second, the common technology platform, offers the opportunity of leveraging common reporting tools. While reporting on Plan/Actual data is best served using BPC EVDRe functions–trust me exel is not going away anytime soon–adding BW reporting tools into the information delivery strategy instantly broadens information access across the corporate user base.

What do we call these today? Official SAP BusinessObjects product names.

Friday, August 19th, 2011

This just in. The official list of product names as listed in SAP Note 1621084 (requires login to service.sap.com) .

What’s the difference between SAP BPC Lite and Full Optimization

Wednesday, July 13th, 2011

On our project we had a discussion on what the optimization functions are in SAP BPC netWeaver 7.5, their differences, and when they are to be used. Here is what we found based on research and our experience:

Lite Optimization

Background (ref SAP 1551154)

  • Is a maintenance process similar to the BW InfoCube performance maintenance tasks of index rebuild, statistics rebuilds, and compression.
  • This process deletes the infocube indexes and moves records from the F to the E fact tables.
  • This process compresses/collapses the records with the same key
  • Additional zero suppression is possible (manually adjusted in process chain)
  • Updates the infocube statistics

How often should it be run? (ref SAP 1508929)

  • There is no set recommendation as to the frequency, however it is generally recommended that these (index/statistics) tasks be executed after the load process to provide satisfactory performance for reporting and input schedule updates.
  • From 1508929 “There is no rule of thumb for how often to run optimizations. The need can vary depending on the characteristics of your hardware environment and your application.”

As best practice:

  1. When new application sets and applications are created run a Full Optimization.
  2. Lite Optimization doesn’t take the system offline, and can be scheduled during normal business activity (e.g. after a data load)
  3. Full Optimization need the system to be offline so they should be run at down-time periods – for example after a month-end close.

Full Optimization

Background (ref SAP 1551154)

  • This process essentially rebuilds the application in its entirety. The process creates a new application and copies the data to the new application.
  • This process is a RESTRUCTURING of the BPC application data model

How does the system determine if a full optimization is necessary?

  • The algorithm looks at the size of the dimensions and the dimension members. If the dimension tables have <20% size of the fact table and as many line item dimensions are used, then the system will give a message “Optimization not required at this time”.
  • The full optimization logic is as follows (ref. SAP 1551154):

If the InfoCube needs restructuring – do it, then perform lite optimization

If not, perform a lite optimization

  • Why does the infocube technical name change with the Full Optimization?

This is expected and by design. (ref SAP 1527747).

The SAP service notes listed in this post can be found here.