SAP Sizing Request Form

SAP Sizing Request Form

Dell | SAP Competence Center

Version: September 2004

Table of Contents

Introduction.................................................................................................................................3Contact Information.................................................................................................................5SAP Sizing Data within SAP’s Quicksizer..........................................................................6SAP Installation and Infrastructure Information............................................................7Sizing Enterprise Portals.........................................................................................................9Sizing SAP R/3, mySAP ERP, and R/3 Enterprise.........................................................10

User-Based Sizing...............................................................................................................10Transactional-Based Sizing.............................................................................................11

Sizing mySAP Supply Chain Management (APO)........................................................13Sizing mySAP BW (Business Intelligence Warehouse)..............................................16Sizing mySAP Customer Relationship Management.................................................17Sizing mySAP Supplier Relationship Management.....................................................18Sizing Industry-Based Solutions........................................................................................19

Sizing mySAP Insurance – Collections and Disbursement...................................19Sizing mySAP Utilities........................................................................................................21

Sizing Strategic Enterprise Management – Business Planning & Simulation...23

Dell Confidential Dell|SAP Sizing Request Form – Ver. September 2004 Page 2

Introduction

Sizing the architecture for a SAP implementation is vital to the success of a SAP implementation. Sizing is an iterative process and should be revisited as you make discoveries through the phases of your implementation.

There are two types of sizing that can be performed - a User-Based Sizing or a Transactional-Based sizing. It is best to provide both user information as well as transactional information to get the most accurate sizing result.

A user-Based sizing is typical in the beginning of a project, with the mix and usage of modules and users. Although a user-based sizing can be reflective of what will be seen by production go-live, it is best to re-visit the sizing with any updated information to verify that the original planned architecture is still valid. Once transaction information and other particulars are discovered through the various phases of the implementation, the sizing should be checked to determine if any of these discoveries require any changes in the architecture design.

The sizing information requested in this document is based on the most current SAP solutions and sizing methodology, as captured from SAP’s Quicksizer Tool. Customers that require a sizing for any other solution based on solutions not covered in this SAP Sizing Request Form should contact their Dell representative or send an email to [email protected] to get further information.

Dell thanks you for the opportunity to size an SAP environment to meet your needs based on the information provided above. Once you have had the opportunity to enter the relevant data on this form, please forward it to your Dell representative in order to get the requested sizing completed.

Should you not yet have a Dell contact, please attach this filled out sizing request form to an email and send it to the following email address for your region:

Americas: [email protected], Middle East and Africa: [email protected]: [email protected] Pacific Region: [email protected] : [email protected]

After receipt of your sizing request, a sizing will be performed and a sizing result sheet generated with the recommended hardware Dell Confidential Dell|SAP Sizing Request Form – Ver. September 2004

Page 3

mailto:[email protected]






configuration for this environment. Please provide your contact information below in case any discussion needs to occur to architect the optimal solution.

Should any questions arise with regard to your SAP sizing request, please refer to the following websites for more information:

http://www.dell.com/saphttp://service.sap.com

Alternatively, please contact your Dell representative or send an email to the regional address above.


http://service.sap.com/

http://www.dell.com/sap

Contact Information (How can we contact you?)

Company Name

CompanyAddress

City, State, & Zip

Phone Number

Fax Number

Pri

ma

ry C

on

tact

Contact Name

Contact Title

Primary Phone #

Email Address

Se

co

nd

ary

Contact Name

Contact Title

Primary Phone #

Email Address

Systems Integrator/Implementation Partner Information(Who’s helping you with the implementation?)

Systems Integrator/ Implementation PartnerPrimaryContact Name

PrimaryContact TitlePrimary Phone #

Secondary Phone #


SAP Sizing Data within SAP’s Quick Sizer

(If you have already done a sizing using SAP’s Quick Sizer, you can provide us the customer number and project name to save yourself time on completing the solution sections of this SAP sizing request form)

SAP Customer Number

Quick Sizer Project Name

If you have access to SAP’s Service Marketplace and have a S-User, you should be able to utilize SAP’s Quick Sizer tool. Completing the a Quick Sizer project is the most efficient manner in providing the necessary sizing input since it will allow you to have online help as well as always have the latest information from SAP.

You can access SAP’s Quick Sizer via http://service.sap.com/quicksizer


http://service.sap.com/quicksizer

SAP Installation and Infrastructure Information

(What are your implementation specifics?)

Operating System? (Windows2000, Windows2003, RedHat Linux, SuSe Linux, Heterogeneous with UNIX backend)

Database? (Oracle, SQL Server, DB2, Informix, MaxDB.)

Will you be implementing Unicode (Yes/No)?

SAP Project Start Date?

SAP “Go-Live” Date?

3 System Landscape (PRD, QAS, and DEV) or 2 System Landscape (PRD and combined DEV/QAS)?Also list any optional environments (Training, Staging, other)Number of Workdays per year?

Hours of Operation?

Current SAP Database size?

Legacy data to import? How much?

Interested in Fiber Channel or SCSI storage? Direct attach or SAN?

Interested in Database Clustering technology? (Yes/No)

Interested in Load Balancing technology? (Yes/No)

Interested in Complete Highly Available Solution? (Yes/No)

Interested in maximum redundancy and fault tolerance? (e.g., RAID 1+0, dual components, etc.)?

Interested in a Centralized Tape Backup Solution? (Yes/No)

Backup and Restore Window?

Interested in Dell-SAP Services? (Yes/No)


Current Dell customer? If yes, name of Dell sales representative? (Yes/No)

Number of employees?(Overall)

Should sizing take into consideration ‘add-on’ products (e.g., ITS, ESS, etc.)? If yes, comments (user counts, # of hits, etc.)?

Other, general comments?


Sizing Enterprise PortalsVersion (i.e. EP5, EP6)

Logon PhaseHighest number of users who log on in parallel

UsageHighest number of concurrent portal users per hour

Content ManagementHow many clicks (in %) access Content Management

Highest number of search requests per hour

Enter any kind of additional information with regard to this project here.


Sizing SAP R/3, mySAP ERP, and R/3 Enterprise

Solution/Version (i.e. R/3 4.6C; R/3 Enterprise with WAS 6.x; mySAP ERP CC 5)

User-Based Sizing The users listed below should be CONCURRENT (active) users, not NAMED users. Not all active users have the same activity pattern, and are typically distributed across low, medium and high use for each of the modules.

SAP Application Module Low Users Medium Users High UsersFI Financial Accounting

FI-AA Asset Accounting

TR Treasury

CO Controlling

EC Enterprise Controlling

SD Sales and Distribution

MM Materials Management

LE-WM Warehouse Management

QM Quality Management

PM Plant Maintenance

CS Customer Service

PP Production Planning

PS Project System

PA Personnel Administration and Payroll Accounting

PA-PD Personnel Development

BC Basis Components

Totals by Type of User

Total Number of Users

Low User (Occasional User)An Occasional User is a user of the R/3 system who is logged-on to the system and consumes system resources. On average typically around 400 dialog steps (screen changes) are executed per week, which is equivalent to ten dialog steps an hour (assuming a work week of 40 hours) or every six minutes. This type of user should be used if the user accesses the system from time to time. Typically this type of user definition fits to information users or executives.

Medium User (Accountant / Clerk)A Medium User is a user of the R/3 System who is logged-on to the system and consumes system resources. On average typically around 4800 dialog steps (screen changes) are executed per week that is equivalent to 120 dialog steps an hour (assuming a work week of 40 hours) or every 30 seconds. This type of user should be used if the user accesses the system permanently and is working with the system on a regular basis. Typically this type of user definition fits to accountants, clerks or office personnel.

High User (Data Entry User / Telesales User / Power User)A High User is a user of the R/3 system who is logged-on to the system and consumes system resources. On average typically around 14400 dialog steps (screen changes) are executed per week that is equivalent to 360 dialog steps an hour (assuming a work week of 40 hours) or every 10 seconds. This type of user should be used if the user accesses the system permanently and is heavily and intensively working with the system on a regular


base. Typically, this type of user definition fits to users working in the telesales environment, data entry users or power users such as application developers.


Transactional-Based Sizing



Component and Object Number of Objects Created per Year

Sub-Object of the Object

Average Number of

Sub-Objects(Natural #’s Only)

Retention Period [Months

]

HIGHLOAD PHASE Object Changes (%)

Object Display (%)

Number of

Objects Created per Day

Execution Period[hh:00-hh:00]

FI Documents Line Items

FI-TV Receipts Line Items

TR Postings

CO Documents Line Items

CO-PA(Orders transferred from SD-SL)CO-PA(Billings transferred from SD-BIL)CO-PA(Documents transferred from FI)EC Reports Lines

EC-PCA Documents LinesSD Customer Inquiries Line items

SD-SLSSales Order

Line items

SD-BIL Invoices Line items

SD-POS-IN Sales Data/IDOCS

Line items

MM-PUR Purchase Orders Line Items

MM-IM Material Movements Line Items

LE-WM Transfer Orders Line Items

LE-SHPDelivery Notes & Goods Issue

Line items

QM Inspections Inspection Characteristics

PM Orders Components

CS Orders Components

PP-SOP Planned Orders Components

PP-SFC Production Orders Components

PS Projects WBS Elements

PS Networks

PS Activities

PT Time Data

BC Printed Documents

BWP Business Workplace Sub-Objects

BWP Internal Emails

BWP External Emails

Transactional Data (Batch Only)

Component and Object

DescriptionMaximum

No. of Objects

Execution Time Period [hh:00-

hh:00]

FI-AA Assets Depreciation

Number of Assets

CO-OM-OPA Order Settlement

Number of Orders Allocated per Period

CO-OM-OPA Overhead Rate

Number of Orders per Period with Overhead Rates

CO-OM Assessment Number of Sender-Receiver Relations for All Cycles

PA Employees Number of Employees

PT Time Evaluation Number of Processed Time Pairs

PY Payroll Average Number of Retro-Calculations per Payroll

MM Period Closer(until release 4.0)

Number of Materials

MRP Object Number of Planned Orders per Day

MRP Object Average Number of Components per BOMMRP Object Number of Purchase Order Line Items for

Reorder-Point Driven Materials per DayMRP Object Number of Purchase Order Line Items/Schedule

Lines for Non Reorder-Point Driven Materials per Day

MRP Object Size of Planning Horizon in DaysMRP Object Number of BOM Structure Changes per Day in %MRP Object Variant Configuration: Average Number of BOM

Components with Object Dependencies in %MRP Object How many orders use Lead Time Scheduling in

%


Sizing mySAP Supply Chain Management (APO)Version (i.e. 4.0)

DEMAND PLANNING Planning Area 1

Planning Area 2

Planning Area 3

Planning Area 4

Number of characteristics combinations

Number of key figures in planning horizon

Number of periods in planning horizon

Number of key figures in the historical horizon

Number of periods in the historical horizon

Total Number of key figures in entire horizon

Total Number of periods in entire horizon

Compression Index (0 = pessimistic – 10 = optimistic)

Number of compressed time series (optional) Listed as percentageNumber of periods in the compressed time series (optional) Number of planning versions in the InfoCube

Number of planning versions in the LiveCache

Characteristic combinations used for planning run in % of question 1 above

Execution period of planning run [hh:00-hh:00]

Users of Demand Planning

Users of Demand Planning – Working Hours [hh:00-hh:00]

MASTER DATANumber of location products

Total number of resources

Number of warehouse stocks

DIFFERENT TYPES OF ORDERS OR REQUISITIONS USED FOR PLANNING

Average Number of Objects in the Planning Horizon Average Number of Subcomponents per ObjectSales Order Delivery Schedules

Purchase orders or purchase requisitions

Delivery Schedules

Transfer orders Products (materials)

Forecast orders Time buckets

Planned orders with SNP production process models (PPMs)

Components

Operations


Operation steps (activities) per operation

Average number of planned orders and manufacturing orders with PP-PPMs

Components

Operations

Operation steps (activities) per operationAlternative resources per activityParallel capacity requirements per operation step

SUPPLY NETWORK PLANNING AND PRODUCTION PLANNING

Time Series Livecache In SNPNumber of location products

No. of key figures

No. of time buckets

Supply Network PlanningNumber of location products planned in heuristic planning runExecution period of the planning runs [hh:00-hh:00]

Users of Supply Network Planning

Users of Supply Network Planning – Working hours [hh:00-hh:00]Production Planning – Detailed SchedulingUsers of Planning Table (as additional load)

Users of Planning Table – Working hours [hh:00-hh:00]Number of objects displayed by graphical planning boardNumber if planning board calls per user in the execution periodAvailable To Promise (ATP) Objects

Number of ObjectsHighload Phase [hh:00-hh:00]

Number of ATP requests against warehouse stocks

Number of rule-based ATP requests per hour

Number of CTP requests per hour

Integration to SAP R/3 (integration of orders transferred to and from APO)

Number of Objects

Number of Line Items

Highload Phase [hh:00-hh:00]

Number of sales orders

Number of manufacturing orders

Number of purchase requisitions

Number of stock values


INVENTORY COLLABORATION HUB (ICH)Message Type

Number of Messages per year

Avg. Number of Products per Message(natural numbers)

Avg. Number of Periods per Product (natural numbers)

Retention Period in Months

Highest No. of Objects per Day

Execution Period [hh:00-hh:00]

Product Activity

Delivery Schedule

Advanced Shipment

Goods Receipt

ICH Users Working hours [hh:00 –

hh:00]

MiscellaneousNumber of planning versions (including active version)



Sizing mySAP BW (Business Intelligence Warehouse)

Version (i.e. 3.5)

User Activity Info Consumer (Low Activity )

Executive (Medium activity)

Power user (High Activity)

Enter the number of Business Warehouse users by type

Query DistributionQuery Type Reporting View

(in Percentage)OLAP Analysis (in Percentage)

Data Exploration (in Percentage)

Total(in Percentage)

Info Consumer (low activity)

80 20 0 100Executive User(medium activity)

50 50 0 100Power User(high activity)

0 0 100 100

Data UploadNumber of uploaded objects (taken from periodic runs below) Upload period in hours

Mark, if upload runs parallel to queries

INFOCUBEName Type Dimensions Key Figures Initial Load Periodic

LoadNo. of Periods

ODS OBJECTSName No. of Numeric

FieldsNo. of Character Fields

Initial Load Periodic Load No. of Periods



Sizing mySAP Customer Relationship Management

Version (i.e. 4.0)

Users Low Users Medium Users High UsersCRM Online - Sales orders

Low Users Medium Users High UsersCRM Online - Service transactions

Low Users Medium Users High UsersCRM Online - Opportunity Management

Low Users Medium Users High UsersCRM Online - Activity Management

Low Users Medium Users High UsersEnter below how many of the above users enter objects such as customer orders or opportunities using the Customer Interaction CenterCRM Online - Customer Interaction Center

Low Users Medium Users High Users

Catalog Browsing

Filling Shopping Cart & Ordering

Internet Sales users per hourI Users Low Users Medium Users

Parallel Logons

Mobile SalesI Users Low UsersMobile ServiceI Users Low Users



Average Number ofSub-Objects(Natural #’s Only)

Retention Period [Months]


Object Display (%)

Max Number of Objects Created per Day


Internet Sales Orders Line Items

Mobile Sales Orders Line Items

Customer Orders Line Items

Service orders Line Items

Customer Interaction CenterCallsOpportunity ManagementOpportunitiesActivity ManagementActivities




Sizing mySAP Supplier Relationship Management

Version (i.e. 2.0)






Object Display (%)



Classic ProcurementOrders

Line Items

Extended Classic Procurement & Standalone Procurement Orders

Line Items

Plan-Driven ProcurementOrders

Line Items

Supplier Enablement – MM Orders

Line Items

Supplier Enablement – EBP Orders

Line Items

Strategic Sourcing Bid Invitations

Line Items

Bid Responses



Sizing Industry-Based Solutions

Sizing mySAP Insurance – Collections and Disbursement

Release (i.e. 4.70)

Master DataTotal Number of Business Partners

Number of contract accounts

Number of insurance objects

Number of brokers

Avg. number of customers assigned to a broker

Sub-ledger DocumentsComponent and Object Number

of Objects Created per Year




Sub-ledger documentpostings

BP Line Items

GL Line Items

Sub-ledger documentpayments

GL Line Items

Batch ProcessesComponent and Object Number

of Objects Created per Year





Object Display (%)



Payment Plan TransferPayment Plan ExecutionPayment RunPayment LotDunning Line ItemsBroker Report item (transfer/post)Insurance Invoices Line ItemsAccount Statement Lines

Online Processes


Transaction Number of objects in Highload Phase

Execution Period[hh:00 – hh:00]

Display Account Balance



Sizing mySAP Utilities

Release (i.e. 4.72)

DIALOG PART ONE – Disk SizingTotal number of business partners

UsersTotal number of contracts

UsersNumber of contract accounts

UsersNumber of budget billings per year

UsersNumber of billing cycles per year

UsersEnter either budget billing amounts or partial billings per yearAverage number of billing lines per bill

UsersAverage number of print lines per bill

UsersNumber of overdue notices per year

Total number of cash security deposits

Number of meters in the network

Number of customer contacts per year

Posting relevant line items on a partial bill per contract

Posting relevant line items on a consumption bill per contractAdditional lines of information on a consumption bill per contractNumber of different taxed per contract

Retention period for the above objects in monthsUsers

DIALOG PART TWOObject Average number

created per yearCreated during highload phase

Customer-OverviewsUsers

Customer contactsUsers

Move-inUsers

Move-outUsers

Duration of highload phase for the above objects; mandatory, if you entered values for the highload phase

UsersBATCHNo. of business partners (equal to dialog input)

UsersMinimum no. of days to complete one batch cycle

UsersBatch processing interval Users




Sizing Strategic Enterprise Management – Business Planning & Simulation

Version (i.e. BPS 3.1)

User Group Definition Highload Phase of One HourMaximum no. of concurrent users by group

Avg. no of data records manipulated by one single planning step

No. of planning steps per user

Max no. of data records manipulated by one single planning step

Max no. of data records a user works with simultaneously

Group A 30000 06 60000 200000Group B 15000 12 30000 100000Group C 5000 30 10000 25000

