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

Sizing Guide

Sizing CRM Billing, SAP CRM 7.0 EhP2

Released for SAP Customers and Partners Document Version 2.0, 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, Excel, Outlook, PowerPoint, Silverlight, and

Visual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, z10, z/VM, z/OS,

OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems,

POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale,

PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,

Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United

States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are

trademarks or registered trademarks of Adobe Systems Incorporated

in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-

Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or

registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry

Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2,

BlackBerry PlayBook, and BlackBerry App World are trademarks or

registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data

API, Google Maps, Google Mobile Ads, Google Mobile Updater,

Google Mobile, Google Store, Google Sync, Google Updater, Google

Voice, Google Mail, Gmail, YouTube, Dalvik and Android are

trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies

Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings

LLC.

Computop is a registered trademark of Computop

Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of

Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate is an SAP company.

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

__________________________________________________________________________________

1 Sizing SAP CRM Billing - SAP Customers and Partners

TABLE OF CONTENTS 1. Introduction .................................................................................................................................. 1 1.1 Functions of SAP CRM Billing ............................................................................................................. 1 1.2 Architecture of SAP CRM Billing .......................................................................................................... 1 1.3 Factors that influence the performance ............................................................................................... 2 2. Sizing Fundamentals and Terminology ..................................................................................... 3 3. Initial Sizing for SAP CRM Billing ............................................................................................... 4 3.1 Assumptions ......................................................................................................................................... 4 3.2 Sizing guideline .................................................................................................................................... 4 4. Miscellaneous ............................................................................................................................... 7 5. Comments and Feedback............................................................................................................ 7

1. INTRODUCTION

The billing application in SAP Customer Relationship Management (SAP CRM) is used for invoicing with the service and sales processes to create collective billing documents for various transactions including service orders, service contracts, complaints, and sales with corresponding deliveries. It is used in business scenarios integrated into account receivables and contract accounting. The billing application in SAP CRM can be used for settlement of claims in SAP Trade Promotion Management (SAP TPM) and market development funds (MDF) if this function is required. The proposed sizing guidance provides initial figures for customers regarding the performance of resources necessary to execute mass billing in the background processing mode.

1.1 Functions of SAP CRM Billing

Billing of a SAP CRM transaction, for example, service contracts, includes the following main capabilities:

A collective run process that selects the relevant transactions and creates collective billing documents

Pricing with or without document-related discounting and tax calculation

Determining the output process of invoices, for example, by printout or electronic data interchange (EDI)

Transferring billing documents to the accounting (FI-AR) and controlling (CO-PA, EC-PCA) components

Updating the business intelligence (BI) content with the extraction of invoice data

Updating financial credit management

Updating CRM order transactions, for example, service contracts, with the invoices amount and quantity, and the reference to the related invoice (document flow)

Updating applications for CRM order transactions, including;

o BI content of CRM order transactions

o Mobile sales devices

o Financial credit management

If the settlement of trade claims option is used, the following processes are also executed in addition to the process steps above;

Integration into the funds management system

Funds availability check

There are other scenarios supported by the billing application in SAP CRM, such as delivery-related billing of sales orders and the necessary follow-up activities not specifically considered in this sizing guide.

1.2 Architecture of SAP CRM Billing

The billing application in SAP CRM consists of two main components:

CRM billing due list

CRM billing document

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

2 2

SAP AG 2005, SAP CRM 5.0 – Sales, 8 of 40

OutputPrinter

and mail

Transfer SAP

FI/CO

Extract SAP BW

ConnectOther

appl.

Transaction

Delivery

Externaldata

Process Overview

The billing process comprises three main steps:

Input processing – loading data into billing due list

Billing – creating billing documents

Output processing

Input processing Billing

OutputprocessingBilling

due

list

Billing

docu-

ments

Graphic 1: Architecture of CRM Billing

CRM Billing Due List and Input Processing

The CRM billing due list is the object responsible for capturing billing-relevant transactions within the billing application in SAP CRM. It consists of a major database container with the capability of referencing dependent information on prices, partners, and notes. The CRM billing due list is the entry point for the selected transaction being billed and the basis for the mass billing run, which is typically executed by the system in the background.

CRM Billing Document and Billing Process

The CRM billing document is the object created during the billing run to structure customer invoices. It carries information about prices and tax, partners, notes, and the corresponding action for triggering output processing.

Output Processing of CRM Billing and follow-up Integration

CRM billing documents are typically built jointly for a large number of transactions for a given set of customers. The documents are populated using a messaging BDOC via CRM middleware to perform follow-up activities, such as:

o Transferring information to the accounting component of SAP ERP

o Updating SAP NetWeaver Business Warehouse (SAP NetWeaver BI) content

o Updating corresponding CRM order transactions, for example, service contracts

o Updating financial credit management or mobile sales devices

1.3 Factors that influence the performance

The following key factors influence the performance of the billing process:

The structure and size (number of items) of the billing document resulting from the transactions that are billed jointly.

The numbers of billing-relevant transactions that are related to a business partner in the CRM system, especially when a selected sold-to party owns a small or large number of transactions.

For a recommendation about how to configure the billing engine in SAP CRM for small and large numbers of transactions, see SAP Note 1133857.

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

3 3

The functions in use, for example:

o Pricing and tax calculation

o Output determination

o Funds availability check

o Rebates integration

The duration for the execution of the billing process can be optimized by running parallel batch jobs. To enable batch processing, billing must be started with the transaction ‘Schedule Batch Jobs’ (/BEA/CRMB06). Assuming the billing run is executed with 16 jobs in parallel, the throughput can potentially be increased by the factor 16 if the number of SAP application performance standards (SAPS) also increased by a factor of 16.

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 http://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.

Sizing Sizing means determining the hardware requirements of an SAP application, such as the 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 and scalability tests (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 http://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. For more 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 the customer-specific 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.

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

4 4

There are some "best practices" which may be valid for a specific combination of operating system and database. To provide guidance, SAP created the NetWeaver configuration guides (http://service.sap.com/instguides SAP NetWeaver).

3. INITIAL SIZING FOR SAP CRM BILLING

This sizing guideline provides information about the resources necessary at runtime for SAP CRM. The necessary runtime of SAP ECC is not considered. The given sizing guidance only covers aspects of the billing process and output processing. The sizing of input processing (e.g. updating the billing due list) is not considered in this document.

3.1 Assumptions

Integration Assumptions for Billing Processing The following assumptions regarding processing of billing documents are valid for the sizing measurements:

The collective run process, which selects the relevant transactions and creates the collective billing documents

Pricing is performed without tax calculation

Automatic transfer of the billing documents to accounting in ECC is activated

Extraction of the invoice data for updating the BI content

Update of financial credit management

Update of the CRM business transactions with invoice status

Update of the CRM business transactions to the following consuming applications:

o BI: Extraction of the invoiced business transactions for updating the SAP NetWeaver BI content

o Notify mobile sales devices

o Update financial credit management

Configuration Assumptions for Billing Processing The sizing guideline for the billing process is based on the background execution of the process as a batch job. The billing application in SAP CRM has the initial default configuration, including the following settings:

Tax calculation is deactivated

Text determination on header and item level is deactivated

Determination of actions for output determination is activated

Account determination is based on the simple account determination

Update of rebate processing is deactivated

Assumptions on Data Volumes Calculation of billing items as an example for service contracts: A typical service contract has the duration of 12 periods for each contract item. Depending on the structure of the service contract, there will be a respective number of billing request Items, for example, a service contract of 25 items will contain 12*25 = 300 billing request items. The enhancement to replace billing request items for periodic billing plans by an item extension, where each extension line is representing a period to be billed, is not used in the example calculation above. This new feature is available with CRM 7.0 EHP1.

3.2 Sizing guideline

The hardware resources required to process a set of billing documents depends on the following information:

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

5 5

The number of documents

The average number of items in one document

The definition of the affordable duration for the billing run

Relevant parameters:

N_docs – Number of documents which need to be processed in one schedule

AVG_items – Average number of items in each document

P – Time in hours in which the processing of all documents should be completed

If the customer has a large deviation in the number of items in each document, a more precise calculation may be achieved by grouping documents with similar characteristics and performing a separate calculation for each group and then adding the totals for all groups to obtain the sizing of the final resource consumption. CPU Sizing In the following T-shirt sizing the same amount of documents with a different amount of average items per document is planned for processing within 1 hour or within 5 hours.

1

Categories N_docs AVG_items P [hours] SAPS ABAP SAPS DB

S 1000 2 1 380 190

1000 50 1 2120 500

1000 50 5 430 100

M 2500 2 1 930 460

2500 50 1 5290 1250

2500 50 5 1060 250

L 25.000 2 1 9270 4560

25.000 50 1 52,900 12,500

25.000 50 5 10,600 2500

XL Please contact SAP or hardware partner

As seen in the table, the period of time for the execution (P) of billing processing dominates the resource calculation for SAPS compared to the other two parameters in the sizing formula (please compare the lines in bold italic). For this reason the SAP recommendation is: if there is no specific use-case at the customer for very fast processing of huge billing document volumes, a reasonable planning for the duration might significantly save expenses on hardware resources. Sizing for Posting of Billing Documents in ECC CRM billing documents are populated via a messaging BDOC utilizing the CRM Middleware to fulfill the follow up activities like Transfer to ECC and posting of Accounting documents in ECC.

1 Usually there are two different users which are involved in the processing of Billing document – the user who triggers the billing

and the technical user who runs the RFC calls to the ECC system. The following formulas are used to calculate the number of SAPS for the CPU of the Application Server [ABAP] and DB Server. Please note that the numbers in the sizing table were rounded: User who triggers the billing process

SAPS (ABAP) = N_docs*(589,97+( AVG_items *83))/(0,65*P*3600)

SAPS (DB) = N_docs * (332,56 + AVG_items *15,37) / (0,65 * P * 3600 ) User for RFC communication with ECC System

SAPS (ABAP) = N_docs*(107,63+( AVG_items *2))/(0,65*P*3600)

SAPS (DB) = N_docs * (62,94 + AVG_items *0,05) / (0,65 * P * 3600 ) Note: For sizing scenarios the CPU utilization is always defined as 65%. This factor is applied because the system load might be influenced by other system activities and dialog processes running in parallel.

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

6 6

To each Billing Document a corresponding single Financial Accounting document is created with at least 2 items. The number of items in the Financial Accounting document depends on the customizing setting for the Revenue and Tax Account Determination. In order to calculate the additional resource consumption for posting of the corresponding accounting documents in ECC please use the following Quick Sizer scenario available on SAP Service Marketplace: http://service.sap.com/sap/bc/bsp/spn/quicksizer/main.do?sap-language=en&bsp-language=en

1. Create a new sizing project 2. Goto ‘SAP Business Suite’ - ‘SAP ERP’ - ‘Financials’ 3. Goto ‘Throughput - Standard Sizing’ 4. Use sizing element ‘FIN-BAC’ [Business Accounting Documents] 5. Enter the relevant average number of accounting documents per year, average number of

items, percentage of changes and displays. 6. Press button ‘Calculate Results’

Check results, e.g. number of SAPS, memory, disk space 7. Press button ‘Save’

The resources required on the SAP ERP side for posting of accounting documents must also be considered. Memory Sizing The memory demand for executing the processes in billing engine in SAP CRM depends on creating batch jobs for the task over multiple ABAP work processes. Relevant additional parameter:

Nwp = number of configured work processes for parallel execution of Billing processes

The batch jobs can be determined only when it is known how many CPUs/cores will be available on the planned CRM server for billing processing. The maximum number of work processes involved in billing processing should not exceed the configuration of the number of available CPU cores on the ABAP side. In the following example the same amount of average items per billing is processed with a different number of parallel work processes:

AVG_items Nwp Memory in MB [ABAP]2

25 1 28

25 5 140

The resulting memory should be planned on top of the memory which is required by ABAP system. The optimal memory of the database server should be planned according to DB Vendor rules. Disk Sizing Initial sizing of the required disk space considers the total content of the database of application data. Initial disk sizing results do not include disk space for database log files or temporarily needed disk space for reorganization, backup, or any other database administration task. It does not include disk space needed for operating system itself, for example, swap space. The disk space calculation is the total disk space needed to store the information for the billing documents created during the billing run. The disk space sizing is relevant for the disks of the database Relevant additional parameter:

2 The following formula is used to calculate the memory consumption for billing processes. Please note that the numbers in the

table were rounded: User who triggers the billing process

Memory in MB (ABAP) = Nwp * (12 + AVG_items * 0.5) User for RFC communication with ECC System

Memory in MB (ABAP) = Nwp * (3 + AVG_items * 0.02)

Sizing SAP CRM Billing - SAP Customers and Partners __________________________________________________________________________________

Copyright/Trademark

7 7

N_total_docs = total amount of documents which will be created over a certain period of time (e.g. months, year) until data archiving for the stored documents is planned

Disk size calculation for different number of billing documents and different number of average items per document

N_docs AVG_items Number of Items Disk [GB]3

2.000.000 5 10.000.000 37.1

1.000.000 10 10.000.000 35.3

400.000 25 10.000.000 34.2

100.000 100 10.000.000 33.6

To obtain the final disk space, the sum of all billing documents which reside in the database at once has to be calculated. This quantity depends on the residence time of the billing documents, that is, the time until completed billing documents will be taken out of the database after data archiving. Note: If tax calculation is executed during the billing engine run, you must include 3,378 bytes of additional disk space for each billing document, which is the required disk space for tax documents.

4. MISCELLANEOUS

The sizing guidance is valid for all types of billing-relevant transactions, including service or sales orders with deliveries, complaints and claims.

5. COMMENTS AND FEEDBACK

Comments and feedback on this document are highly appreciated. Please use the SAP Support Portal https://service.sap.com/support and create an OSS ticket for component CRM-BE.

3 The following formula is used to calculate the disk size for billing documents. .Please note that the numbers in the table were

rounded

Disk space [GB] = N_total_docs * (0.0019 + AVG_items * 0.0034) / 1024