Skip to Content
Technical Articles

Sizing information for “SAP BPC Optimized for SAP S/4HANA” with FAQs

(Created as of release SAP S/4HANA 1809. It is also valid for SAP S/4HANA 1909)

In this blog, the sizing information of “SAP BPC (Business Planning & Consolidation) Optimized for SAP S/4HANA” is presented with FAQs. Here is a summary of “SAP BPC Optimized for SAP S/4HANA” sizing with the Quick Sizer tool.

You need to know “SAP BPC Optimized for SAP S/4HANA” a bit more.

  • SAP BPC Optimized for SAP S/4HANA is SAP BPC 10.1 NW Embedded with the delivered BPC contents in SAP S/4HANA.
  • SAP BPC Optimized for SAP S/4HANA is running on Embedded SAP BW in SAP S/4HANA
  • Embedded SAP BW is available for SAP S/4HANA but it is not intended to be an Enterprise Data Warehouse (See Embedded SAP BW -Definition and Positioning: Link).
  • SAP BPC Optimized for SAP S/4HANA provides the delivered BPC contents that includes Planning functions (see SAP Help Link). BPC users can input/report planning data with these contents.
  • SAP BPC Optimized for SAP S/4HANA can still be used for real-time planning but SAP Analytics Cloud for Planning (SAC) is SAP’s strategic planning application.

Some “SAP BPC Optimized for SAP S/4HANA” projects used “SAP Business Warehouse powered by SAP HANA” node in the Quick Sizer tool for initial sizing so far. For the delivered BPC contents (for example, such as InfoCube), the Quick Sizer for “SAP Business Warehouse powered by SAP HANA” node was more appropriate by comparing “SAP BW/4HANA” node. We have guided that customer can use the Quick Sizer for “SAP BW/4HANA” node, especially if ADSO (Advanced DataStore Object) is used instead of InfoCube. However “SAP Business Warehouse powered by SAP HANA” node was removed from HANA Quick Sizer with HANA Quick Sizer version 252 (golive: September 2018). Because SAP does not promote “SAP Business Warehouse powered by SAP HANA (as known as SAP BW on SAP HANA)” anymore. The product to go is “SAP BW/4HANA”.

Question is how customer can conduct “SAP BPC Optimized for SAP S/4HANA” sizing estimations without using the QuickSizer for “SAP Business Warehouse powered by SAP HANA” node.

Workaround (HANA Quick Sizer version 255):

The available workaround for “SAP BPC Optimized for SAP S/4HANA” sizing was to use the Quick Sizer for “SAP BW/4HANA” node and “SAP S/4HANA Embedded Analytics” node. The Quick Sizer “SAP BPC BW/4HANA Standard / Planning” node is designed for SAP BPC Standard model and was not recommended for use with “SAP BPC Optimized for SAP S/4HANA” sizing estimations.

We could think of below 2 Cases.

Case 1: Customer uses the delivered BPC contents (with small extension):

In order to get an estimate for your “SAP BPC Optimized for SAP S/4HANA” system, you can use the Quick Sizer for “SAP BW/4HANA” node (only Table 1) and “SAP S/4HANA Embedded Analytics” node (Table 1) as a workaround. The resource requirements (Memory & CPU(SAPS)) for Planning functions of “SAP BPC Optimized for SAP S/4HANA” is very close to the ones of an equivalent system running on SAP BW/4HANA. The resource requirements (Memory & CPU(SAPS)) for Reporting of “SAP BPC Optimized for SAP S/4HANA” would be estimated by “SAP S/4HANA Embedded Analytics” node. By using both nodes, you can estimate the effects of planning functions and reporting with the BPC contents. There is no need for any additional estimation for the data volume. Because usually plan data volume is not that huge compared to the actual data.

Case 2: Customer extends the delivered BPC contents and/or even more InfoCubes (more data volume is expected):

In this case, it may happen that the planning data may be significant compared to the actual data. It does not apply for the above Case 1 approach (usage of the QuickSizer for “SAP BW/4HANA” node (only Table 1) and “SAP S/4HANA Embedded Analytics” node (Table 1)), then additional sizing for the data volume is appropriate in this case. However, you can not estimate for this exceptional case by using Table 5 in the Quick Sizer for “SAP BW/4HANA” node. Because the Quick Sizer does not offer InfoCube in Table 5 anymore (only ADSO (Advanced DataStore Object) is available) and we would not recommend to use it at all. It is the current limitation with the Quick Sizer. If customer expects it to fall under this case, they need to order a Premium Engagement service or a consultant.

Most customers expect it to fall under Case 1, so we expect Case 2 to be rare.

From HANA Quick Sizer version 256:

SAP developments (BPC, BW and Sizing experts) discussed to create “SAP BPC Optimized for SAP S/4HANA” node under SAP S/4HANA sizing. Some appropriate algorithms were developed and transported from the established sizing algorithms. Finally, HANA Quick Sizer version 256 (golive: August 2019) was released and introduced “SAP BPC optimized for S/4HANA / Planning” node. You will see more information in “How to fill in the questionnaire” in the Quick Sizer.

Please note below points:

  • The sizing for Planning function will be covered by Table 1 of “SAP BPC optimized for S/4HANA /Planning”.
  • The sizing for Reporting will be covered by Table 1 of “SAP S/4HANA Embedded Analytics”.
  • The sizing for Data volume will be covered by Table 2 (InfoCube) or Table 3 (ADSO) of “SAP BPC optimized for S/4HANA /Planning”.

Version 256

The following 2 sizing approaches are considered.

 Case 1: Customer uses the delivered BPC contents (with small extension):

In order to get an estimate for your “SAP BPC Optimized for SAP S/4HANA” system, you can use the Quick Sizer for “SAP BPC optimized for S/4HANA / Planning” node (only Table 1) and “SAP S/4HANA Embedded Analytics” node (Table 1). The resource requirements (Memory & CPU(SAPS)) for Planning functions of “SAP BPC Optimized for SAP S/4HANA” would be estimated by “SAP BPC optimized for S/4HANA / Planning” node. The resource requirements (Memory & CPU(SAPS)) for Reporting of “SAP BPC Optimized for SAP S/4HANA” would be estimated by “SAP S/4HANA Embedded Analytics” node. By using both nodes, you can estimate the effects of planning functions and reporting with the BPC contents. There is no need for any additional estimation for the data volume. Because usually plan data volume is not that huge compared to the actual data.

 Case 2: Customer extends the delivered BPC contents and/or even more InfoCubes (more data volume is expected):

In this case, it may happen that the planning data may be significant compared to the actual data. It does not apply for the above Case 1 approach (usage of the QuickSizer for “SAP BPC optimized for S/4HANA / Planning” node (only Table 1) and “SAP S/4HANA Embedded Analytics” node (Table 1), then additional sizing for the data volume is appropriate in this case. For the data volume sizing of InfoCube, you can use Table 2 of “SAP BPC optimized for S/4HANA /Planning” node. For the data volume sizing of ADSO (Advanced DataStore Object), you can use Table 3 of “SAP BPC optimized for S/4HANA /Planning” node.

Most customers expect it to fall under Case 1, so we expect Case 2 to be rare.

FAQs———————————————

<Q1> Why we can ignore the data volume sizing if customer uses the delivered BPC contents (with small extension)? – Related to Case 1

We only need to consider SAP S/4HANA sizing which already included usage of SAP BPC as planning tool for SAP S/4HANA finance planning. Form the data volume perspective, SAP BPC generates plan data but it should be similar with old transaction code based planning. It means “SAP BPC Optimized for SAP S/4HANA” is only used as the tool in this case, it doesn’t generate ‘new’ data on the system level. As we don’t have additional sizing for financial planning in R/3, we don’t need additional sizing of the data volume for SAP S/4HANA. The expected plan data volume is small compared to the actual data that would be sourced from ACDOCA. So the data volume sizing should be covered by the actual SAP S/4HANA sizing. In general, no need to input for BPC data volume in the Quick Sizer.

<Q2> Do we need to consider 20% rule of Embedded SAP BW document if we use “SAP BPC Optimized for SAP S/4HANA”? (Link)

Above figure is saying “The amount of data persisted in the Embedded SAP BW should not exceed 20 % of the overall data volume of the system”. It means Embedded SAP BW should not extensively be used as Enterprise Data Warehouse. If you have more than 20% of the data volume sitting in the Embedded SAP BW, the workload associated with this system is assumed to be mainly of analytical nature. Based on this guidance from SAP, customer thinks it is a hard limit and try to check the 20% rule somehow. However customer can not specify in the Quick Sizer which share of the data is query relevant on a per table basis. By only using the Quick Sizer, they can not compare between the amount of data in Embedded SAP BW and the overall data volume of SAP S/4HANA system. In addition, we would consider this rule as being rather “soft” (not a hard limit) and the pure DB size is not so important if nobody is performing OLAP activities on it. From our point of view, it is at the customer’s discretion to decide if they anticipated substantial load from Analytics or not. In the end it’s all about making the customer aware that the more analytical workload they expect, the more CPU resources are required. A good rule of thumb is that at ~20% of the data volume that is relevant for Analytical queries we see a break-even point. If customer uses “SAP BPC Optimized for SAP S/4HANA” with the delivered contents (with small extension), we assume that the data volume in the Embedded SAP BW is expected much less than 20% that is relevant for Analytics. Customer does not need to worry about this rule.

<Q3> How customer can conduct the data volume sizing if customer uses Table ACDOCP?

Customer can store the planning data either in InfoCube (/ERP/SFIN_R01) or in ACDOCP table. As of now, most of customers chooses in InfoCube (/ERP/SFIN_R01) but a few customers start using ACDOCP table. No matter planning data is stored in ACDOCP or InfoCube, it should be very similar in terms of data volume sizing. Either ACDOCP or InfoCube is just a table in HANA data base. If Customers use table ACDOCP with the BPC contents as the replacement of traditional CO planning functionalities, they do not need to consider data volume sizing.

 

Please insert your comments if you have any.

Finally, I would like to thank experts at SAP for their tireless support, especially:

  • William Yu (BPC sizing owner)
  • Thomas Becker (BW development)
  • Nikolai Sauerwald (Sizing development)
  • Lars Rosenberger (DBS EMEA)

Brought to you by the S/4HANA RIG

Be the first to leave a comment
You must be Logged on to comment or reply to a post.