0% found this document useful (0 votes)
965 views

SAP Sizing Request Form

This document is a SAP sizing request form used by Dell to collect information needed to size a customer's SAP implementation. It requests details about the customer's SAP solution, modules, users, infrastructure, implementation timeline and more. The form is used to perform a user-based or transaction-based sizing of the required hardware configuration. Once completed, the customer submits it to Dell to generate a sizing results sheet with hardware recommendations.

Uploaded by

Pooya Ranjbar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
965 views

SAP Sizing Request Form

This document is a SAP sizing request form used by Dell to collect information needed to size a customer's SAP implementation. It requests details about the customer's SAP solution, modules, users, infrastructure, implementation timeline and more. The form is used to perform a user-based or transaction-based sizing of the required hardware configuration. Once completed, the customer submits it to Dell to generate a sizing results sheet with hardware recommendations.

Uploaded by

Pooya Ranjbar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 25

SAP Sizing Request Form

Dell | SAP Competence Center


Version: September 2004
Table of Contents

Introduction......................................................................................................................................3
Contact Information.........................................................................................................................5
SAP Sizing Data within SAP’s Quick Sizer....................................................................................6
SAP Installation and Infrastructure Information..............................................................................7
Sizing Enterprise Portals..................................................................................................................9
Sizing SAP R/3, mySAP ERP, and R/3 Enterprise.......................................................................10
User-Based Sizing .....................................................................................................................10
Transactional-Based Sizing.......................................................................................................11
Sizing mySAP Supply Chain Management (APO).......................................................................14
Sizing mySAP BW (Business Intelligence Warehouse)................................................................17
Sizing mySAP Customer Relationship Management...................................................................18
Sizing mySAP Supplier Relationship Management......................................................................20
Sizing Industry-Based Solutions....................................................................................................21
Sizing mySAP Insurance – Collections and Disbursement.......................................................21
Sizing mySAP Utilities..............................................................................................................23
Sizing Strategic Enterprise Management – Business Planning & Simulation...............................25

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
sap_sizing@dell.com 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: sap_sizing@dell.com
Europe, Middle East and Africa: sap_cc_walldorf@dell.com
Japan: JP_sap_sizing@dell.com
Asia Pacific Region: sap_sizing@dell.com
China : china_sap_sizing@dell.com

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

Alternatively, please contact your Dell representative or send an email


to the regional address above.

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


Page 4
Contact Information
(How can we contact you?)

Company Name

Company
Address

City, State, & Zip

Phone Number

Fax Number

Contact Name
Primary Contact

Contact Title

Primary Phone #

Email Address

Contact Name
Secondary Contact

Contact Title

Primary Phone #

Email Address

Systems Integrator/Implementation Partner Information


(Who’s helping you with the implementation?)

Systems Integrator/
Implementation
Partner
Primary
Contact Name

Primary
Contact Title
Primary Phone #

Secondary Phone #

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


Page 5
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

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


Page 6
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)
Dell Confidential Dell|SAP Sizing Request Form – Ver. September 2004
Page 7
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?

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


Page 8
Sizing Enterprise Portals
Version (i.e. EP5, EP6)

Logon Phase
Highest number of users who log on in parallel

Usage
Highest number of concurrent portal users per hour

Content Management
How 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.

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


Page 9
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 Users


FI 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.
Dell Confidential Dell|SAP Sizing Request Form – Ver. September 2004
Page 10
Transactional-Based Sizing

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


Page 11
Component and Object Number Sub-Object Average Retentio HIGHLOAD PHASE Object Object
of Objects of the Number of n Period Number Executio Change Displa
Created Object Sub- [Months of n Period s (%) y (%)
per Year Objects ] Objects [hh:00-
(Natural Created hh:00]
#’s Only) per Day
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 Lines


SD Customer Inquiries Line items

SD-SLS Line items


Sales Order
SD-BIL Invoices Line items

SD-POS-IN Sales Data/ Line items


IDOCS
MM-PUR Purchase Orders Line Items

MM-IM Material Movements Line Items

LE-WM Transfer Orders Line Items

LE-SHP Line items


Delivery Notes & Goods Issue
QM Inspections Inspection
Characteristi
cs
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

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


Page 12
Transactional Data (Batch Only)

Maximum Execution Time


No. of Period [hh:00-
Component and Description Objects hh:00]
Object
FI-AA Assets Number of Assets
Depreciation

CO-OM-OPA Order Number of Orders Allocated per Period


Settlement

CO-OM-OPA Overhead Number of Orders per Period with Overhead


Rate 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 Number of Materials
(until release 4.0)

MRP Object Number of Planned Orders per Day


MRP Object Average Number of Components per BOM
MRP Object Number of Purchase Order Line Items for
Reorder-Point Driven Materials per Day
MRP Object Number of Purchase Order Line Items/Schedule
Lines for Non Reorder-Point Driven Materials per
Day
MRP Object Size of Planning Horizon in Days
MRP 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
%

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


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

DEMAND PLANNING Planning Planning Planning Planning


Area 1 Area 2 Area 3 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 percentage
Number 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 DATA
Number 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 Object
Sales Order Delivery Schedules

Purchase orders or Delivery Schedules


purchase requisitions
Transfer orders Products (materials)

Forecast orders Time buckets

Planned orders with SNP Components


production process
models (PPMs)
Operations

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


Page 14
Operation steps
(activities) per operation

Average number of Components


planned orders and
manufacturing orders
with PP-PPMs Operations

Operation steps
(activities) per operation
Alternative resources per
activity
Parallel capacity
requirements per
operation step

SUPPLY NETWORK PLANNING AND PRODUCTION PLANNING

Time Series Livecache In SNP


Number of location products

No. of key figures

No. of time buckets

Supply Network Planning


Number of location products planned in heuristic
planning run
Execution 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 Scheduling
Users of Planning Table (as additional load)

Users of Planning Table – Working hours


[hh:00-hh:00]
Number of objects displayed by graphical planning
board
Number if planning board calls per user in the
execution period
Available To Promise (ATP) Objects Highload Phase
Number of Objects [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 Number of Number of Highload Phase


transferred to and from APO) Objects Line Items [hh:00-hh:00]
Number of sales orders

Number of manufacturing orders

Number of purchase requisitions

Number of stock values

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


Page 15
INVENTORY COLLABORATION HUB (ICH)
Message Avg. Number Avg. Number
Type of Products of Periods per Retentio Highest
Number of per Message Product n Period No. of Execution
Messages (natural (natural in Objects per Period [hh:00-
per year numbers) numbers) Months Day hh:00]
Product
Activity

Delivery
Schedule

Advanced
Shipment

Goods
Receipt

ICH
Users Working hours [hh:00 –
hh:00]

Miscellaneous
Number of planning versions (including active
version)

Other, general comments?

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


Page 16
Sizing mySAP BW (Business Intelligence Warehouse)
Version (i.e. 3.5)

User Activity Executive


Info Consumer (Medium Power user
(Low Activity ) activity) (High Activity)
Enter the number of Business Warehouse users by
type

Query Distribution
Query Type Reporting View OLAP Analysis Data Exploration Total
(in Percentage) (in Percentage) (in Percentage) (in
Percentage)
Info Consumer
(low activity)
80 20 0 100
Executive User
(medium activity)
50 50 0 100
Power User
(high activity)
0 0 100 100

Data Upload
Number of uploaded objects Mark, if upload runs
(taken from periodic runs below) Upload period in hours parallel to queries

INFOCUBE
Name Type Dimensions Key Figures Initial Load Periodic No. of
Load Periods

ODS OBJECTS
Name No. of No. of Initial Load Periodic Load No. of
Numeric Fields Character Periods
Fields

Other, general comments?

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


Page 17
Sizing mySAP Customer Relationship Management
Version (i.e. 4.0)

Users Low Users Medium Users High Users


CRM Online - Sales orders
Low Users Medium Users High Users
CRM Online - Service transactions
Low Users Medium Users High Users
CRM Online - Opportunity Management
Low Users Medium Users High Users
CRM Online - Activity Management
Low Users Medium Users High Users
Enter below how many of the above users enter objects such as customer orders or opportunities using the
Customer Interaction Center
CRM Online - Customer Interaction Center
Low Users Medium Users High Users
Filling
Catalog Shopping Cart
Browsing & Ordering
Internet Sales users per hour
I Users Low Users Medium Users
Parallel
Logons
Mobile Sales
I Users Low Users
Mobile Service
I Users Low Users

Component and Object Number Sub- Average Retentio HIGHLOAD PHASE Object Object
of Objects Object of Number of n Period Max Executio Change Display
Created the Sub- [Months] Number n Period s (%) (%)
per Year Object Objects of [hh:00-
(Natural Objects hh:00]
#’s Only) Created
per Day
Internet Sales Orders Line Items

Mobile Sales Orders Line Items

Customer Orders Line Items

Service orders Line Items

Customer Interaction Center


Calls
Opportunity Management
Opportunities
Activity Management
Activities

Other, general comments?

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


Page 18
Dell Confidential Dell|SAP Sizing Request Form – Ver. September 2004
Page 19
Sizing mySAP Supplier Relationship Management
Version (i.e. 2.0)

Component and Object Number Sub- Average Retentio HIGHLOAD PHASE Object Object
of Objects Object of Number of n Period Max Executio Change Display
Created the Sub- [Months] Number n Period s (%) (%)
per Year Object Objects of [hh:00-
(Natural Objects hh:00]
#’s Only) Created
per Day
Classic Procurement Line Items
Orders
Extended Classic Line Items
Procurement & Standalone
Procurement Orders
Plan-Driven Procurement Line Items
Orders
Supplier Enablement – Line Items
MM Orders
Supplier Enablement – Line Items
EBP Orders
Strategic Sourcing Line Items
Bid Invitations
Bid Responses

Other, general comments?

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


Page 20
Sizing Industry-Based Solutions

Sizing mySAP Insurance – Collections and Disbursement

Release (i.e. 4.70)

Master Data
Total 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 Documents
Component and Object Number Sub- Average Number Retentio
of Objects Object of of n Period
Created the Object Sub-Objects [Months]
per Year (Natural #’s
Only)
BP Line
Sub-ledger document Items
postings
GL Line
Items
GL Line
Sub-ledger document Items
payments

Batch Processes
Component and Object Number Sub- Average Retentio HIGHLOAD PHASE Object Object
of Objects Object of Number of n Period Max Executio Change Display
Created the Sub- [Months] Number n Period s (%) (%)
per Year Object Objects of [hh:00-
(Natural Objects hh:00]
#’s Only) Created
per Day
Payment Plan Transfer
Payment Plan Execution
Payment Run
Payment Lot
Dunning Line Items
Broker Report item
(transfer/post)
Insurance Invoices Line Items
Account Statement Lines

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


Page 21
Online Processes
Transaction Number of
objects in Execution
Highload Period
Phase [hh:00 – hh:00]
Display Account Balance

Other, general comments?

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


Page 22
Sizing mySAP Utilities

Release (i.e. 4.72)

DIALOG PART ONE – Disk Sizing


Total number of business partners
Users
Total number of contracts
Users
Number of contract accounts
Users
Number of budget billings per year
Users
Number of billing cycles per year
Users
Enter either budget billing amounts or partial
billings per year
Average number of billing lines per bill
Users
Average number of print lines per bill
Users
Number 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 contract
Additional lines of information on a consumption
bill per contract
Number of different taxed per contract

Retention period for the above objects in months


Users

DIALOG PART TWO


Object Average number Created during
created per year highload phase
Customer-Overviews
Users
Customer contacts
Users
Move-in
Users
Move-out
Users
Duration of highload phase for the above objects;
mandatory, if you entered values for the highload
phase
Users

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


Page 23
BATCH
No. of business partners (equal to dialog input)
Users
Minimum no. of days to complete one batch cycle
Users
Batch processing interval
Users

Other, general comments?

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


Page 24
Sizing Strategic Enterprise Management – Business
Planning & Simulation
Version (i.e. BPS 3.1)

User Group Definition Highload Phase of One Hour


Maximum no. Avg. no of No. of planning Max no. of Max no. of
of concurrent data records steps per user data records data records
users by manipulated manipulated a user works
group by one single by one single with
planning step planning step simultaneous
ly
Group A 30000 06 60000 200000
Group B 15000 12 30000 100000
Group C 5000 30 10000 25000

Other, general comments?

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


Page 25

You might also like