Note 1657623 - SAP Buffer Tuning for BPC 10NW

Summary

Symptom

Prior to this note, it was not clear which SAP buffers were used for BPC Meta/Master Data server side caching.  This meant that SAP buffer sizes had to be calculated manually and the tuning/sizing of these buffers specifically for BPC NetWeaver was a difficult process

Other terms

BPC Performance, BPC Memory Management, BPC System Tuning, BPC Server Caching

Reason and Prerequisites

The default profile parameters related to SAP buffers are not optimized for the new BPC NetWeaver Meta/Master Data caching mechanism.  These new caching mechanisms in BPC NetWeaver rely heavily on having sufficient sizes set for specific SAP buffers.  If these SAP buffers are not configured correctly for BPC NetWeaver, then BPC Meta/Master Data cannot be fully cached within the Application Server Memory.  If the BPC Meta/Master Data is not fully cached, additional overhead will be added to the back end server runtime due to direct database access and this will impact the overall performance of BPC NetWeaver.

Solution

The buffer parameters listed below must be set to an appropriate size in order to properly utilize server side caching of BPC Meta/Master Data.

• SAP Table Buffer ( See note 480710 for details )

• Parameter: zcsa/table_buffer_area

• Parameter: zcsa/db_max_buftab

• Shared Object Buffer ( See note 1657612 for details )

• Parameter: abap/shared_objects_size_MB

• This buffer is only used when shared memory is turned on for BPC NetWeaver. Please see note 1657612 for additional details on how to enable shared memory for BPC NetWeaver.

• Export/Import Buffer ( See note 702728 for detail )

• Parameter: rsdb/obj/buffersize

• Parameter: rsdb/obj/max_objects

• You only have to adjust this buffer if note 1634921 is applied or BPC 10NW has been upgraded to SP04

After applying this note or upgrading to BPC 10NW SP05, you can run the report UJA_BPC_BUFFER_SIZER to calculate the recommended size of the buffers listed above.
Note

• The buffer sizes are calculated based on the total volume of Meta/Master Data for the BPC Environments specified; it does NOT take other SAP Applications into account. You must determine the final profile parameter values by combining what is calculated by the tool along with all other external factors (such as hardware capacity of your server, and usage of the buffers by other applications).

• You will need to re-adjust the parameters when the meta/master data volume grows dramatically.

• BPC 10 NetWeaver will not use the Shared Object Buffer by default. As of SP05, you can switch it on in the IMG after you have set it to an adequate size. Please see note 1657612for additional details on how to enable shared memory for BPC NetWeaver.

• If profile parameter zcsa/table_buffer_area is greater than 2GB and your Application Server is on a 32bit platform, you need to adjust shared memory pool 19 to '0' ( profile parameter: ipc/shm_psize_19 ).

Business Objects Planning and Consolidation(BPC) - Data Push from BPC Cube to BW Cube through APD

Scenario

This scenario will show how to push data from BPC Application to BI

Introduction

The Data Manager module in SAP Business Objects Planning and Consolidation, version for SAP NetWeaver, utilizes SAP NetWeaver Process Chains, and provides a way for business users to execute these chains via Data Manager Packages.

Technical Information to the developer:

Since this development is involved the push data to BI for reporting.

1) A query is developed on BPC application Multi provider. The Bex query is referenced in APD. The filter setting will be done inside the query designer for everytime the user likes to change the selection in pushing the data from BPC.

2)  Create the required BI structures (InfoCube, DSO[Direct Update, Standard], InfoSource, DTP) as shown in screen shot below

3) Data is pushed through APD : Below is the screen shot for the data flow in BI through APD.

Here we are assigning source field to Target. This is a ABAP routine that need to be developed according to the requirement source fields (BPC) to target fields (BI) mapping. Finally the data is sent to BI direct update DSO in BI and then from Direct update DSO to Standard DSO further to target cube on which BI reports  will be developed.

4) Create the Process Chain that will be triggered from BPC Data Manager. This process chain is created on APD, which is pushing data from BPC cube to BI cube as mentioned in above screenshots.

5) Create DM package inside BPC application to trigger the Process Chain

Chavi Jindal   I am SAP BI-BPC & ABAP Certified Consultant. Having overall experience over 5.6 years. I have worked for couple end-end implementation projects as well as support projects.