SAP SRM 7.

01 PPS: Introduction to Performance and Sizing for SRM Hub Deployment

SRM Development

Version 1.0 Abstract:

Status In process

Date February 10th, 2010

This document is intended as a high-level performance-tuning guide for SAP Supplier Relationship Management (SAP SRM). As such, it explains the relationship between business terms and performance, and provides recommendations on how to optimize the SAP SRM system landscape in order to achieve a high-performance setup. Although this document focuses primarily on SAP SRM 7.01, most of the recommendations can also be applied to previous releases of SAP SRM (in particular SAP SRM 7.0). This document recommends how to configure specific technical systems. However, it does not provide detailed tuning measures for all of these systems; for more information on this, refer to the related documentation for each specific system.

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

SAP SRM 7.01 PPS: Introduction to Performance and Sizing Introduction

Note: Throughout this document, the term performance refers to response time and throughput. For large business documents (that is, documents with more than 100 line items) SAP SRM 7.01 retains the high performance standards of the previous SAP SRM releases (SAP SRM 5.0 and SAP SRM 7.0). In addition, SAP SRM 7.01 uses less memory compared to the previous releases. However, in terms of sizing, SAP SRM 7.01 has specific system landscape requirements which depend on the employed business scenario. These system landscape requirements are greater than those of previous releases (see details below). This document briefly describes the following aspects that influence the overall SAP SRM system performance: Business attributes Technical attributes Configuration

Business Attributes
Although performance is based primarily on technical system attributes, such as CPU speed, memory size, network speed, or database, it is important to note that for SAP SRM, business attributes also greatly influence performance. SAP SRM performs best when it is used within certain ideal parameters,1 which are primarily (but not solely) determined by the size of the business documents the user is processing. The size of a document is determined primarily (again, not solely) by the number of line items it contains. For the contract business-document, the document size should not exceed 500 to 1000 line items depending on the used PPS functionality. For all other business documents, for example, shopping cart (SC), purchase order (PO), or RFx, business documents that contain up to 200 line items give the best performance. Please be aware that this recommendation is based on a standard usage of the below mentioned business attributes (e.g. 1000 line items, 1 condition, 1 Distribution, 1 small attachment, 1 Partner). Hierarchies should not exceed 5 levels. If your requirements go beyond that recommendation - please contact SAP consulting for further advice. Furthermore you should consider a hardware setup with CPUs that give best single thread performance. In addition to the number of line items, the following business-related attributes (apart from the more technical system landscape attributes) influence the performance of SAP SRM transactions:

Business Attribute Number of partners for each line item

Affected Business Document o o o o Shopping cart Purchase order RFx Confirmation

All figures provided in this document (in particular document sizes outlined for the ideal parameters) should be used as a point of reference only. They can be achieved only in an ideal technical system setup. For example, in the case of business scenarios performance, all involved business documents need to be considered; for functions such as Renegotiate (which create an RFx from a contract) or Update Contract from RFx, performance is best for documents that contain up to 500 line items.

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Version: 1.0 Date: November 24th, 2008

Page 2 of 6

SAP SRM 7.01 PPS: Introduction to Performance and Sizing

Number of pricing condition records (particularly when combined with a high number of line items) Attachments of more than 10 MB (this also depends on the number of attachments per document) Pricing (particularly when combined with a high number of line items) Tax calculation (particularly when combined with a high number of line items) Distributions (particularly when combined with a high number of line items) o o o Contract RFx All business documents

o o o o o

Shopping cart Purchase order Shopping cart Purchase order Contract

Note: Only the most important influencing factors are included in the table above. If you need to process very large business documents, we recommend that you take the following measures: Where possible, divide the business documents into several smaller business documents. Start with the business process in SAP ERP. Change time-consuming interactive steps into background process steps. The threshold values for background processing are available (in Customizing) for the following steps: o Contract: check, save, release, copy, renew, print preview, export, import, , delete, close, version comparison, negotiate, lock, unlock, change currency o RFx: check, save, publish, refresh, export, import, copy, follow up, copy template, create from template, create purchase order from bid, create contract from bid, update contract from bid, print preview o RFx response: download, upload, print preview, check, save, copy, refresh, export, import, delete, version comparison, document creation from response, simulate document creation from response, publish to catalog o PO: check, save, order, copy, print preview, refresh, export, import, delete, close, version comparison The performance of a business process is influenced by the deployed business integration scenario ( Classic or Extended). In particular, for the Extended and Classic business integration scenarios, the integration points between SAP ERP and SAP SRM are crucial for good system performance. Business attributes, such as document size, in conjunction with technical parameters, such as network speed and performance of the connected ERP systems, are a determining factor in the overall system performance.

Technical Attributes
In order to tune the technical attributes of the SAP SRM system landscape, you must take the following influencing factors into consideration: Servers (application server, data base server, etc.) Integration of servers (network throughput and latency, LAN, WAN)

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Version: 1.0 Date: November 24th, 2008

Page 3 of 6

SAP SRM 7.01 PPS: Introduction to Performance and Sizing

Users workstations The following servers (all belonging to the SAP SRM system landscape) must be considered for tuning. Note: The precise set of servers depends on which business scenario you are using; for example, Process Integration (PI) is mandatory for the newly-introduced Service Procurement scenario. Adobe Document Server (ADS) o Required for printing Enterprise Portal o This is a mandatory component. Existing portal installations can be re-used, in particular, Java Enterprise Edition (JEE) server settings and optimized portal content. SRM MDM Catalog including Master Data Management (MDM) Process Integration (PI) o Required for the scenarios Plan-Driven Procurement with Plant Maintenance and Service Procurement TREX o Required for Enterprise Search SRM ABAP and database server o For example, buffers and caches, number of work processes (available memory), database parameters and statistics ERP server(s) As indicated above, the integration of SAP SRM within its system landscape plays a crucial part in maintaining a high level of performance. Depending on the employed business scenarios, the following integration points should be tuned: Internet Pricing Configurator/Virtual Machine Container (IPC/VMC) settings settings for IPC Gateway setting Remote Function Call (RFC) communication (synchronous, asynchronous communication) influence all scenarios except local SAP SRM transactions especially for high volumes of business documents. Network latencies and low throughput significantly reduces system performance and end-to-end response time, especially if the system landscape is distributed and/or separated by firewalls or WAN segments. The performance of the system for the end user is influenced by the users workstation. In particular, the following factors play a significant role: Network/firewalls o Network latencies in WAN can cause a significant reduction in the performance of browser response times End-user machine or workstation setup: o CPU speed and memory size o Online anti-virus software performing JavaScript scanning o Other resource-consuming software and/or IP traffic-influencing measures Browser o Be aware of the browser cache settings in order to avoid unnecessary lookups to the server

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Version: 1.0 Date: November 24th, 2008

Page 4 of 6

SAP SRM 7.01 PPS: Introduction to Performance and Sizing

The following figure gives an overview of the technical parameters discussed above.

Sizing Configuration CPU Memory Virus scanner Portal content

BADI implementations

Network Latencies Network Topology WAN quality

Profile Parameters Database Paramters & Statistics Gateway Parameters Buffers & Caches

Conclusion
Finally, to further optimize the system landscape for high volumes of concurrent users and documents, you should consider the following: The restricting factor for the number of concurrent users is the available physical memory. Because of this, you must specify carefully the session timeout settings in order to optimize the overall memory consumption. For optimal throughput of all approval processes, you should enable queued event-processing for the SAP business workflow. When sizing the database and hardware, consider high data volumes and do not rely solely on Quick Sizer sizing (see Note below). The number of items in the database (table CRMD_ORDERADM_I and subsequent) should be kept as small as possible by doing regular archiving of business documents and work items. Note: SAP provides Quick Sizer to support the sizing of server hardware. However, depending on the specific performance requirements and system setup, it is not sufficient to rely solely on Quick Sizer. For example customer-specific BADIs or high-end load requirements are not covered. For additional help, contact the CoE (Center of Excellence) service.

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Version: 1.0 Date: November 24th, 2008

Page 5 of 6

SAP SRM 7.01 PPS: Introduction to Performance and Sizing

This document is complemented with up-to-date information in customer note 1266771 (specifically for portal 1180648) which contains some general performance hints, as well as a collection of all performance-relevant notes. References: SAP Performance Optimization Guide (5th Edition) 624 pages ISBN 978-1-59229-202-8

2010 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Version: 1.0 Date: November 24th, 2008

Page 6 of 6