Sizing Guide Document Version: 2.0 2015-03-27
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. Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/sizing. 2 2015 SAP SE. All rights reserved. Disclaimer
Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> EXAMPLE Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. Typographic Conventions 2015 SAP SE. All rights reserved. 3
Document History Version Date Change 1.0 July 2012 Initial Version 2.0 March 2015 Update of Guide Layout Section 3.2: Additional Paragraph about Shared Memory Requirements 4 2015 SAP SE. All rights reserved. Document History
Table of Contents 1 Introduction... 6 1.1 Functions of SAP Quality Issue Management...6 1.2 Architecture of SAP Quality Issue Management...6 2 Sizing Fundamentals and Terminology... 9 3 Initial Sizing for SAP Quality Issue Management... 10 3.1 Assumptions... 10 3.2 Sizing Guideline... 10 4 Comments and Feedback... 12 Table of Contents 2015 SAP SE. All rights reserved. 5
1 Introduction SAP Quality Issue Management provides a highly flexible and fully auditable solution for dealing with qualityrelated activity management. Nearly all companies, whether in manufacturing, service industries or others, deal with quality-related issues and activities in different business areas. SAP Quality Issue Management is SAP s answer to these requirements 1.1 Functions of SAP Quality Issue Management SAP Quality Issue Management provides a way of managing various quality problems. Specifically, it helps with identifying quality issues, introducing quality measures, monitoring the processing status as issues are dealt with, and evaluating the resolutions. It offers the following advantages: An integrated solution: a central entry point for the processing and monitoring of quality problems, including those from other applications and systems, for example, FMEA, audits, quality reports, and claims Intuitive operation: Web-based, customizable user interface Standardized processes: for dealing with problems such as rule-based determination of partners, codes and policies Analytical capabilities: application and system boundaries Documentation: covering the solving process and resulting in improved cost control 1.2 Architecture of SAP Quality Issue Management This section provides an overview of the architecture of SAP Quality Issues Management, specifically describing which business scenario uses which software unit. For the latest component version and patch level requirements, see http://service.sap.com/sp-stacks. There are three deployment scenarios for SAP Quality Issue Management: your installation depends on which scenario you choose. 6 2015 SAP SE. All rights reserved. Introduction
You can use SAP Quality Issue Management in the following scenarios: Standalone: SAP Quality Issue Management as a standalone solution Side-by-side with SAP ERP: SAP Quality Issue Management as a standalone solution parallel to an existing system. In this variant of SAP Quality Issue Management and SAP ERP running on separate systems. The systems communicate via RFC connections or services Add-on: SAP Quality Issue Management as a complementary solution to an existing system, for example, SAP ERP. In this variant of SAP Quality Issue Management and SAP ERP running on the same system. You can use the master and organizational data base of SAP ERP. Table 1: Software Component Matrix Deployment Scenario SAP QIM ADS SAP BS FND 731 SAP NetWeaver AS ABAP 731 SAP ERP 4.6C SAP ERP 6 incl EHP 6 SAP Solution Manager SAP QIM as a standalone system X X X X - - X SAP QIM side by side with SAP ERP X X X X X minimal scope* (X) full scope* X SAP QIM as add-on X X X X (X)** (X)** X Key: X = mandatory (X) = optional * For more information, see SAP Library for SAP QIM under http://help.sap.com/qim100 Application Help Use of SAP QIM Connection of Systems in a Side-by-Side Scenario. ** As a prerequisite, the SAP ERP system must at least be based on SAP NetWeaver AS ABAP 731. Introduction 2015 SAP SE. All rights reserved. 7
Figure 1: Typical System Landscape Components Within a typical system landscape, you do not need a separate system for SAP Quality Issue Management. Instead you can install it on any suite system preferably on SAP ERP with SAP NetWeaver Application Server ABAP 731 underneath. Communication between Back and Front Ends The communication between back end and front end is HTTP. The applications are accessed from the front end by using the SAP NetWeaver Business Client (NWBC). Communication with Other SAP Systems You can communicate with other Suite systems using remote function calls (RFCs) or Enterprise Services. SAP Solution Manager is useful for installing IAM and connecting to different systems. Prerequisites You need ADS if you want to print documents such as issue reports. For more information, see the SAP NetWeaver Library under Configuration of Adobe Document Services for Print Applications. 8 2015 SAP SE. All rights reserved. Introduction
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 at service.sap.com/sizing Sizing Guidelines Presentations and Articles. This section explains the most important sizing terms, as these terms are used extensively in this document. Sizing Sizing means determining the hardware requirements of an SAP application, such as network bandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware and database is influenced by both business aspects and technological aspects. This means that the number of users using the various application components and the data load they put on the server must be taken into account. Benchmarking Sizing information can be determined using SAP Standard Application Benchmarks (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizing recommendations to customers by placing a substantial load upon a system during the testing of new hardware, system software components, and relational database management systems (RDBMS). All performance data relevant to the system, user, and business applications are monitored during a benchmark run and can be used to compare platforms. SAPS The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fully business processed order line items per hour. (For more information about SAPS, see www.sap.com/benchmark Measuring in SAPS). Initial Sizing Initial sizing refers to the sizing approach that provides statements about platform-independent requirements of the hardware resources necessary for representative, standard delivery SAP applications. The initial sizing guidelines assume optimal system parameter settings, standard business scenarios, and so on. Expert Sizing This term refers to a sizing exercise where customer-specific data is being analyzed and used to put more detail on the sizing result. The main objective is to determine the resource consumption of customized content and applications (not SAP standard delivery) by comprehensive measurements. More information can be found here. Configuration and System Landscaping Hardware resource and optimal system configuration greatly depend on the requirements of the customerspecific project. This includes the implementation of distribution, security, and high availability solutions by different approaches using various third-party tools. In the case of high availability through redundant resources, for example, the final resource requirements must be adjusted accordingly. There are best practices which may be valid for a specific combination of operating system and database. To provide guidance, SAP created NetWeaver configuration guides (service.sap.com/instguides SAP NetWeaver). Sizing Fundamentals and Terminology 2015 SAP SE. All rights reserved. 9
3 Initial Sizing for SAP Quality Issue Management 3.1 Assumptions The creation of an issue with 5 partners and 2 object assignments and 5 activities was taken as reference business process. 3.2 Sizing Guideline Categories Small: 10 business processes per hour by 20 users Medium: 50 business processes per hour by 100 users Large: 100 business processes per hour by 200 users Assumptions Users work 8 hours/day Average working days: 200 Data remains 2 years in the database Table 2 Category for Enterprises CPU Requirements Memory Requirements Disk Requirements Small 41 SAPS 3 GB RAM 2 GB Disk Medium 205 SAPS 6 GB RAM 7 GB Disk Large 410 SAPS 9 GB RAM 13 GB Disk X-Large (more than 700 users) Please contact SAP or your hardware partner Formulas o CPU in SAPS = Number of Issues created per hour * 4,1 SAPS o Memory in MB = Parallel Users * 36 MB + 2000 MB o Disk Size in MB = 0,040 MB * Objects per Year * Retention period in years (until deletion) o Required Space on Frontend = 20 kb 10 2015 SAP SE. All rights reserved. Initial Sizing for SAP Quality Issue Management
Shared Memory Requirements We recommend to make the following shared memory parameter settings per application server (independent from the above mentioned categories): abap/shared_object_size_mb = 40 Initial Sizing for SAP Quality Issue Management 2015 SAP SE. All rights reserved. 11
4 Comments and Feedback Both are very welcome; please send them to Holger Ulrich Eisele, Quality Issue Management. holger.ulrich.eisele@sap.com 12 2015 SAP SE. All rights reserved. Comments and Feedback
www.sap.com/contactsap 2015 SAP SE. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System ads, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, xapps, xapp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE 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 SE 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.