SAP BPC 10 Sizing Guide.pdf

8/17/2019 SAP BPC 10 Sizing Guide.pdf

http://slidepdf.com/reader/full/sap-bpc-10-sizing-guidepdf 1/13

1

Please make sure that you are always using the most current version of the sizing guideline!

Sizing Guide

SAP BusinessObjects Planningand Consolidation 10.0,Version for SAP NetWeaver

Released for SAP Customers and Partners

Document Version 1.4, February 2012



Copyright/Trademark

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted

in any form or for any purpose without the express permission

of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States

and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C ®, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services mentioned

herein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in several

other countries all over the world. All other product and

service names mentioned are the trademarks of their

respective companies. Data contained in this document

serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with respect

to the materials. The only warranties for SAP Group products

and services are those that are set forth in the express

warranty statements accompanying such products and

services, if any. Nothing herein should be construed as

constituting an additional warranty.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressly

prohibited, as is any decompilation of these components.

SAP Library document classification: CUSTOMERS &

PARTNERS

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http://service.sap.com/sizing

http://service.sap.com/sizin

http://service.sap.com/sizin



__________________________________________________________________________________

1

SAP BusinessObjects Planning and Consolidation 10.0, (SAP NW) - SAP Customers and Partners

TABLE OF CONTENTS

1. Introduction ....................................................................................................................................... 2 1.1 Functions of SAP BusinessObjects Planning and Consolidation ..................................................... 2 1.2 Architecture of SAP BusinessObjects Planning and Consolidation ................................................. 2 1.3 Factors that influence the performance ............................................................................................ 4 2. Sizing Fundamentals and Terminology .......................................................................................... 5 3. Initial Sizing - Setup .......................................................................................................................... 6 3.1 BPC Environment setup for the 3 sizing categories ......................................................................... 6 3.2 BPC User Profile definition and Activities ......................................................................................... 7 4. Initial Sizing - Recommendations ................................................................................................... 8 4.1 Sizing when using EPM Add-in and Web frontend ........................................................................... 9 4.2 Sizing when using exclusively the EPM Add-in front-end .............................................................. 10 5. Comments and Feedback .............................................................................................................. 11



SAP BusinessObjects Planning and Consolidation 10.0, (SAP NW) - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

1. INTRODUCTIONSAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver (called SAP BPC NW),is a robust planning and consolidation application designed to meet organizational budgeting, planning,consolidation and reporting requirements. It supports a wide array of top-down and bottom-up financialplanning needs, as well as consolidation processes that ensure a smooth and timely financial close, all

using a single application. Through the implementation and utilization by implementing and using SAPBusinessObjects Planning and Consolidation, organizations are empowered to meet increasinglystringent regulations, effectively plan strategies and tactics, and obtain the information necessary togain important insights.

1.1 Functions of SAP BusinessObjects Planning and ConsolidationSAP BusinessObjects Planning and Consolidation enables organizational planning and consolidationprocesses. The application helps to improve planning and consolidation frequency, accuracy, andeffectiveness; reduce budget-cycle times and costs and increase user confidence in the validity offinancial results. The primary capabilities of SAP BusinessObjects Planning and Consolidation include:

Planning :o Budgetingo Planningo Forecastingo Business Process Flows

Consolidation:o Financial Consolidationo Intercompany Reconciliationo Journalso Financial Closingo Reporting

1.2 Architecture of SAP BusinessObjects Planning andConsolidation

At a high level, SAP Business Planning and Consolidation, version for SAP NetWeaver, has three tiers: Client tier: Runs Zero Footprint (aka ZFP, Web), Microsoft Office (including Microsoft Excel,

Microsoft Word, and Microsoft PowerPoint), or SAP BusinessObjects Planning andConsolidation Administration (Web)

Application server tier: SAP NetWeaver BW Application Servers (OLAP Engine and Application Logic), aka BPC Add-on

Database tier: Any database engine including SAP NetWeaver BW physical data storage




Copyright/Trademark

Figure 1: Architecture of SAP BusinessObjects Planning and Consolidation

Note that the .NET tier that handled the communications between client and application server is nowremoved and replaced by REST interfaces on the application server. Thus, the work that was done bythe .NET server is now done by the application server.




Copyright/Trademark

Server Components of SAP BusinessObjects Planning and Consolidation, versionfor SAP NetWeaver

To help you understand the different configurations, following are the components used by SAPBusinessObjects Planning and Consolidation. For more information about the hardware requirementsand underlying software requirements, see the documentation on SAP Service Marketplace at

https://service.sap.com/instguidescpm-bpc: SAP BusinessObjects Planning and Consolidation – MasterGuide & Installation Guide.

Database Tier Can be any database supported by SAP NetWeaver (MS SQL, Oracle, DB2, MaxDB, etc…) Full support of 64-bit and Unicode capabilities Common Processing

o All reads of datao All write back of datao Metadata read/writeo File Storage Read/Write

Storage location for all application files Book Repository Report & Input Templates Unstructured Data Conversion & Transformation Files

SAP NetWeaver ABAP Application ServerPlease note .NET server is no longer part of the architecture. It was replaced with BPC REST Layerwhich is part of the BPC Add-on.The BPC Add-on has the following components:

BPC Rest Layer (Replacement of .NET server) Business Service Layer (existing also into SAP BPC 7.x) Infrastructure layer (existing also into SAP BPC 7.x) – One important change of this layer is the

system is using NW users for authentication.

Client TierBPC Client has two big components:

Web client using IE browsero SBC BUI Flex Frameworko BPC Web UI

BPC add-in office part of EPM add-in.

1.3 Factors that influence the performanceThe following factors can influence the performance of SAP BusinessObjects Planning and

Consolidation: Active concurrent users in the system Hardware (CPU, Memory, Network bandwidth, whether BWA used) Data volume of Master Data Complexity of the hierarchies (Number of hierarchies, deepest level of hierarchy) Data volume in cube(s) Complexity of any script logic and the formula used for calculations Complexity of any consolidation logic Complexity of any member access rules Number of BPF step region instance Complexity of Report or Input Form Design (Size of the report, if MDX query needed) Complexity of default logic for write-back Complexity of transformation/conversion files for data loading through DataManager Sparse of source data when loading transaction data through DataManager

https://service.sap.com/instguidescpm-bpc

https://service.sap.com/instguidescpm-bpc




Copyright/Trademark

2. SIZING FUNDAMENTALS AND TERMINOLOGY SAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide,we assume that you are familiar with sizing fundamentals. You can find more information athttp://service.sap.com/sizing Sizing Guidelines General Sizing Procedures .This section explains the most important sizing terms, as these terms are used extensively in this

document.SizingSizing means determining the hardware requirements of an SAP application, such as the networkbandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware anddatabase is influenced by both business aspects and technological aspects. This means that thenumber of users using the various application components and the data load they put on the servermust be taken into account.

BenchmarkingSizing information can be determined using SAP Standard Application Benchmarks and scalabilitytests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizingrecommendations to customers by placing a substantial load upon a system during the testing of newhardware, system software components, and relational database management systems (RDBMS). Allperformance data relevant to the system, user, and business applications are monitored during abenchmark run and can be used to compare platforms.

SAPS The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes theperformance of a system configuration in the SAP environment. It is derived from the Sales andDistribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fullybusiness processed order line items per hour. (For more information about SAPS, seehttp://www.sap.com/benchmark Measuring in SAPS).

Initial SizingInitial sizing refers to the sizing approach that provides statements about platform-independentrequirements of the hardware resources necessary for representative, standard delivery SAP

applications. The initial sizing guidelines assume optimal system parameter settings, standard businessscenarios, and so on.

Expert SizingThis term refers to a sizing exercise where customer-specific data is being analyzed and used to putmore detail on the sizing result. The main objective is to determine the resource consumption ofcustomized content and applications (not SAP standard delivery) by comprehensive measurements. Formore information, see http://service.sap.com/sizing Sizing Guidelines General Sizing Procedures

Expert Sizing.

Configuration and System Landscaping Hardware resource and optimal system configuration greatly depend on the requirements of thecustomer-specific project. This includes the implementation of distribution, security, and high availabilitysolutions by different approaches using various third-party tools. In the case of high availability throughredundant resources, for example, the final resource requirements must be adjusted accordingly.There are some "best practices" which may be valid for a specific combination of operating system anddatabase. To provide guidance, SAP created the NetWeaver configuration guides(http://service.sap.com/instguides SAP NetWeaver ).

http://service.sap.com/sizing



http://service.sap.com/instguides








Copyright/Trademark

3. INITIAL SIZING - SETUPThis guide handles the sizing of 3 categories of BPC environments:

Category 1 – a medium sized implementation Category 2 – a large implementation Category 3 – a large enterprise deployment

For each of these environments, the guide will provide sizing for 3 different concurrent user numbers: 50concurrent users, 150 concurrent users and 300 concurrent users.

Note that “concurrent users” are users currently working on the system. This number is not to beconfused with “named users” – the total number of users that have access to the system.

So, in summary this guide will deliver sizing recommendations for nine use cases: Category 1 – a medium sized implementation with 50, 150 and 300 concurrent users Category 2 – a large implementation with 50, 150 and 300 concurrent users Category 3 – a large enterprise deployment with 50, 150 and 300 concurrent users

First the environment setup is discussed, then we discuss the types and activities of users and finallywe give two sizing tables for the nine sizing cases. The first table will exclude any use of web interface,the second table will show the numbers if you add the usage of the web interface.This is done, to provide a guideline for existing BPC customers that traditionally focus very much onExcel – without the web.

3.1 BPC Environment setup for the 3 sizing categories The table below describes of the 3 BPC environments: Category 1, 2 and 3, specifying for example, thenumber of dimensions and hierarchies, the data volume, the script logic complexity of the securitysetup. All these characteristic of the BPC environment impact the sizing.

*Script logic is considered as a parameter in the sizing tests and configured as a default feature:

Implementation Categories Category 1 Category 2 Category 3

Number of Dimensions 8 8 12

Max. Number of Dimension Members 1,000 50,000 100,000

Max. Number Dimension Hierarchies 1 1 2

Max. Number Dimension Hierarchy Levels 1 8 11

Max. Size of Dimension Property 10 30 60

Max. Number of Dimension Properties 1 10 100

Number of Member Access Profiles * Number of Access Rules 1*1 5*5 10*10

Number of Secured Dimensions 1 1 5Number of Transactional Data Records in theenvironment 10 million 50 million 100 million

Script Logic Complexity* Simple Simple Complex

Custom LogicComplexity Action Detail

Simple Allocations/Calculations Simple formulas by using keywords such as*WHEN/*ENDWHEN and simple allocation

Complex Allocations/Calculations Allocations with more members and formulas with moredata volume, Script with complex keywords such asLOOKUP




Copyright/Trademark

3.2 BPC User Profile definition and ActivitiesThe following table describes the different user profiles and the actions they perform in the BPCEnvironment along with the wait times before repeating the action.

User Profile Description User ActionsThink Time

Between CyclesRun Business Process Flow - Log on

- Refresh Process and Activities lists- Complete activity in place- Open an activity with a workspace- Switch activities- Log out

No think time

Change Work Status (Web Client) - Log on- Open a web input form- Change work status- Log out

5 Minute

Run Report (Web Client) - Log on

- Open a web report- Log out

5 Minute

User Input Data (Web Client) - Log on- Open a web input form- Send data and execute script logic- Log out

20 Minute

Change Work Status (EPM Addin Client) - Log on- Open document- Change work status- Log out

5 Minute

Run Report (EPM Addin Client ) - Log on- Open document- Log out

5 Minute

User Input Data (EPM Addin Client) - Log on- Open document- Send data and execute script logic- Log out

20 Minute

Process Dimension (Web Client) - Log on- Open Administration tab- Select a dimension- Select members of the selecteddimension- Modify values on the selectedmembers- Save and process- Log out

No think time

Upload Transactional Data(DataManager)

- Log on- Run package- Import transactional data from Flat filewithout default logic- Check the import- Log out

No think time

Transactional Data Transfer BetweenCubes (Data Manager)

- Log on- Run package- Import transactional data from InfoProvider without default logic- Check the import- Log out

No think time




Copyright/Trademark

These user profiles definitions are the same for all 3 categories. However the data they read and writevolumes differ per scenario:

4. INITIAL SIZING - RECOMMENDATIONSThe following section specifies the sizing recommendation for the 3 categories along the 3 differentusers counts (50, 150 and 300 concurrent users).

To determine the amount of hardware required pick the category that your project falls into and thenumber of concurrent users. The table below specifies the amount of SAPS, memory and disc space forthe application server and the database server.

Implementation Categories Category 1 Category 2 Category 3

Number of Baseline Records Read for Reporting (READRECORDS)

100,000 1,000,000 10,000,000

Number of User Input Records (WRITTEN RECORDS) 500 1,000 2,000

Number of Transactional Data Imported (DataManager) 10,000 10,000 10,000




Copyright/Trademark

4.1 Sizing when using EPM Add-in and Web frontendThe results are based on the following user profile distribution:

The system can be classified into the following 9 categories based on the above combination ofimplementation complexity and user profile distribution assumptions:

CategoryNumber ofConcurrent

Users

SAP NetWeaver ABAP Application Server(s) Database Server

CPURequirements

MemoryRequirements

DisksRequirements

CPURequirements

MemoryRequirements

DisksRequirements

CAT 1

50 1,200 SAPS 40 GB RAM 27 GB 1,030 SAPS 20 GB RAM 71 GB



CAT 2




CAT 3



300 Please contact SAP or your hardware partner

More than 300 concurrentusers or otherimplementation categories

Please contact SAP or your hardware partner

Number of Concurrent Users per Profile 50 150 300

Run Business Process Flow 5 15 30

Change Work Status (Web Client) 5 15 30

Run Report (Web Client) 10 30 60

User Input Data (Web Client) 6 20 40

Change Work Status (EPM Addin Client) 5 15 30

Run Report (EPM Addin Client ) 10 30 60

User Input Data (EPM Addin Client) 6 20 40

Process Dimension (Web Client) 1 1 2

Upload Transactional Data (DataManager) 1 2 5

Transactional Data Transfer Between Cubes (DataManager) 1 2 3




Copyright/Trademark

4.2 Sizing when using exclusively the EPM Add-in front-endHistorically most BPC customer have primarily used Excel interface without the web. This sectiondetails the sizing for this case.

Sizing is based on the following user profile distribution:

The system can be classified into the following 9 categories based on the above combination ofimplementation complexity and user profile distribution assumptions:

CategoryNumber ofConcurrent

Users

SAP NetWeaver ABAP Application Server(s) Database Server

CPURequirements

MemoryRequirements

DisksRequirements

CPURequirements

MemoryRequirements

DisksRequirements

CAT 1

50 350 SAPS 40 GB RAM 27 GB 445 SAPS 20 GB RAM 71 GB



CAT 2

50 4,200 SAPS 40 GB RAM 27 GB 900 SAPS 21 GB RAM 76 GB



CAT 3



300 Please contact SAP or your hardware partner

More than 300 concurrentusers or other

implementation categories

Please contact SAP or your hardware partner

Number of Concurrent Users per Profile 50 150 300

Change Work Status (EPM Addin Client) 10 30 60

Run Report (EPM Addin Client ) 23 68 140

User Input Data (EPM Addin Client) 14 47 90

Process Dimension (Web Client) 1 1 2

Upload Transactional Data (DataManager) 1 2 5

Transactional Data Transfer Between Cubes (DataManager) 1 2 3




Copyright/Trademark

5. COMMENTS AND FEEDBACKThis is a first release of SAP BusinessObjects Planning and Consolidation 10.0, version for SAPNetWeaver. Your feedback is appreciated.Please send your feedback and comments to: Tsai, Albert [email protected].

mailto:[email protected]

mailto:[email protected]

Documents

SAP BPC 10 Sizing Guide.pdf