Beruflich Dokumente
Kultur Dokumente
Table of Content
SAP Business Suite
SAP CRM
CRM Master Data
CRM Sales
CRM Service
CRM E-Commerce
CRM Interaction Center
CRM Mobile
CRM Marketing
SAP Web Channel Experience Management
SAP ERP
Financials
Contract Accounting
Human Capital Management
E-Recruiting
Logistics Execution
Product Development & Execution
Sales & Service
Corporate Services
SAP SCM
Demand Planning
Supply & Production Planning
Order Fulfillment
Service Parts Management
Integration to ECC
SAP Extended Warehouse Management
SAP Extended Warehouse Management - Inbound
SAP Extended Warehouse Management - Outbound
SAP Transportation Management
SAP SRM
SAP GRC Global Trade Services
Compliance and Customs Management
Risk Management Preference Processing
Industry Solutions
SAP for Banking
Analytical Banking
Core Banking
SAP for Insurance
SAP for Retail
SAP for Retail
SAP Forecasting & Replenishment
SAP for Utilities
SAP NetWeaver
Portal & KMC
Business Warehouse
Process Integration
Application Server
NetWeaver Standalone Engines
Solution Manager
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 2 of 59
Expert Functions
The sizing elements from the questionnaires are written in italics.
Back to Top
CRM in the
In Quick Sizer CRM is covered by the following questionnaires:
Quick Sizer
CRM Master Data / Account Management
CRM Sales
CRM Service
CRM E-Commerce
CRM Interaction Center
CRM Marketing
CRM Mobile
Check also the CRM sizing guideline on the SAP Service Marketplace.
Note for Response Times
If you want to achieve specific response times with CRM scenarios, in addition to an appropriate throughput capacity of the
hardware measured in SAPS, choose CPUs which deliver sufficient single-thread performance to fulfill your requirement.
Note for Throughput-Based Sizing
The throughput-based numbers in CRM sizing components CRM-CORACC, CRM-INDACC, CRM-ACT, CRM-LEAD, CRM-OPP,
CRM-APP, CRM-SLSQOT, CRM-SLS, CRM-SLSCON, CRM-SRVACT, CRM-SRVQOT, CRM-SRV, CRM-CONF, CRM-CPLT, CRM-
WCL, CRM-SRVCON, and IC-CALL reflect scenarios that consist of multiple dialog steps and are executed from CRM Web UI
in the browser. The total resource consumption with such scenarios is much higher compared to execution of similar
functionality in batch mode and therefore this sizing is not applicable to batch execution.
Note for IPC Handling
In Quick Sizer, whenever pricing is part of the CRM business process, the resource consumption of pricing is calculated with
simple rules configuration. The CRM sizing in Quick Sizer includes IPC resources (VMC in the same backend system), but for
a very basic pricing configuration.
With more complex customer specific pricing rules/pricing configuration the sizing guide of IPC
(https://service.sap.com/~form/sapnet?
_SCENARIO=01100035870000000112&_SHORTKEY=00200797470000071612&_OBJECT=011000358700002722012003E&)
or even better expert sizing should be applied.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 3 of 59
sizing.
Unlike of the rest of the throughput sizing elements in CRM, the changes and displays to an account are handled as
absolute numbers and not as %.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 4 of 59
With CRM-OPP throughput sizing the input data for number of displays and changes is required as percent of the number
of created objects.
Comment
User-based sizing element OPP-USER should be used as alternative to the throughput-based sizing element CRM-
OPP. Overlap should be avoided.
Any attachments to opportunity such as text files, presentations, documents in print format, photos, etc. which are
uploaded into CRM are not considered in this approach and should be calculated additionally.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 5 of 59
Service confirmations
Complaint, return and inhouse repair
Warranty claim
Service contract and contract quote
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 6 of 59
The sizing calculation includes create new claim, maintain header data, maintain billing data, add item(s), and save.
Note
With CRM-WCL throughput sizing the input data for number of displays and changes is required as percent of the number
of created objects.
But if you take a look at extreme cases, where for example within the B2C use case, sales documents with about 100
items are created in one step by using templates (which is quite familiar in some industry sectors), then the sizing of the
pure IC user will be insufficient. In such a case you should enter the affected users additionally, for example within the
CRM sales questionnaire (that means extra CPU and extra memory).
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 7 of 59
Note
With CRM-MSA throughput sizing the input data for number of displays and changes is required as percent of the number
of created objects.
In general, the mobile sales users will upload their data to the CRM system in a time frame of a few hours, for example in
the evening. Enter the highest number of users you expect to login within one hour.
Users of handheld sales and handheld service functionality should be sized in this component.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 8 of 59
Note
The loyalty offline mass upload and processing is usually bound to requirement for the duration of the
execution and therefore in Quick Sizer it is more appropriate to use the peak sizing per period compared to
the average year sizing. Whenever possible avoid overlapping intervals for upload and processing to
minimize the resource consumption requirements.
To efficiently allocate hardware resources that are calculated in Quick Sizer the number of
MA_LSMW_UPLOAD_MAX_NO_WP which are used for CRM Loyalty Management and configurable in the CRM
system under ‘Spro -> IMG -> Customer Relationship Management -> Marketing -> Loyalty Management -
> Processing Settings -> Define Batch processing Parameters’ should be maintained.
For example, equal to the number of CPUs (out of the total machine capacity) which the customer would
like to dedicate to loyalty batch job.
Specifics for CRM Loyalty Batch Jobs for Processing (LOY-PROC)
Activities (Number of activities)
Enter value for the total number of member activities which should be uploaded in the defined time interval.
Rules p a (Average number of rules per activity)
Enter value for the average number of rules which are defined per single activity. A typical expected value range is
not more than 10, while maximum enabled value in Quick Sizer is 99.
Act p.r (Average number of actions per rule)
Enter value for the average number of actions defined per one rule. A typical expected value range is less than five
while Quick Sizer enables values up to nine.
Mon. (Number of months the data remain in the database)
Enter the number of months that data remains in the database (residence time).
Specifics for CRM Loyalty Online Processing (LOY-CMA (Create member activity), LOY-PMP (Post member
points), and LOY-RMD (Retrieve member data))
Objects (Sizing objects created per time unit (TI)
Enter the number of remote requests which the CRM Loyalty system needs to handle in the defined time interval.
The expectation is that each request registers exactly one member activity with or w/o points or retrieves
information for exactly one member.
Mon. (Number of months the data remain in the database)
Enter the number of months that data remains in the database (residence time).
The CRM side part of the export to SAP NetWeaver BW is always included.
Note
The campaign execution is usually bound to requirement for the duration of the execution and therefore in Quick Sizer it
is more appropriate to use the peak sizing per period compared to the average year sizing. For each different campaign
create a new line of peak interval in the sizing table. When possible avoid overlapping intervals of execution of the
different campaigns to minimize the resource consumption requirements. To efficiently allocate hardware resources that
are calculated in Quick Sizer the number of ‘parallel processes’ which are used for CRM campaign execution and
configurable in the CRM system under ‘Spro -> IMG -> Customer Relationship Management -> Marketing -> Marketing
planning and Campaign management -> Campaign Execution -> Make Settings for Parallel Campaign Execution’ should
be maintained.
For example, equal to the number of CPUs (out of the total machine capacity) which the customer would like to dedicate
to campaign execution.
Back to Top
Íntroduction to Introduction
SAP Web Channel SAP Web Channel Experience Management installation uses the following software technologies from SAP: Web AS Java,
Experience AS ABAP in CRM or ERP usage and MDM Server. It could be run in four different variants of shopping cart, which influence
Management the sizing result and are reflected in Quick Sizer as sizing elements:
Java shopping cart with CRM order backend (sizing element J-SC-CRM)
CRM shopping cart with CRM order backend (sizing element CRM-SC)
Java shopping cart with ERP order backend (sizing element J-SC-ERP)
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 9 of 59
ERP shopping cart with ERP order backend (sizing element ERP-SC)
Additional resource consumption influencing factor is the choice between list pricing and dynamic pricing. With dynamic
pricing IPC resource consumption is accounted to the CRM backend, where IPC is actually located. Quick Sizer delivers
throughput-based sizing for all involved components, according to selected shopping cart and pricing configuration.
Note for Good Response Times
SAP Web Channel Experience Management is such type of product for which end user set very challenging response time
requirements. To achieve that choose CPUs with best Single Computing Unit performance (see also OSS note 1501701).
SAP ERP
Back to Top
Financials Definition
SAP ERP Financials comprises
Financial Supply Chain Management (FSCM)
Financial Accounting (FA)
Management Accounting (MA)
Corporate Governance (CG)
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 10 of 59
Financial Supply Chain Management includes functions such as Treasury and Risk Management, Cash and
Liquidity Management (CLM), Credit Management, and Dispute Management. The dominating functions of
Financial Accounting are General Ledger, Accounts Receivable and Payable, Fixed Asset Accounting, and
Financial Statements. Amongst others, Management Accounting includes Profit Center Accounting, Project
Accounting, Revenue and Cost Planning, and Transfer Pricing.
The Quick Sizer maps most of the sizings of FSCM and FA to FI, Management Accounting is predominatly reflected in CO.
From a sizing perspective Corporate Governance plays a subordinate role.
FI User Definition
FI-USER In general, all users in the above transactions can be sized with 1 FI user (e.g. FI-AA, CLM).
To size Treasury and Risk Management (TRM) users, enter 2 FI users per TRM user.
Note
Business Warehouse with its Strategic Enterprise Management comprises the functions that were formerly accounted for
by Enterprise Controlling.(see Business Warehouse)
Posting activity calculation from Posting activity calculation to Number of line items
Cost center Cost center 3
Cost center Statistical order 4
Comment
If you use detailed planning, you should add line items created during planning.
Enter the number of line items that are created online (D = standard sizing for throughput)
Enter the period closing activities (B = standard sizing for background)
Profitability Comment
Analysis In our experience, the number of documents that you transfer to CO-PA from Sales and Distribution (SD) or Financial
CO-PA-BIL Accounting (FI) serves as a good indicator of the disk space and system load that CO-PA represents. Using this indicator
CO-PA-FI simplifies the sizing process because the Quick Sizer no longer needs to take into account the contributions from
CO-PA-SLS planning, cost center assessment, the information system, realignments, or settlement. If your requirements in one of
these areas are high (for example, a large volume of data needs to be processed by a large number of users during peak
system load times), you should contact your hardware partner or SAP. To gain a deeper understanding of the factors that
can influence sizing and performance, see the information contained in at service.sap.com/co-pa.
Transferred Objects: If you use Profitability Analysis, SD billing documents (SD-BIL) and FI documents are transferred to
CO-PA automatically. The transfer of orders (SD-SLS), on the other hand, is optional. For objects, enter the number of
documents transferred per year from the respective components to CO-PA. For sub objects, enter the average number of
document items in each case. You can also use the above methods to display how external data is transferred to CO-PA.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 11 of 59
Documents postings are created in other components and then posted to EC-PCA.
EC-PCA Enter the number of documents that are created in PCA with their respective lines items and the number of orders that
have been posted by other components.
Business Definition
Accounting The proof of a business transaction. A distinction is made between original documents and data processing (DP)
Documents documents:
FIN-BAC Original documents include incoming invoices, bank statements and carbon copies of outgoing invoices.
DP documents include accounting documents, sample documents and recurring entry documents.
Whereas accounting documents are a representation of the original document in the SAP System, sample and recurring
entry documents are simply templates to simplify entry of accounting transactions.
Assessment Definition
CO-OM Assessment is a method of internal cost allocation in which you transfer the costs of a sender cost center to receiver CO
objects (orders, other cost centers, and so on) under an assessment cost element. The system supports both the
hierarchical method (where the user determines the assessment sequence) and the iterative method (where the system
determines the sequence via iteration).
Estimation of line items for assessment, distribution and periodic reposting:
The segments of all cycles have to be added. For each segment the line items (sender (S) - receiver (R) relationship) may
be calculated:
Example
You have defined a cycle which consists of the segments A and B. Each segment consists of 5 senders and two receivers.
Each receiver(R) of segment A has received postings from each sender(S) with three different cost elements (CE). Each
receiver(R) of segment B has received postings from each sender(S) with four different cost elements.
Therefore the cycle has 30 + 40 = 70 S-R relations altogether.
Segment A: 5 (S) * 3 (CE) * 2 (R) = 30 S-R relationships
Segment B: 5 (S) * 4 (CE) * 2 (R) = 40 S-R relationships
Back to Top
Contract Accounting
Contract Definition
Accounting Find more information on Contract Accounting within the document "Sizing Contract Accounting with the Quick
Sizer" at the Service Marketplace www.service.sap.com/quicksizing -> Using the Quick Sizer -> Experts.
The whole sizing is split into one mandatory and four optional blocks:
EDR Billing (optional)
* EDR-UPL
* EDR-BILL
Upload of billing documents (optional)
* LOAD-BILL
Convergent invoicing (optional)
* CONV-INV
* Subledger
Upload of subledger documents (optional)
* LOAD-INV
FI-CA (mandatory)
* PAY-RUN
* CD-PL
* DUNNING
* DEF-POST
* CORR-PRINT
.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 12 of 59
Convergent Definition
Invoicing During invoicing billing documents are converted into invoicing and subleger documents. In most cases there is a 1:1
(optional) relationship amongst them, one billing document gives one invoicing document and one subledger document, therefore
CONV-INV this assumption has been built into the Quick Sizer.(Tip: in cases where multiple billing documents are aggregated into
one invoice, the number of billing lines per invoice document should be used as input in ‘Lines per invoicing document’.
This gives a better result)
The relation between billing lines and invoicing lines is difficult to estimate, it can be everything from less lines to more
lines. Invoicing can aggregate billing lines but also adds tax lines to the document, hence this behaviour. Example: For
each phone in a company's office a bill is created and there might be only one bill for the whole office. However, it would
be possible to create two invoices, one for the head of the office and one for the other employees. In this case, there
would always be two invoices per contract account.
These phone bills may consist out of landline calls, mobile calls, internet usage and cellphone purchase, but there might
be five lines on the invoice, one for mobile and landline calls, one for internet usage, one for cellphone purchase and one
additional for VAT.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 13 of 59
Specifics for this sizing element for CPU and Disk Sizing
Invoicing documents (Objects)
Invoices created per year.
Lines per invoicing document (Items)
Average number of lines on the invoice
Subledger Definition
Documents Subledger documents are financial documents that are finally posted in an aggregated form in the general ledger (GL).
(optional) They consist of a header and two different types of lines that represent the document as the business partner sees it and
SUBLEDGER as it is seen by the general ledger. If business partners purchase a book, they might see two lines on the bill, one is the
price of the book and one is the tax. These lines printed on the bill to the customer are the so-called business partner line
items. The vendor might see the book sale from a different view and post the tax on one GL account. The price however
is split into two parts, one to be transferred finally to the publisher, the second one to the author, hence s/he wants to
post them to two different GL accounts.
When a subledger document is balanced usually another subledger document is created for which only the GL items are
replicated.
Upload of Definition
Subledger This section and hence the parameters are only important, if it is planned to upload subledger documents from an
Documents external source, e.g. a billing system. In a hybrid scenario where the majority of billing documents comes from the
(optional) convergent invoicing and only some are uploaded from a billing system, the values to be entered herein might be
LOAD-INV different from those entered in the previous sections.
Specifics for this sizing element for CPU Sizing
Subledger documents (Objects)
The number of subledger documents created during a year. They can be uploaded or created during convergent
invoicing. Budget billing plans and down payments create subledger documents as well.
General ledger items per subledger document (Items)
The average number of GL items a single document is posted to.
.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 14 of 59
Specifics for this sizing element for CPU and Disk Sizing
Payments per year (Objects)
Total number of payments to be handled via payment lot.
.
Dunning Definition
(mandatory) Not always business partners pay their open items on time. In this case, a dunning procedure is started, usually a
DUNNING reminder is send to the customer first before other actions like cancellation of service are done. Experience from
customers shows this figure is between 5 and 10% of all documents.
Specifics for this sizing element for CPU and Disk Sizing
Dunnings notices per year (Objects)
Total amount of overdue items per year is requested here.
Lines per dunning document (Items)
The average number of lines of a dunning document. This may be different from the number of lines of the original
subledger document as a dunning fee may be charged.
.
Specifics for this sizing element for CPU and Disk Sizing
Number of deferred postings per run - CPU sizing - or per year - disk sizing - (Objects)
Average number of postings into which a subledger document is split for deferred revenue postings.
.
Correspondence Definition
Print (mandatory) A correspondence is any letter send to the business partner. This includes bills, invoices, dunning letters and other mail.
CORR-PRINT
Specifics for this sizing element for CPU and Disk Sizing
Correspondences per year (Objects)
Number of correspondences created per year. In most cases this number is equal to the number of bills generated
plus the number of dunning notices.
.
Back to Top
Personnel Definition
Administration & Personnel Administration and Payroll Accounting from the SAP ERP HCM solution includes the following areas: Personnel
Payroll Administration, Benefits, Compensation Management, Recruitment, Personnel Time Management, Incentive Wages,
Accounting Business Trip Management and Payroll Accounting.
PA-USER
Personnel Definition
Planning & Personnel Planning and Development includes the following areas: Organizational Management, Personnel Development,
Development Workforce Planning, Training and Event Management and Room Reservations Planning.
PD-USER
General Remarks Quick Sizer offers templates for different categories of ESS/MSS scenarios
for the ESS/MSS The Quick Sizer does not reflect all existing ESS/MSS solutions as we follow the 80:20 rule. That means: 80 percent of
Scenarios load are caused by 20 percent of the SAP solutions. As a workaround you can try to map your scenarios to the existing
scenarios which are weighted as follows: "small" would mean a complexity corresponding to the "payslip (ESS) / CICO
(MSS)" scenario, "medium" would be equivalent to "CATS (ESS) / CATS Approval (MSS)", and "large" would be
eqvalenuit to "travel (ESS) / Manager Homepage (MSS)". Then, additional scenarios can be sized by using the ESS/MSS
component which corresponds best in complexity.
Note on Portal Sizing
Portal integration is per default included automatically. After calculating the sizing result, there are two lines within the
sizing result: one for ERP and one for NetWeaver. The NetWeaver line contains the portal sizing. On the result level
"Sizing element" you see the result for the individual ESS/MSS sizing elements and the corresponding (automatically
calculated) portal sizing element "NW-EP-ESS" or "NW-EP-MSS".
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 15 of 59
ESS - Medium Specifics for ESS-MEDIUM CATS, Leave Request, Personal Information
ESS-MEDIUM With this sizing element, employees can enter CATS information, enter leave requests, or maintain personal information
in the self-service application.
In the "Objects" column, for exmaple enter how many CATS entries are executed for all users per time period.
In the "Portal" column, per default Portal integration is selected. Uncheck the flag, if Portal intergration is not
used.
Note
CATS, Leave Request, and Personal Information are typical medium ESS scenarios (see “general remarks for the
ESS/MSS scenarios”)
Portal integration is per default included automatically. After calculating the sizing result, there are two lines within
the sizing result: one for ERP and one for NetWeaver. The NetWeaver line contains the portal sizing. On the result
level "Sizing element" you see the result for the individual ESS/MSS sizing elements and the corresponding
(automatically calculated) portal sizing element "NW-EP-ESS" or "NW-EP-MSS".
If ESS/MSS is used without Portal integration, the flag should be unchecked.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 16 of 59
In the "Objects" column, enter how many CATS approval scenarios are executed for all users per time period.
In the "Portal" column, per default Portal integration is selected. Uncheck the flag, if Portal intergration is not
used.
Note
CATS Approval is a typical medium MSS scenario (see “general remarks for the ESS/MSS scenarios”)
Portal integration is per default included automatically. After calculating the sizing result, there are two lines within
the sizing result: one for ERP and one for NetWeaver. The NetWeaver line contains the portal sizing. On the result
level "Sizing element" you see the result for the individual ESS/MSS sizing elements and the corresponding
(automatically calculated) portal sizing element "NW-EP-ESS" or "NW-EP-MSS".
If ESS/MSS is used without Portal integration, the flag should be unchecked.
Payroll Definition
HCM-PY For payroll you need to enter the number of employees and the number of retro calculations per payroll. A retro
calculation is when a payroll run is repeated for a period for which payroll accounting has already been performed in the
payroll past. Retroactive accounting is triggered during the payroll run for the current period if certain master and time
data affecting the payroll past has been changed in the meantime.
Multiply the average number of retro calculations per employee per payroll times plus 1 times the number of employees:
(number_employees)* (1 + number_retro_calculations).
For example: You have 2 retro calculations per employee, this means a payroll run is executed for 3 periods in total. If
have 100,000 employeed for whom the payroll is done, then you calculate
(100,000) * (1 + 2) = 300,000. Please enter 300,000.
Comment
Financial postings resulting from loan postings have to be treated separately. For the number of employees we assume
that the payroll is executed once a month. Other periods should be scaled through the input data (Example: 50,000
employees should be calculated semi-monthly in 4 hours -> Input: 100,000 employees and 8 hours)
Back to Top
E-Recruiting
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 17 of 59
Distributed Candidate scenario, checkboxes for all candidate and applicant scenarios (Candidate Registration,
Application for Job Posting, Job Search) have to be selected. It is not possible to select only part of the candidate
and applicant scenarios. In this case, the user will get an error message. If no Distributed Candidate scenario is
used, all ‘Distributed Candidate Scenario’ checkboxes have to be deselected. This is the default case.
Recruiter Scenarios:
• ERC-REQ Creation of Requisition (with Posting and Publication)
• ERC-CA-LST List of Candidate Assignments to Requisition (with Subsequent Processing Steps)
Creation of Definition
Requisition (with A requisition is an internal document created by recruiters or managers in order to search for suitable candidates for one
Posting and or more positions. A requisition contains – besides the general job information – information on organizational data,
Publication) support team, job requirements, education requirements, as well as attachments for additional information and a list of
ERC-REQ job postings. Vacant jobs for which potential candidates can apply are announced using postings. Job postings are based
on the associated requisition. A job posting can be published in various posting channels and for various periods. Thus
various publications (for example, separated for external and internal candidates) can be created for a job posting.
The current sizing scenario comprises the creation of one requisition with general job information, assignment of three
support team members, various job requirements, and three education requirements. Three attachments and
questionnaires are assigned. One posting is created with two publications (one for internal candidates, one for external
candidates).
To simplify matters, different pieces of information of a requisition are treated in the same way in the current sizing
scenario. In order to determine the sizing of an average requisition, you add the various pieces of information (for
example, number of job requirements, number of education requirements, number of postings) and enter the sum as the
average number of line items. If you are unsure, just use 15 items for an average requisition.
Note that attachments of requisitions are not taken into account for disk sizing as the percentage for these attachments
should be very small compared to the attachments for candidate registrations.
Candidate Definition
Registration Candidate registration means that a person who is interested in a work relationship registers in the Talent Warehouse
ERC-CA-REG and stores his or her data there (‘Candidate Profile’). For internal candidates (employees of the company), part of his or
her data is usually already available and can be transferred to Talent Warehouse; external candidates (not belonging to
the company) have to enter all of their data. Candidate data, that is, the candidate profile, comprises personal data,
communication data, information on work experience, education, qualifications, and desired job conditions and work
location. Attachments (such as resumes) can be uploaded by candidates.
The current sizing scenario comprises the registration of an external candidate with the following profile data: personal
data, communication data, information on desired job conditions and work location, information about three different
work experiences, three educations and on various qualifications. Three attachments are also uploaded.
To simplify matters, different pieces of information of a candidate registration are treated in the same way in the current
sizing scenario. In order to determine the sizing of an average candidate registration, you add the various pieces of
information (for example, number of work experiences, number of educations, number of attachments, and so on) and
enter the sum as the average number of line items. If you are unsure, just enter 15 items for an average candidate
registration.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 18 of 59
For a Distributed Candidate scenario, the ‘Distributed Candidate Scenario’ (DCS) checkbox has to be selected for all
candidate and applicant scenarios (Candidate Registration, Application for Job Posting, Job Search).
Specifics for this sizing element
Objects
Enter the number of candidate registrations you expect during peak times.
Items
Enter the average number of line items per candidate registration. If you are unsure, just enter 15.
Attachments
Enter the average number of attachments per object.
Size
Enter the average size of attachments in KB.
Months
Enter the number of months that data remains in the database (residence time).
Back to Top
Logistics Execution
Logistics Definition
Execution Logistics Execution contains Warehouse Management as well as Inbound and Outbound Logistics
LE-USER
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 19 of 59
PM Orders Definition
ALM-USER Orders in the sense of maintenance orders. Requirement to execute a maintenance task on a maintenance object for a
ALM-PM specific deadline. In addition, the maintenance order is a means of documenting maintenance work. In particular,
maintenance orders are used to
- plan maintenance tasks in a targeted manner
- monitor the execution of maintenance tasks
- enter and settle the costs incurred by maintenance tasks
The sub-object of a maintenance order is a component. A maintenance order contains operations that describe the
individual work steps. If greater detail is required, operations can be subdivided into sub-operations. Enter the average
number of components per operation.
Materials Definition
Management Materials Management contains Inventory Management as well as Purchasing.
MM-USER
Materials Definition
Movement Physical or logical movement of materials which leads to a change in material stock levels or results in direct consumption
MM-IM of the material. A goods movement can be a goods receipt, goods issue, or a transfer posting of materials. Please enter
the number of all material movements that originate from any used component within the SAP system (e.g. LE - SHP
Logistics Execution - Shipment)
Line items: A goods movement consists of items containing the quantity and value of the given material. The materials to
be actually placed in or removed from storage can be specified in each item as single units.
Comment
No postings in the previous month. When processing different IDOC-types (e.g. store order), enter any follow-on
documents separately (such as SD order line-items in SD-SLS).
Purchase Order Definition
MM-PUR Request or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a certain
quantity of material or to perform certain services.
Line items: A purchase order consists of a number of items, each of which will have a procurement type defined.
Comment
We assume a purchase order has two text lines on average. 30% of the purchase orders are assigned to an account.
10% of the line items have delivery costs. There is one goods receipt line item per purchase order line item. There is one
invoice line item per purchase order line item.
Production Definition
Planning and Production Planning contains Sales & Operations Planning, Master Planning Capacity planning as well as Material
Control Requirements Planning.
PP-USER Production Control deals with Production Orders, KANBAN and Repetitive Manufacturing.
Confirmations Definition
PP-CONF Documents the processing status of operations or sub-operations. A final confirmation is used to determine:
At which work center the operation was carried out
Who performed the operation
Quantities of yield and scrap produced
Size of the standard values required for the operation
Comment
Enter the respective materials movements (goods receipt for the header material and goods movement for the
used components) in the line for MM-IM. This is not counted automatically.
Line items means the number of confirmed operations.This is not the number of material components as in the
sizing element PP-SFC.
The assumptions of the production order in the sizing element PP-SFC apply here, too.
Repetitive Definition
Manufacturing A component in the SAP System for planning and controlling repetitive manufacturing and flow manufacturing.
(Planned Orders)
It enables the period-dependent and quantity-dependent planning of production lines and reduces the work involved in
PP-REM
production control and simplifies backflushing (confirmation, goods receipt posting).
Production Orders Definition
PP-SFC Manufacturing order used for discrete manufacturing. A production order contains operation sequences. An operation
describes how to carry out a work step. By combining operations into operation sequences, you can create parallel or
alternative processes.
The sub-object of a production order is a component: The following graph gives an example of how to determine the
number of components by showing number of components of a multi-level BOM of a product F1.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 20 of 59
The finished product F1 contains a semi-finished product F2, which is also an in-house-product. Therefore the production
orders for both products F1 and F2 must be considered for sizing.
The size of the "number of components" is determined by the summation of all individual components on the first
production layer (finished product and semi-finished product, respectively). The components used are either raw
materials, for example F1Cx or F2Cx, or assemblies, such as F2 used in the production of F1. Phantom assemblies (P1
and P2) are only used to structure the bill of materials; they are not produced seperately. The components of the
phantom assemblies (P1Cx or P2Cx) must therefore be added to the components of the next higher level.
Therefore, in this example we can determine the following number of components:
The production orders for the finished product F1 have seven components (F1C1, F1C2, F1C3, P1, P1C1, P1C2, and
F2). The phantom assembly P1 should be counted as a real component.
The production orders for the assembly F2 have six components (F2C1, F2C2, P2, P2C1, P2C2, and P2C3).
Note
The columns for the display of objects and the changes of objects should be filled, too. If, for example, you create
a production order in one transaction and release it afterwards, please enter "100" for "object changes" because
every order (i.e., 100% of the orders) is changed by being released. If you display the production order, then you
must fill in the field for object display.
Confirmations to a production order must be entered at the sizing element PP-CONF.
Order settlements are not considered and have to be considered by CO.
Comment
We assume:
10 status items per production order
3 status items per component
1 sequence for every 10 componentsr
1 operation for every 5 components
3 status items per operation
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 21 of 59
consumption, enter data that reflects the actions of a very busy day. Do not enter data that reflects a typical day -
this is automatically considered.
The way of entering data for peak load for projects is a little bit different from other sizing objects. The number of
new projects, the number of changes and displays are just added and the sum is entered in the field "Objects".
Average numbers of WBS, networks, and activities are entered as for the average load.
The fields "Changes" and "Display" stay empty.
For example:
Every year, 150 projects are created with an average of 500 WBS elements. They remain in the database for about five
years. On the average, each project consists of 20 networks and 100 activities per network. The estimation of the total
number of changes and displays per project bases on the assumption that a project is changed three times and displayed
once per working day over a period of 2 years. In a high load phase, 300 projects are changed five times and displayed
once during a day. Additionally, on these very busy days, 10 projects are created. The sum of the number of new
projects, changes, and displays is:
Inspections in Definition
Quality Tasks for determining the actual status of a technical system (for example, a machine) or a material.
Management
Inspection Characteristics: The basis on which an inspection is performed.
QM-USER
QM-IM Comment
We assume that one inspection with several inspection characteristics is carried out per inspection lot. On average, there
is one single value recording per inspection characteristic.
Material Definition
Requirements Material Requirements Planning (MRP)
Planning Generic term for procedures in materials planning which take into account and plan every future requirement during the
MRP RUN creation of order proposals (independent requirements, dependent requirements, and so on).
Net Change Planning
Materials planning run where only those materials are planned which have undergone a change relevant to materials
planning since the last planning run.
Specifics for MRP
Planned orders per day
A planned order (PP-SOP) is a request created in the planning run for a plant to trigger the internal procurement of
a plant material for a certain quantity for a specific date. Enter the number of planned orders that are added per
day. The Quick Sizer automatically determines the total number of planned orders for the planning run (number of
planned orders per day * planning horizon in days).
Components/Bill of Material (BOM): Average number of components per BOM
see PP-SFC
Reorder items: Purchase requisitions for reorder-point driven materials
Special procedure in materials planning. If the reorder point is greater than warehouse stock, an order proposal is
created by materials planning. For this type of procurement multiple requests are summed up to build one
procurement request. This is the lean version of external procurement.
Non-reorder items: Purchase requisitions or schedule line items for non-reorder-point driven materials
For this type of procurement each individual request leads to a purchase requisition or a schedule line item. This is
the more demanding version of external procurement.
Planning horizon in days: Length of planning horizon in days
The planning horizon is the period which is used when the MRP planning mode "net change planning in the planning
horizon" is used. For this type of net change planning only those materials are planned in the planning run which
have a change related to materials planning within the period (in work days). The length of the planning horizon
should at least include the following: Period in which customer orders are being created, delivery times and
complete material processing time.
% BOM changes per day: Number of BOM structure changes per day in %
Each change of a BOM invalidates the planning data and requires a new calculation of all planned orders which are
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 22 of 59
based on this BOM. Enter the average number of BOMs which are changed per day.
% dependencies: % of BOM components with object dependencies (average)
When variant configuration is used the explosion of the BOM is a more complex process. The Quick Sizer assumes a
model of small or medium complexity of the underlying variant configuration and takes into account additional
resource requirements. If the customer's model of variant configuration lies within this small to medium category,
the average number of components (%) with object dependencies can be entered directly. If the customer's model
of variant configuration is very complex, the input can be multiplied by an additional factor which takes into
consideration extra resources.
For example:
If 10 % of the BOM components have object dependencies and the model is three times more complex enter 30 %
in this field.
% LTS: Number of orders with Lead Time Scheduling in %
Lead Time Scheduling calculates the exact production dates and creates capacity requirements by using the routing
information.
Comment
We assume the following:
The MRP run is conducted every day with the processing key "Net change" and planning mode "Adapt planning
data".
The number of components implicitely determines the scope of the routing. With an increasing number of
components, the number of operations in the routing rise.
The runtime and CPU consumption directly depend on the number of reservations in the system.
The MRP run can be parallized without end, dependencies on data constellation are not considered.
The MRP sizing of the Quicksizer only gives CPU numbers. Diskspace is not calculated, because the MRP run works
more or less on a steady state concerning the disk space. This means that the planning data created by the MRP
run is deleted when the corresponding production orders and purchase orders are created.
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 23 of 59
only be completely archived if all due line items have been cleared. Reversed documents can always be archived.
"Old" case versions that are not valid can be archived immediately. There are further restrictions for all other
versions.
Customer Definition
Inquiries A customer request to the company for a quotation or sales information that is not binding. The request can refer to
SD-CUST materials or services, conditions and, if necessary, delivery deadlines. It is accepted by the sales area that is then
responsible for any further processing.
A customer request comprises one or several items containing the required quantity of a material/service.
Line items: Number of line items per customer inquiry
Invoices Definition
SD-BIL Sales and distribution document used to charge a customer for a delivery of goods or for services rendered.
Line items: Number of line items per invoice.
Sales Data and Definition
IDocs Number of Sales Data and IDocs created per year. The Quick Sizer assumes that for every Idoc, one material document
SD-POS and one billing document are generated with subsequent postings to FI. The IDocs themselves are assumed to be
archived immediately.
The column "number of objects created per year" refers to the number of documents created per year. The next column
"number of subobjects....." refers to the number of line items per document.
The Quick Sizer considers aggregated upload (WPUUMS). In the case of WPUBON, you will have to consider the following:
1. Number of POS transactions. This corresponds to the number of customers per store.
2. Number of items per transaction. This corresponds to the number of articles purchased by each customer.
The total number of line items is the product of number of customers and the number of articles per customers.
Example: You have 500 stores with an average of 300 customers per day and an average of three articles per
customers. Assuming one IDoc per store this will give you:
500 IDocs, each with 900 lines per day. Assuming 300 working days
Number of objects created per year = 300 x 500 = 150000,
Number of sub objects = 900
Residence period is actually that of the follow-on documents - material-, billing- and financial-documents.
Comment
Number of Sales Data and Idocs created per year. The System creates one goods issue and one bill per document/IDOC
including the respective number of line items.
With each bill and material movement, one FI document with the respective number of line item is created. Additional
postings are not considered.
When processing different IDOC-types (e.g. store order), enter any follow-on documents separately (such as SD order
line-items in SD-SLS).
In the following graph you can see the factors that influence sizing.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 24 of 59
SD-SLS A customer request to the company for delivery of goods or services at a certain time.
Back to Top
Corporate Services
Back to Top
User in SCM
In SCM, load created by users is added to the throughput sizing. This is a different procedure from standard user sizing.
Back to Top
Demand Planning
Demand Planning
Sizing assumptions and principles
DP USER
The hardware sizing for SAP APO estimates the following three hardware components:
1) Live Cache server
2) Database server
3) Application server
liveCache is a memory-based Database and therefore the appropriate estimation of the memory requirement is very
important.
The SAP APO Demand planning application stores the historical data in NetWeaver BW InfoCubes. These are described as
user designed relational databases, composed of one large table of input and output values, called a Fact Table, and
several smaller tables that contain characteristics describing the data. These are called dimension tables. InfoCube data
are stored in tables on the disk, not in the Live Cache.
For performance reason the historical data is copied from NetWeaver BW InfoCube to liveCache. Since Demand Planning
uses Live Cache, the Live Cache size is increased due to the historic and planning result time series data in it. Instead of
storing the data in Star Scheme format (Fact and Dimension table combination) of the InfoCube, Live Cache stores the
data in a time series for a particular key figure and characteristic combination.
Characteristics are attributes that describe what is planned. Examples include item code, UPC, brand name, market
segment, location and customer name. Key figures hold the data input and output quantities that are stored in a single
fact table for each InfoCube. Examples include sales history, demand forecast and percent promotion increase.
Characteristics and key figures cannot be interchanged. In addition, characteristics can be bundled into groups, called
dimensions. For example, item name, UPC, brand name, and market segment can be bundled into a single dimension
called product. The number of info objects and dimensions and the number of unique values for each info object are used
to determine the required data storage needed for the APO Demand Planning system.
The characteristic combinations, key figures, and time horizon are the variables, which influence the scalability of
Demand Planning. The characteristic combination is the most dynamic variable, which has the range from a few hundred
thousands to several millions. Tests showed that the runtime of the DP planning jobs is acted in a linear form with the
increasing of the characteristic combination. In other words, the throughput (number of characteristic combinations be
planned per hour) scales with the size of the hardware.
Compression of The Time Series data stored in liveCache may be compressed. This compression technique is very simple and it should
Timeseries be understood that a Time Series is either compressed or it is not. There is no partial compression. The only parts of
the Time Series that is compressed are the empty time buckets. If less than 30% of the time buckets in a Time Series
are loaded with data, then the empty time buckets are compressed. Nothing is done to the time buckets that have data
in them. If more than 30% of the time buckets in a Time Series are loaded with data, the empty time buckets remain
uncompressed and are loaded with zeros. As data is loaded, time buckets are filled for a specific characteristic
combination key figure in a Time Series. Time Series compression is dynamic, i.e. when a Time Series is filled to greater
than 30%, SAP software un-compresses the empty time buckets. Likewise, if data is deleted from the Time Series and
usage falls below 30%, the Time Series is again compressed. For all practical purposes, there is no memory consumed
by empty time buckets for a Time Series when compressed. However, memory is consumed when the Time Series is
expanded even with the time buckets filled with zeros. For a characteristic combination key figure Time Series, data
resides in real memory until LiveCache is cleared. When compressing a characteristic combination key figure Time
Series, SAP software builds a structure representing the compressed data. This structure consists of the position of the
time bucket data for a characteristic combination key figure in a Time Series, and the data for that time bucket. There
are no entries in the structure for time buckets that have zero data. Currently, all characteristic combination key figures
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 25 of 59
for a Time Series and for a Planning area have the same number of time buckets.
Sizing Elements Mainly we size the memory requirements of the timeseries stored in liveCache. The CPU sizing is determined by the
batch planning run which calculates the forecast.
APO - Planning Specifics for the Planning Area Sizing - SAP liveCache Memory
Area Sizing - SAP
The total number of characteristic combinations is the number of values of each combination multiplied. For
liveCache Memory
example, a company plans 800 products across 12 plants to serve 20 customer locations. Then the number of
TIMESERIES
characteristic combinations would be 800*12*20 = 19,200. But usually not all products are available in all plants
and all customer locations. Instead the average number of products in each location has to be estimated, e.g. in
average 100 products are located in plants and in average 2 customer locations are delivered by one plant. Then
the total number of characteristic combinations would be 100*12*2= 2,400.
Total number of key figures is the sum of the key figures used in planning.
Total number of periods is a count of time buckets used in planning. The more time buckets, the more memory
space in liveCache are required to store data. For example, a DP planner may define an annual forecast in weekly
time buckets. Hence, the number of time buckets is 52. Alternatively, the planner may define the annual forecast
horizon as 12 weeks followed by 8 months. In that case, the number of time buckets would be 12+8*4 = 42,
because all data is stored in the smallest time unit.
Compression index
Either a 'Compression index' can be specified or the number of compressed time series (in percent) and the
number of periods can be specified in the compressed time series. A compression index of 0 means that all time
series are not stored in compressed form and the maximum main memory requirement is calculated. A
compression index of 9 means that 90% of the time series are stored in a compressed way. A compression index
of 5 is preset. This corresponds to a compression rate which we have observed with many
customers.
Note
Fill-in either values for the compression index or values for the following two fields.
Percentage of compressed timeseries: In a productive environment you can determine the percentage of
compressed timeseries with help of the report /SAPAPO/OM_TS_FILLRATE (see note 537210). If you can’t
determine this number than please use the compression index.
Number of time buckets in compressed timeseries: If the percentage of compressed time series and the
number of periods in the compressed time series is known, these values can be entered in the fields provided (see
note 537210).
Total number of planning versions stored in liveCache. The calculation for liveCache memory requirements
assumes that each version contains the same amount of data per version.
Back to Top
Production
Sizing assumptions and principles
Planning and
Supply Network
The hardware sizing for SAP APO estimates the following three hardware components:
Planing
PP USER 1. Live Cache server
SNP USER
2. Database server
3. Application server
The Task of Supply Network Planning is to identify sources for supply for finished products. It plans and considers safety
stock levels in any location and distributes production over plants. Additionally it chooses production resources in plants
and explodes bill of materials in plants. The outputs are purchase requisitions, stock transport purchase requisitions and
planned production orders. We consider SNP heuristic to estimate the CPU requirements. The SNP heuristic usually runs
in background.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 26 of 59
Mainly we size the memory requirements of the orders in liveCache. The CPU sizing is determined by the SNP heuristic
Sizing Elements
planning run. If more than one version is used then we recommend to input the data for each version separately and add
a comment which describes the version. You can easily add new input lines for each version.
APO - Master Data Specifics for Master Data - SAP liveCache Memory
- SAP liveCache
The number of location-product combinations can be determined by one of two ways. If all products can be
Memory
stored in all locations, then multiply the number of products by the number of modeled locations. Alternatively, if
MASTERDATA
selected products are stored at each facility, then sum up the number of products modeled at each location. For
example, each customer location may store only finished goods, while each distribution center stores both finished
goods, and components, and each plant produces and stores only a portion of the finished goods and components.
Total numbers of resources i.e. work center, production lines, and tools to be planned in APO.
Resources used in APO can define work centers, or production lines and tools used in the manufacturing of
products. Determine the number of resources used in APO planning for both Supply Network Planning and Detailed
Scheduling.
APO - Sales and Specifics for Sales and Purchase Orders - SAP liveCache Memory
Purchase Orders -
The average number of forecast orders used for planning asks for the number of location-product
SAP liveCache
combinations, with a forecast that is released from Demand Planning to Supply Network Planning. Each location-
Memory
product combination is considered one forecast order.
FORECAST
The average number of schedule lines per forecast order refers to the number of partitions made for each
time bucket in Demand Planning. So, if the forecasts from Demand Planning are in monthly time buckets, and SNP
plans in daily time buckets, then the average number of scheduled lines per monthly forecast is 30.
The average number of planning relevant purchase orders or purchase requisitions. The number of
planning relevant purchase orders include only those purchase orders that are not yet filled. Those that are will be
PURCHORD deleted from liveCache. However, until payment is completed, they will still reside in R/3. For this reason, more
purchase orders often reside in the backend system than in APO.
The average number of delivery schedules per purchase order or purchase requisition asks for the
number of transports required for the average purchase order.
The average number of sales orders used for planning. Those orders that are satisfied are not relevant for
SALES planning, because they are deleted from liveCache. However, they still reside in R/3, until payment for the sale is
fulfilled. So, there are typically more sales orders in the backend system than in APO.
The average number of delivery schedules per sales order. Determine how many transports, on average,
are required for a sales order.
Average number of transfer orders used in planning. These are internal stock transfers generated by the
TRANSFER APO SNP planning process. This number is typically a count of vehicles generated from a Transportation Load
Builder (TLB) planning run.
Average number of products per transfer order asks for a count of products that are grouped into a transfer
order from a TLB planning run.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 27 of 59
Back to Top
Order Fulfillment
Sizing Elements We size the memory requirements of the ATP time series in liveCache. The CPU sizing is determined by the different ATP
checks.
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 28 of 59
Planning processing in Service Parts Planning can also be done for partial product volumes, e.g.: fast moving parts with
weekly planning and slow moving parts with monthly planning.
For DRP a trigger based process is available. When triggers are used please consider that DRP always calculates the
whole BoD subtree below an entry location (one trigger can impact the calculation of multiple location products).
Example assumptions:
Service Parts
Planning - Assume you have five locations (one global distribution center and four regional distribution centers) and in total
Example 100,000 different products. The global distribution center stores all 100,000 products, each regional center stores
50,000 products.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 29 of 59
Back to Top
Integration to ECC
Sizing Elements The CPU sizing is determined by the load generated by the integration. Only the SCM system is considered in the sizing
result.
PI-STOCK
Back to Top
Extended Definition
Warehouse Extended Warehouse Management (EWM) offers you flexible, automated support for processing various goods movements
Management and for managing stocks in your warehouse complex. The system supports planned and efficient processing of all logistics
(EWM) processes in your warehouse.
If you manage your warehouse stocks using the application component Inventory Management (MM-IM), then you
manage the material stocks based on quantity and value in several storage locations.
In contrast, EWM gives you the option of mapping your entire warehouse complex in detail in the system, down to
storage bin level. Not only do you gain an overview of the entire quantity of a material in the warehouse, you can also
always determine exactly where a certain material currently is in your warehouse complex. With EWM, you can optimize
the use of various storage bins and stock movements, and can store together material stocks from several plants in
random storage areas. Using EWM, you can control and optimize various processes in the warehouse.
EWM is completely integrated into Inventory Management and Delivery Processing. Business processes, which you trigger
in other application components, lead to physical goods movements in your warehouse. You organize, control, and
monitor these goods movements using EWM.
Note
In the Quick Sizer we distinguish between inbound and outbound delivery processes.
For good response times choose CPUs with a good single-thread performance.
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 30 of 59
Optional: Change of resource in movement from deconsolidation packing to final bin (IEWM-RESFI)
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 31 of 59
Deconsolidation
Packing to Final
Bin
IEWM-RESFI
EWM - Inbound Find this example to see how the fields could be filled-in.
Delivery Process
During the peak hour the following process steps are executed in the system:
Example
100 inbound deliveries with four items on average are created based on messages received from ERP. Each item is
packed in two highest-level HUs.
Enter for sizing element IEWM-DLV: objects = 100 deliveries , items = 4 items per delivery
50% make use of system based unloading with unloading warehouse tasks for the highest-level HUs.
Enter for sizing elements IEWM-UNTSK and IEWM-CONF: wareh. tasks = 400 (50% * 100 * 4 * 2)
For each received HU a (first) warehouse task is processed, either to deconsolidation station or for direct putaway
(in case the reveived HUs are applicable for storage). Bundling of these warehouse tasks is always a single
warehouse task per warehouse order. 30% of received HUs are applicable for storage and are not deconsolidated.
Confirmation of these 30% warehouse tasks is done by GUI (not RF) and the putaway is done with a single
resource.
Enter for sizing element IEWM-PACON: wareh. tasks = 800 ( 100 deliveries * 8 highest-level HUs), % RF = 70%
RF based confirmation
Enter for sizing element IEWM-PATSK: wareh. tasks = 400 (800 – 400)
The move warehouse tasks going to deconsolidation are processed with one resource change.
Enter for sizing element IEWM-RESPA: wareh. tasks = 560 ( 70% * 800 highest-level HUs), rschg = 1 (one
resource change)
560 received highest-level HUs are deconsolidated into 280 putaway HUs, each containing a single product.
Enter for sizing element IEWM-DECON: HUs = 280 putaway HUs after deconsolidation, items = 1 putaway item per
HU, unpack. items = 0
The 280 HUs created in deconsolidation are applicable for storage, so no split of those HUs into multiple putaway
warehouse tasks per HU is done.
Enter for sizing element IEWM-MOVE: wareh. tasks = 280 HU warehouse tasks
Put-away of those 280 HUs needs two times a resource change (for example those HUs are going to high rack).
Enter for sizing element IEWM-RESFI: wareh. tasks = 280 ( 280 HUs) , rschg = 2 (two resource changes)
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 32 of 59
EWM - Simple Find this example to see how the fields could be filled-in.
Outbound
During the peak hour the following process steps are executed in the system:
Delivery Process
Example 500 outbound delivery orders with two items on average are created based on messages received from ERP.
Enter for sizing elements OEWM-DLV and OEWM-GOODS: objects = 500 deliveries , items = 2 items per delivery
Each delivery item is picked with a single picking warehouse task. Average size of a warehouse order is one
picking warehouse task. A full pallet is picked, pallets play the role of picking and shipping HU:
Enter for sizing element OEWM-PICK: wareh. tasks = 1000 pick warehouse tasks
Enter for sizig element OEWM-CONF: wareh. tasks = 1000 pick warehouse tasks , % RF = 100% RF
The full pallets are moved to staging area, including on average two resource changes (the pick resource plus two
others take part).
Enter for sizing element OEWM-DEST: wareh. tasks = 1000 HU movement warehouse tasks
Enter for sizing element OEWM-RESPI: wareh. tasks = 1000 , rschg = 2 (two resource changes)
Enter for sizing element OEWM-PACK: HUs = 0 (no repacking), items = 0
Enter for sizing element OEWM-STAGE: wareh. tasks = 0
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 33 of 59
EWM - Highly Find this example to see how the fields could be filled-in.
Complex
During the peak hour the following process steps are executed in the system:
Outbound
Delivery Process 100 outbound delivery orders with four items on average are created based on messages received from ERP.
Example Enter for sizing elements OEWM-DLV and OEWM-GOODS: objects = 100 deliveries , items = 4 items per delivery
On average, each delivery item is picked via two picking warehouse tasks (whole delivery quantity can not be
managed with a single warehouse task). Average size of a warehouse order is five picking warehouse tasks. All
five picking items are picked into a pick HU with RF (->160 pick HUs are created).
Enter for sizing element OEWM-PICK: wareh. tasks = 800 pick warehouse tasks
Enter for sizig element OEWM-CONF: wareh. tasks = 800 pick warehouse tasks , % RF = 100% RF
Pick HUs are beeing moved by pick resource (small fork lift). 40% of them are dropt to be overtaken by one other
resource which moves them to packing station, the 60% rest is directly moved to packing station.
Enter for sizing element OEWM-DEST: wareh. tasks = 160 HU movement warehouse tasks
Enter for sizing element OEWM-RESPI: wareh. tasks = 64 ( 40% * 160) , rschg = 1 (one resource change)
During RF based packing, the pick HUs with five items each (cross delivery ! ) are repacked into shipping HUs with
four items.
Enter for sizing element OEWM-PACK: HUs = 100 HUs, items = 8 ( 4 delivery items * 2 picking warehouse tasks
per delivery item)
Shipping HUs are beeing moved to staging area by a single resource (without resource changes).
Enter for sizing element OEWM-STAGE: wareh. tasks = 100 HU movement warehouse tasks
Enter for sizing element OEWM-RESST: rschg = 0 (no resource change)
30% make use of system based loading with loading warehouse tasks.
Enter for sizing element OEWM-LOAD: wareh. tasks = 30 HU loading warehouse tasks (30% of objects of sizing
element OEWM-STAGE)
Goods issue is performed for the 100 deliveries.
Back to Top
SAP Definition
Transportation SAP Transportation Management (SAP TM) supports you in all activities connected with the physical transportation of
Management goods from one location to another. You can use SAP TM to perform the following activities, for example:
Create forwarding orders for your ordering parties
Transfer orders and deliveries from an ERP system
Create freight bookings
Plan the transportation and select carriers
Tender transportation services
Dispatch and monitor the transportation
Calculate the transportation charges for both the ordering party and the supplier side
Consider foreign trade and dangerous goods regulations
You can use SAP TM to create and monitor an efficient transportation plan that fulfills the relevant constraints (for
example, service level, costs, and resource availability). You can determine options to save costs and to optimize the use
of available resources. You can react to transportation events and find solutions to possible deviations from the original
transportation plan.
Scenario: Direct creation of Freight Orders
Example situation: A shipper (e.g. a manufacturer) distributes products through its network of plants, distribution centers
and 3rd party warehouse operations. The Logistics organization of the shipper is responsible for the timely, cost effective
and efficient transport between and from their facilities to the end customer. The shipper receives orders electronically in
SAP Transportation Management (TM) via Sales Orders created in ERP Sales and Distribution. Within TM, these orders are
directly transferred into corresponding Freight Orders. The shipper determines carriers for the Freight Orders and
executes a tendering process. The finally selected carriers execute the transportation. In TM, the shipper calculates the
freight costs and finally creates freight settlement documents for payment of the transport.
This shipper scenario (for a throughput-based sizing) consists of the following steps, where some of them are optional:
1. Creation of Order Based Transportation Requirements (OTRs) in TM, based on Sales Orders received
from ERP
2. (Optional) Carrier selection for the Freight Orders
3. (Optional) Tendering of Freight Orders to Carriers
4. Calculation of Transportation Charges for the Freight Orders
5. Create Freight Settlement for the Freight Orders
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 34 of 59
(Optional) Specifics
Tendering Objects:
TM-TENDER Number of Freight Orders to be tendered.
Carriers:
Average Number of carriers used in the tendering process.
Costs:
Determination of costs: Internal Costs or Charge Calculation
Choose either
'Lanes: internal costs from Lanes',
'SCC: Simple Charge Calculation' or
'CCC: Complex Charge Calculation'.
Note: For medium charge calculation, choose 'CCC: Complex Charge Calculation'.
Calculation of Specifics
Transportation Objects:
Charges Number of Freight Orders to be calculated
TM-CHA-CAL C.Complexity: (C.Compl.):
Complexity of Charge Calculation:
Choose either
List of simple charge elements with flat rates ('Simple: Charge elements with flat rates'),
List of charge elements with rates determined from related rate tables ('Medium: Charge elements with rate
from rate tables') or
List of charge elements with flat rates, relative rates, percentages, and rates determined from related rate
tables ('Complex: Rates: flat, relative, percentage and tables')
Freight Specifics
Settlement Objects:
TM-FRE-SET Number of Freight Settlement Documents
Cost Determination (Cost Det.):
Determniation of costs
Copy all charges from Freight Order
Copy fixed charges and redetermine others
Choose either
List of simple charge elements with flat rates ('Simple: Charge elements with flat rates'),
List of charge elements with rates determined from related rate tables ('Medium: Charge elements with rate
from rate tables'),
List of charge elements with flat rates, relative rates, percentages, and rates determined from related rate
tables ('Complex: Rates: flat, relative, percentage and tables') or
List of all charges from Freight Orders ('Order: All charges from freight orders')
Example The following example shows how the sizing elements could be filled:
Sales Orders / OTRs (Table 1: Throughput- Creation of OTRs and Freight Orders)
Sales Orders with 5 items in average are created in ERP and transferred to TM where corresponding 1.000 OTRs with 5
items each are created from these Sales Orders.
Fill-in average sizing element TM-OTR:
'Objects' = 1.000,
'Items' = 5
'Freight Ord.' = One Freight Order per OTR header
(Optional) Carrier Selection (Table 2: Throughput - Carrier Selection and Tendering)
For each of the 1.000 Freight Orders a Carrier Selection is executed with an average number of 5 carriers, based on
internal costs defined on the involved lanes.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 35 of 59
Back to Top
The business objects are created via the Web Dynpro UI, and they are complex. This means that all or at least
most features of the business object are used (for example conditions, schedule lines, distribution functions,
internal notes, IPC pricing).
Use this scenario for all online users. If you use only a few object features, you can use scenario 2 approach for
complex business objects and the scenario 1 approach for simple objects.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 36 of 59
SRM-CTR-1U: Simple contract scenario with few complex steps – number of users
SRM-CTR-2U: Complex contract scenario with many simple stpes – number of users
SRM-CTR-1: Simple contract scenario with few complex steps – number of documents
SRM-CTR-2: Complex contract scenario with many simple stpes – number of documents
Example
If you transfer purchase requisitions from SAP ERP to SAP SRM, you can use the Professional Shopping Cart scenario 1 to
perform the sizing for these objects.
For the objects invoice, confirmation, and shopping cart wizard (occasional shopping cart), there is no need for a
distinction between the two scenarios hence the above naming convention does not apply to these objects.
Contract Definition
SRM-CTR-1U, A central contract is a legally binding agreement between a purchaser and a supplier. It defines the purchase and supply
SRM-CTR-2, of goods or services at agreed prices and conditions, such as rebates and quantities to be ordered. A strategic purchaser
SRM-CTR-1, typically creates a central contract as soon as it becomes clear that the relationship with a supplier will be long-term. The
SRM-CTR-2 quantity and value of purchase orders (POs), limit confirmations, and invoices are released against the central contract.
Specifics for Contract Input
Enter the number of users
Enter the number of documents which are created
RFx Definition
SRM-RFX-1U, Purchasers can create RFx documents for products and services. RFx can be created from scratch, in the SAP Bidding
SRM-RFX-2U, Engine, or directly from a central contract. Using RFx as a basis, suppliers bid on the products and services that are
SRM-RFX-1, required, allowing the purchaser to determine the most suitable source of supply.
SRM-RFX-2
The term RFx is used as a general term for the type of document a purchaser sends out to potential bidders. Purchasers
can create any type of document, or transaction type they choose, such as a simple request for information, or a request
for a quote.
Specifics for RFx Input
Enter the number of users
Enter the number of documents which are created
Occasional Definition
Shopping Cart The shopping cart wizard is the default user interface for employees and is less complex than the professional shopping
SRM-OSC-U, cart.
SRM-OSC
Specifics for Occasional Shopping Cart Input
Enter the number of users
Enter the number of documents which are created
Professional Definition
Shopping Cart This user interface is available to fill shopping carts with products quickly and easily.
SRM-PSC-1U,
Specifics for Professional Shopping Cart Input
SRM-PSC-2U,
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 37 of 59
Confirmation
Definition
SRM-CONF-U,
Confirmation of goods delivery, services rendered and hours worked. Purchasers can create confirmations themselves,
SRM-CONF
even if the purchase order is in the back-end system. It is possible to create express confirmations directly in the Check
Status application without having to switch to another application.
Specifics for Confirmation Input
Enter the number of users
Enter the number of documents which are created.
Invoice Definition
SRM-INV-U, Display and process invoices.
SRM-INV
For invoices that you create with reference to a purchase order, the system automatically supplies the data from the
system in which the purchase order was originally created (local purchase order or back-end purchase order).
Specifics for Invoice Input
Enter the number of users
Enter the number of documents which are created.
Back to Top
Global Trade
Definition
Services (SAP
SAP Global Trade Services (SAP GTS) automates global trade processes and enables you to manage large numbers of
GTS) Compliance
business partners and material as well as high volumes of documents, while also helping you to comply with changing
and Customs
legal regulations. It facilitates foreign trade by providing you with the tools you require to respond to governments
Management
modernizing their systems and communicating electronically with businesses.
GTS-CUMA,
GTS-SLS, SAP GTS supports international trade compliance issues in three primary areas:
GTS-FI,
Sanctioned party list (SPL) screening
GTS-BP,
Import/export control
GTS-MAT,
Embargo checking
GTS-SCREEN
SAP GTS also supports automated and standardized customs processes including, for example, electronic communication
with the customs authorities. It speeds up the release of goods by the customs authorities in the following areas:
Import processing
Export processing
Transit procedure
The following are the technical elements used for SAP GTS sizing and their explanation:
GTS-CUMA – GTS Customs Documents (Import/Export Customs Declarations and Customs Shipments, Transit
Documents)
GTS-SLS – GTS Compliance Documents (Sales Orders, Deliveries, Purchase Orders)
GTS-FI - Screening of payment (Sanctioned Party List Screening for Financial Accounting)
Due to tighter control measures and legal regulations implemented by the European Union on foreign payment
transactions, it is necessary for companies that operate on a global level to provide evidence of checks performed
on incoming and outgoing payments. This involves checking business partners in accounting transactions against
published sanctioned party lists.
Your company can insure that sanctioned persons, groups and organizations are recognized in advance of payment
transactions taking place, and, as a result, prevent transactions being performed. These sanctioned parties are
published and updated on a regular basis in different countries and by different organizations, and may contain, in
some cases, the same sanctioned parties.
You should enter the number of FI payment documents and the average number of invoice line items you plan to
screen during automatic transactions (F110 and F111) and during manual payments with printout (FBZ4).
Technically, the number of entries in FI database table REGUH can give you a guideline for the number of payment
documents whereas the number of entries in FI database table REGUP can help to derive the average number of
invoice items.
GTS-BP – Business Partners Master data (Vendors, Customers, Employees, etc)
GTS-MAT – GTS materials
GTS-SCREEN – Periodic GTS screenings (B1, B2, C1, C2)
All the above are to be used considering annual volumes by using the Average (rows with A -Y after the technical
description) or Peak (row with P-P after the technical description) sizing methods, excepting for GTS-SCREEN, which is
explained in more detail below.
Note for GTS Business Partner & Documents Screening (GTS-SCREEN)
The column "documents" refers to the B2 (Periodic) and C2 (SPL update) scenarios, which check document addresses.
B2 Scenario
With the B2 scenario you can check periodically addresses in documents which have already been checked.
Therefore, from a business perspective, this scenario is to be run only when GTS is first implemented to check on
documents which have already been processed either manually or if you were using a different vendor software.
To do this, you will have first to mass transfer the documents and then run the B2 scenario. Since it is
recommended to transfer the documents and run the scenario BEFORE GTS is live and it is to be run only once, for
sizing purposes, you should run a separate calculation with the quick sizer ONLY with the number of documents in
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 38 of 59
GTS-SCREEN which you have mass transferred previously. This will give you a number of SAPS which should be
required for this process, since there are no other processes consuming resources at the same time. Notice that
since the documents have been already processed (and probably shipped), this B2 scenario is run for purely
informative purposes, as you cannot take any logistic action on the documents. Also notice that there will be audit
trail records available to be checked in case of an audit.
C2 Scenario
With the C2 scenario you can check addresses in documents which have already been checked when there has
been a recent SPL data update. Therefore, from a business perspective, this scenario is to be run only when an
SPL update has been implemented to check on documents which have already been processed. Have in mind that
since there is new SPL data, you may get new SPL matches in documents that did not get any matches before,
and that there will be an audit trail record which can be checked later in case of an audit.
Given that SPL updates are normally issued monthly (this is just a rough guideline which depends on your data
provider), the recommended number of documents to be used for sizing purposes is one-twelfth (1 /12) of the
yearly number of documents being considered for GTS Compliance Management (GTS-SLS at standard throughput
sizing)
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 39 of 59
Example
In our example we have an average of 2,800 ( = (3 * 5,000 + 3 * 600) / 6) records per planning step.
Note
The term planning step is often understood from a business view, where it means a total run of a planning
area. Here, we take a functional perspective.
The memory requirement and CPU consumption is estimated on the basis of this data. To determine
memory requirements, we assume that there is an average data record length of 1KB.
Example
As mentioned above the planning functions work through different sets of data. The maximum number is 5,000
per hour and user.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 40 of 59
Example
Take the example mentioned above. If the user doesn't leave the transaction, he holds 6,800 (5,000 + 600 + 600
+ 600) records in memory. Please keep in mind, that the set of data is the sum of records read and records
created.
SAP NetWeaver Find information for the columns of this table below:
BW powered by BW Users (column "BW user") - Definition
HANA - User In NetWeaver BW, we distinguish roughly between user types according to their frequency of activity and the
Groups: Reporting reporting they will normally do.
& Analysis
H-BW-INFO, Active User Type Navigation Steps per Hour This user will
H-BE-BUSI., predominantly ...
H-BW-EXPER
Information Consumer 1 ... view predefined and static
reports
Business User 11 ... navigate within reports, do
slicing and dicing, but usually
cause moderate system load
BW Expert 33 and more ... run ad-hoc queries with a
high probability of causing
significant database load
A navigation step includes drilling down in the reports and corresponds to nine dialog steps in the SD
benchmark. If you don't know the user distribution, a typical ratio in the NetWeaver BW environment is
71% : 26% : 3% (Information Consumer : Business User : BW Expert).
Comment
The system automatically calculates the Java parts which are shown at the result level.
If BW Java is not used, you should add 5 % to the SAPS of the application server.
Report Viewing, OLAP Analysis, and Data Exploration (columns "Report.", "OLAP", and "Explor.") -
Definition
Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an
InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you
like for each InfoProvider.
For sizing purposes we distinguish between three query types which are defined by the load they create in the
system.
Report Viewing: Predefined, static, reports causing insignificant database load
OLAP Analysis: Slicing and dicing, navigating in reports
Data Exploration: Data mining, that is ad-hoc reports with unpredictable navigation paths, access of
detail data, full table scans
Any user can do any type of query. However, experience shows a certain activity pattern, as you can see in
the table below.
Web JAVA Reporting / Integrated Planning (columns "Web" and "IP") - Definition
In NetWeaver BW, reporting can be done either through the Excel based BEx Analyzer or through a Web browser
which receives HTML documents from a JAVA engine. If you use Web Reporting, you need to check the flag "Web"
and enter the corresponding number of users. If you use both, Web based Reporting and BEx Analyzer, you have
to enter the respective user numbers for both groups in individual lines of the QuickSizer. To create more lines in
table 2, mark the lines for the required user categories, select the number of copies and click on "Insert".
Another property of queries which has an impact on sizing is their input capability. Usually, queries used for
Integrated Planning are ready for input. If a query can accept input, then you need to check the flag "IP". Like in
the case above, you have to create separate lines in table 2 for users who use input queries and for those who
don't.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 41 of 59
BW_HANA_TA source database and the memory requirements of these tables in HANA. We strongly recommend using the default
value if you do not have reliable information justifying a different compression factor.
SAP NetWeaver
BW powered by Definition sizing element DS-OBJECTS
HANA - Definition A DataStore Object serves to store consolidated and debugged transaction data at a document level (atomic level). It
of DataStore describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or
Objects on HANA InfoSet Query.
DS-OBJECTS A DataStore contains a key (for example, document number/item) as well as data fields that can also contain character
fields (for example, order status, customer) as key figures. The data of a DataStore Object can be updated with a delta
update into InfoCubes and/or other DataStore Objects in the same system or across systems. Write-optimized
DataStore objects serve as storage for an inbound data layer. While these objects provide much faster data load, they
do not offer delta information.
In contrast to multi-dimensional data storage with InfoCubes, the data in DataStore Objects is stored in transparent,
flat database tables.
Specifics for DataStore Objects
NumFld (Numeric fields)
Enter the number of numeric fields in the DSO
TxtFlds (Text fields)
Enter the number of text fields in the DSO
CharLg (Character length)
Enter the average length of character fields in bytes
WO (write optimized)
Flag, if DataStore Object is write-optimized.
Compression factor
Enter the compression factor, i.e. the ratio of the sizes of uncompressed data tables (without their indexes) on
the source database and the memory requirements of these tables in HANA. We strongly recommend using the
default value if you do not have reliable information justifying a different compression factor.
Initial load
Enter the number of records initially loaded into the cube
Period. Upld (Periodic upload)
Enter the number of records loaded during the periodic upload process
Period
Enter the total number of uploads which will be kept in the InfoCube
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 42 of 59
Back to Top
SAP Find information about SAP BusinessObjects BI on the SAP Community Network -> BusinessObjects BI. Also see the
BusinessObjects Sizing Companion Guide .
Business
Intelligence (BI) Please refer to example project ‘BO_BI_V26.’ with customer number 188213.
BusinessObjects Each row of the table represents a different BI client tool. You can specify inputs for one or more of the client tools at the
Business same time depending on which BI client tools will be used in the deployment. Since the BI client tool names have been
Intelligence abbreviated in the table, you can see below for the full product names:
ANA-OLAP, SAP BusinessObjects Analysis, edition for OLAP (ANA-OLAP)
CRYST-2011,
CRYST-ENT, SAP Crystal Reports 2011 (CRYST-2011)
DASHBOARD,
WEB-INTEL SAP Crystal Reports for Enterprise (CRYST-ENT)
Note
SAP BusinessObjects Explorer is not currently included in this version of the Quick Sizer. Please see SAP Note 1398242
for Explorer sizing materials.
Find information for the columns of this table below:
Information Consumers (column 'Info') – Definition
The least active of all the user types. Information consumers spend an average of 300 seconds (5 minutes) idle in
between navigation steps. These users typically view predefined and static content and perform relatively little
drilling and filtering on their own.
Business Users (column 'Business') – Definition
These users perform some moderate amount of drilling and filtering on their own. Business users spend an
average of 30 seconds idle in between navigation steps.
Expert Users (column 'Expert') – Definition
The most active of all the user types. Expert users spend an average of 10 seconds idle in between navigation
steps. These users are much more likely to perform resource-intensive operations in the system including ad-hoc
analysis and customization of reports, retrieving a large number of rows, and heavy client-side filtering.
Note on users (columns 'Info', 'Business', and 'Expert')
The number of users you specify for any user type represents active concurrent users, or put another way,
the number of users generating simultaneous requests in the system. The ratio of active concurrent users to
total user population can vary depending on many factors. One rule of thumb is to assume that 10% of all
users might actually be logged-in at the same time, and of those logged-in users 10% would be generating
simultaneous requests. In short, 1% of your total user population.
% of Small Reports (column '% S') – Definition
The expected percentage of small documents in the system.
% of Medium Reports (column '% M') – Definition
The expected percentage of medium-sized documents in the system.
% of Large Reports (column '% L') – Definition
The expected percentage of large documents in the system.
For more information about the report and dashboard document structures and sizes, please see the Sizing Companion
Guide.
Back to Top
Industry Solutions
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 43 of 59
3rd step: Execution of the credit risk exposure calculation (can be done on a daily basis)
4th step: Historization run (is normally not done daily; no sizing available)
5th step: Data extraction to NetWeaver BW (can be done daily)
6th step: Regulatory reporting interface (is normally not done every day)
Specifics for CPU Sizing
For the CPU sizing only the peak values are taken into account. For each step you have to specify the start and end time.
In addition for each step you have to specify the number of objects that have to be processed.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 44 of 59
Regulatory Definition
Reporting Regulatory reporting consists of two parts:
Interface (6th Writing enriched data to the cluster
step) Creating of a file on a file system
REG-REPORT
Sizing considers only the first one.
Back to Top
Statement Definition
FS-BK-STAT The on request bank statement process embraces the selection of all data (postings, balances, settlement details) that
are necessary to provide a bank statement data of an account.
Specifics for Statement
Enter the number of bank statements that are requested in a peak period.
Settlement Definition
FS-BK-SETT The settlement process embraces the calculation of interest and periodic charges for an account and the posting of the
results to the settled or a deviate account.
Specifics for Settlement
Enter ther number of accounts to be setlled per peak period.
Correspondence Definition
FS-BK-CORR The correspondence process embraces the creation of all types of customer correspondences (e.g. bank statements,
correspondences for contract changes, correpondences for special posting events). This correspondence is started
asynchronously e.g. once every day.
Specifics for Correspondence
Enter the number of created documents that have to be processed within a peak period.
Accruals Definition
FS-BK-ACCR The accrual process embraces the calculation of interest and periodic charges for an account. Results are transferred to
general ledger in a subsequent process for the purpose of accrual.
Specifics for Accruals
Enter the number of accounts to be accrued per peak period.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 45 of 59
Back to Top
General Remarks To correctly size Insurance with the Quick Sizer you must also fill-in the sizing elements Subledger, Dunning, Payment lot
for the Insurance (CD-PL) and Payment run (PAY-RUN) available on the Quick Sizer questionnaire under ERP -> Financials -> Contract
questionnaire Accounting.
Definition
Broker
The intermediary (for example broker) between the insurer and the insured. The insurance settlement process can be
BROK-ITEM
carried out either directly with the customer or via the intermediary (hereafter called broker). In Financial Services -
Collections & Disbursement there are two different scenarios:
Scenario 1: Communication and payment take place directly between the insurance company and the insured. In
this scenario the typical master record model is set up as follows: 1 business partner has 1...n accounts, to which
1...n insurance objects are assigned. Payments and correspondences are based on the CD documents posted to
the customer accounts.
Scenario 2: In the scenarios that involve brokers, the master data does not only consist of the customer master
data and the postings, but also of the "broker master data". For the broker additional master data is created:
Business Partner (Intermediary, Broker) --> Contract Account (Broker Account) --> Insurance Object (Broker
Contract). On the insurance contract level it is possible to specify and control for specific periods of time, whether
the broker is also responsible for collections and disbursements. Broker collections offers an additional function
called broker report. When a broker report is posted, the relevant items are transferred to the broker account, via
a transfer posting. In addition, the broker may also have a commission account. The commissions are also posted
to the broker account together with the broker report. In the end only the balance is settled with the broker,
which, compared to Scenario 1, considerably reduces the number of payment transactions, because a broker is
usually responsible for several customers at once.
Relevant is the number of broker report items which are reported by all brokers during the period. This includes all
reported premiums, claims, commission and cost items.
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 46 of 59
Definition
Retail The Retail system is a variation of SAP Standard code which is tailored to fit the volumes and processes which are specific
to a Retail functionality. Instead of dealing with materials and warehouses, this deals with locations/stores, articles and
distribution centers and is engineered to handle the high potential volumes of input data representing the point-of-sale
(POS) data collected at a register. There are six basic processes dealt with from a sizing viewpoint and these represent
the key processes in the daily cycle of a retail operation.
Note for the Questionnaire SAP for Retail within the Quick Sizer
Questionnaire
The questionnaire SAP for Retail contains input fields which must be filled with the results you get with the help of the
SAP for Retail in
retail sizing questionnaires (Sizing SAP Retail Questionnaire, Sizing Forecasting and Replenishment, Sizing SAP POS Data
the Quick Sizer
Management) which reside on the Service Marketplace: http://service.sap.com/sizing -> Sizing Guidelines -> Solutions &
Platform
Comments
Retail environment puts heavy load on the tables listed above and they are considered separately for proper disk sizing.
1. Non-aggregated sales data is sent to POS DM and stored in the TLOG tables.
2. Process non-aggregated data to create aggregated sales IDocs (message type WPUUMS), payment type
IDocs (message type WPUTAB), FI-IDocs (message type WPUFIB).
3. Send IDocs across to the ERP system via report RSEOUT00 for further processing.
Results are the peak SAPS-requirements. Here, use ratio 1:3 for the distribution of the SAPS between DB and AS.
Please enter the results you get if you follow the instructions within the sizing guideline "Sizing SAP POS Data
Management" in the corresponding columns SAPS (DB, ABAP, JAVA), memory (DB, ABAP, JAVA), and disk.
Point Of Sale Download (R-POS-DL)
POS Download is the processing within ERP to prepare data (prices, new articles, promotions etc) to be sent down
to the stores. Each price change, new article, article in a promotion is considered as a "change" that needs to be
sent down to the stores.
Enter the SAPS numbers provided by the Retail Sizing Questionnaire in the corresponding fields "DB SAPS" and
"ABAP SAPS".
Retail Masterdata (R-Master)
This section estimates the disk capacity required to store the master data. Please fill in the fields as shown in the
Retail Sizing Questionnaire.
Comment
The actual processing cycle for POS Data Management (DM) is considered to be a once daily activity. If this is not the
case, then the POS DM sizing will need modification to correctly consider the execution cycle proposed.
Definition
Questionnaire SAP Forecasting and Replenishment (F&R) supports retailers in their daily replenishment. It must be executed exactly
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 47 of 59
once each day for all location product combinations which are defined as relevant for F&R and therefore has strong
SAP Forecasting requirements in terms of throughput.
& Replenishment
The application is located on an SAP SCM system, but also requires another leading ERP system for stock keeping,
purchase order creation or master data maintenance (this can be an SAP ERP system, but this is not a requirement). F&R
on SCM also contains additional software (Forecasting and Replenishment Processor (FRP)) which is executed on the
application servers at the operating system level and also needs current information for master data and transactional
data.
F&R needs to be updated with current data by the ERP system before it can execute its calculations and then transfer the
result as “order proposals” to the purchasing system. F&R sizing however refers only to processes which are running on
the SCM system.
The sizing in the Quick Sizer is a simplified calculation considering only the process steps which are usually the most
critical ones in terms of throughput for F&R. This gives you the possibility to get an estimation on the order of magnitude
for the required system landscape even before you have defined in detail how to run the application (there is also a more
detailed sizing for F&R considering significantly more data, but this requires a good insight to the application and the way
it will be configured. You can find the more detailed sizing for F&R on the service marketplace:
http://www.service.sap.com/~sapidb/011000358700000190022007E).
The simplified sizing in Quick Sizer refers to the following four steps:
1. Synchronization of F&R master data from F&R to FRP
2. Synchronization of order data from F&R to FRP
3. Processing of consumption data (and possibly stock data)
4. FRP run (including execution of all calculations, creation and transfer of the order proposals)
The business logic of F&R requires that these steps are performed in a certain sequence. The sizing model basically
assumes that these steps are executed in sequence, i.e. a given step can only be executed when the previous one has
finished completely. However, it is also possible to run certain steps together: You can run step 1 and 2 together.
You can even run the steps 1, 2 and 4 together, but step 3 must always run before step 4, so you need to run step 3
before this block.
Note:
There is an example project for SAP Forecasting & Replenishment for customer 188213 password "RETAIL F&R V20 F".
Definition
Master Data
In this process step all master data is transferred from F&R to FRP so that FRP has current information for its calculations.
synchronization
This data set does not contain order data, stock nor consumption information.
R-MDS
Specifics for master data synchronization
Location products
In this column you enter the number of all location product combinations which are relevant for F&R, i.e. for which
replenishment is performed with F&R.
Start time/ End time (S.t. / E.t.)
Start and end time describe the time frame in which this process step is executed.Location products:
Definition
Order Data
In this process step all data on open orders is transferred to FRP so that FRP has current information for its calculations.
synchronization
R-ODS Specifics for master data synchronization
Order proposal items (OP items)
In this column you enter the total number of order proposal items which are created by F&R per day in average.
Order proposals residence time (OP res.time)
In this column you enter the number of days which usually lies between the creation of an order and the complete
delivery.
Checkbox WMDS (With master data synchronization)
Activating the checkbox “WMDS” indicates that this step is executed together with the step described in element R-
MDS.
Start time/ End time (S.t. / E.t.)
Start and end time describe the time frame in which this process step is executed. This entry is ignored if the
checkbox WMDS is active.
Definition
Processing
In this step all information on the consumption data (i.e. sales data and/or goods issue data) of the day is processed, i.e.
Consumption
a time series is updated.
(and Stock) Data
R-PCSD Specifics for master data synchronization
Depending on the process setup the current stock information is also updated by reducing the current amount for a
location product by the amount of the corresponding consumption data record. This is necessary if the process
configuration makes use of the option that stock data can already be updated in F&R before the consumption data for the
day is available.
There is also the option that the consumption data for the day is first processed in the ERP system and then the stock
data is transferred to F&R. This makes it necessary to update the stock information in F&R in this process step too.
Location products
In this column you enter the peak number of aggregated consumption data records per day. This means that there
is only one record for each location product combination.
Example: Let’s assume you have non-aggregated consumption data as follows:
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 48 of 59
Definition
FRP Run
In this step all activities are considered which are necessary for forecasting, demand requirement determination, order
R-FRP
creation etc.
Specifics for master data synchronization
Location products of R-MDS
The value for this non-entry field is taken from the corresponding R-MDS input field.
Order proposal items (OP items of R-ODS)
The value for this non-entry field is taken from the corresponding R-ODS input field.
Start time/ End time (S.t. / E.t.)
Start and end time describe the time frame in which this process step is executed. All information concerning the
data volume is derived from other elements (R-MDS, R-ODS).
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 49 of 59
Gas consumption
Water consumption
Waste water
Metering services
Additional info lines which are all non-posting relevant lines. This can include:
Consumption
Control readings
In any of these cases the average number of lines per single bill is requested in this sizing.
Contracts (Contracts)
A contract is an agreement between a business partner and the utility company that applies to a single division.
Therefore, this entity is quite similar to the legal contract the business partner has with the utility company to get
electricity, gas, water or some similar service. For example, if a company sells electricity to 500,000 customers
and gas to 100,000 customers, it would have 600,000 contracts with their business partners.
Meters (Meters)
The number of meters to be read. Meters in the stock are not to be counted here. Here it is asked for meters as
this device is quite familiar to everyone. A more correct input here would be the number of registers, but as
usually the relationship is 1:1 for the majority meters work as well. However, if the customer has a lot meters with
two registers, one e.g. for day- electricity and one for night-electricity, it would be better to enter the number of
registers instead.
Master Data and Specifics for Master Data and Transactional Data
Transactional Business partners (BusPartner)
Data for Disk A business partner is a natural person, organization, group of natural persons, or group of organizations in which a
Sizing - Part II company has a business interest. A business partner may be a person, organization, or group within a company,
UTIL-02 such as 'Mrs. Lisa Davies', 'Repro Electrical Products Inc.', or 'The tenants of 15 Charles St.'.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 50 of 59
Customer Comment
Overview (CPU Enter how often you use the transaction "Customer Overview".
Background
Sizing)
OVERVIEW
Customer Contact Find the definition above at Disk Sizing → Customer contacts per year.
(CPU Background
Sizing) Comment
CONTACT Enter how often you create customer contacts with the respective transaction. Attention: when using a CRM system
together with the IS-U system, the customer contacts are recorded in the CRM system and therefore the question is
irrelevant here.
Back to Top
SAP NetWeaver
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 51 of 59
AFP: Ajax Framework Page with SAP Signature Design (the portal’s new framework page by default) and
Classic Design
Check also SAP Help Portal for more information on this
http://help.sap.com/saphelp_nw73/helpdata/en/48/1fee2f80093184e10000000a42189b/frameset.htm.
Back to Top
SAP NetWeaver Find information about SAP NetWeaver Business Warehouse at the Service Marketplace -> Business Warehouse, for
Business example information about Performance Tuning.
Warehouse
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 52 of 59
Business Planning The general idea is to define user groups which are determined by the number and size of data records they work with
and IP Planning and the types of planning functions they execute. Additionally, you can define elements (users) for planning sequences
Sequences (BPS or IP). Thereto, each planning function is considered one planning step. If you are not sure exactly how many data
Planning 1, are involved, you can take the proposed values, which are based on internal measurements and customer feedback.
Planning 2,
Specifics for User Groups Business Planning and IP Planning Sequences
Planning 3
Users
Estimate the highest number of active users per hour. Opposed to other sizing approaches in the Quick Sizer you
can arbitrarily include users in a specific group. Normally the user groups reflect the fact that you have power,
medium and occasional users (example at "Planning steps per user").
Example
In our example we have an average of 2,800 ( = (3 * 5,000 + 3 * 600) / 6) records per planning step.
Note
The term planning step is often understood from a business view, where it means a total run of a planning
area. Here, we take a functional perspective.
The memory requirement and CPU consumption is estimated on the basis of this data. To determine
memory requirements, we assume that there is an average data record length of 1KB.
Example
As mentioned above the planning functions work through different sets of data. The maximum number is 5,000
per hour and user.
Example
Take the example mentioned above. If the user doesn't leave the transaction, he holds 6,800 (5,000 + 600 + 600
+ 600) records in memory. Please keep in mind, that the set of data is the sum of records read and records
created
Comment
Editing/creating data records is achieved by planning functions or manual planning. We do not differentiate
between these two types for sizing, as both of them are used to manipulate data records.
We only size "User Groups Business Planning". NetWeaver BW server must be sized separately. However, the
sizing result includes the part of NetWeaver BW that is used to deliver the transaction data to "User Groups
Business Planning". For sizing the load generated on the NetWeaver BW system by "User Groups Business
Planning" we assume that 30% of all executed planning steps access NetWeaver BW. For the remaining 70% of
the planning steps we assume that they manipulate data records which have already been read by NetWeaver BW.
User Groups: Find information for the columns of this table below:
Reporting & BW Users (column "BW users") - Definition
Analysis In NetWeaver BW, we distinguish roughly between user types according to their frequency of activity and the
BW-INFO, reporting they will normally do.
BW-BUSIN.,
BW EXPERT Active User Type Navigation Steps per Hour This user will
predominantly ...
Information Consumer 1 ... view predefined and static
reports
Business User 11 ... navigate within reports, do
slicing and dicing, but usually hit
aggregates
BW Expert 33 and more ... run ad-hoc queries with a
high probability of full table
scans
A navigation step includes drilling down in the reports and corresponds to nine dialog steps in the SD
benchmark. If you don't know the user distribution, a typical ratio in the NetWeaver BW environment is
71% : 26% : 3% (Information Consumer : Business User : BW Expert).
Comment
The system automatically calculates the Java parts which are shown at the result level.
If BW Java is not used, you should add 5 % to the SAPS of the application server.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 53 of 59
Report Viewing, OLAP Analysis, and Data Exploration (columns "Report.", "OLAP", and "Explor.") -
Definition
Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an
InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you
like for each InfoProvider.
For sizing purposes we distinguish between three query types which are defined by the load they create in the
system.
Report Viewing: Predefined, static, reports using optimal aggregates
OLAP Analysis: Slicing and dicing, navigating in reports, using various aggregates
Data Exploration: Data mining, that is ad-hoc reports with unpredictable navigation paths, access of
detail data, full table scans
Any user can do any type of query. However, experience shows a certain activity pattern, as you can see in
the table below.
Web JAVA Reporting / Integrated Planning (columns "Web" and "IP") - Definition
In NetWeaver BW, reporting can be done either through the Excel based BEx Analyzer or through a Web browser
which receives HTML documents from a JAVA engine. If you use Web Reporting, you need to check the flag "Web"
and enter the corresponding number of users. If you use both, Web based Reporting and BEx Analyzer, you have
to enter the respective user numbers for both groups in individual lines of the QuickSizer. To create more lines in
table 2, mark the lines for the required user categories, select the number of copies and click on "Insert".
Another property of queries which has an impact on sizing is their input capability. Usually, queries used for
Integrated Planning are ready for input. If a query can accept input, then you need to check the flag "IP". Like in
the case above, you have to create separate lines in table 2 for users who use input queries and for those who
don't.
InfoCubes Definition
INFOCUBE The central objects upon which reports and analyses in NetWeaver BW are based, are called InfoCubes. An InfoCube
IC-APO describes (from a reporting point of view) a self-contained dataset, for example, of a business-orientated area.
IC-CO
An InfoCube has a particular type:
IC-CRM
IC-FI BasicCube which is a collection of relational tables arranged according to the star schema: A large fact table in the
IC-HR center, surrounded by several dimension tables.
IC-MM MultiCube which is based on the basic cube. It combines data from several BasicCubes/RemoteCubes, and brings it
IC-PP together into one context. The MultiCube itself does not contain any data; its data comes exclusively from the
IC-PS BasicCubes it is based on.
IC-SD RemoteCube to carry out reporting using data in external systems without having to physically store transaction
IC-SEM data in NetWeaver BW.
Only BasicCubes physically contain data on the database. MultiCubes and RemoteCubes simply display logical views of a
dataset. The InfoCube type is not important, as far as reporting is concerned. A query definition always refers to one
InfoCube. The difference between the InfoCube types becomes important at the point when you select data for the
query.
InfoCube types: From the list below you can choose additional InfoCubes, just take the information and fill it in the
questionnaire.
Long Text Short Name Cube name Dimensions Key Figures Length
Aerospace & Defense A&D 0AD_C01 6 2 94
Apparel and Footwear AFS 0AFMM_C01 8 48 896
Automotive 0AUPPC_3 12 11 307
Business Planning and Simulation 0SEM_C09 5 14 288
Category Management 0CM_C07 7 34 648
Consumer Products Industry CP 0CP_PURC1 8 52 964
Distribution Channel-Specific A 0CRM_CTI2 3 16 302
E-Analytics 0WEB_C01 12 5 205
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 54 of 59
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 55 of 59
WO (write optimized)
Flag, if DataStore Object is write-optimized.
Initial load
Enter the number of records initially loaded into the cube
Period. Upld (Periodic upload)
Enter the number of records loaded during the periodic upload process
Period
Enter the total number of uploads which will be kept in the InfoCube
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 56 of 59
parallel).
Back to Top
Application Server
Printed Definition
Documents Data storage medium containing information of a specific type.
BC-PRINT,
Specifics for the sizing element BC-PRINT
BC-USER
Enter the number of printed pages.
Comment
We assume that a page is always completely filled in and that the document is always completely printed. This considers
SAP script printing. Other print services such as Adobe print forms may require additional load. For more information
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 57 of 59
Back to Top
Note
Enter the number of searches per time period.
Comments
For sizing TREX we currently consider only the search function on document data (HTML; XML; DOC; TXT; RTF,
and so on).
For Embedded Search, Enterprise Search, and other business search scenarios, follow the link provided in SAP
note 1266024 ‘Sizing TREX 7.1 for Embedded Search’.
Note that there is another acceleration engine available within the SAP NetWeaver BW: the BW accelerator. For
sizing this engine use the column ‘BWA’ within the SAP NetWeaver BW questionnaire.
Back to Top
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 58 of 59
Flag, if XXL systems are monitored in Solution Manager (> 50,000 named users).
Months (Mon.):
The number of months during which the technical monitoring data will be kept in the Business
Warehouse (BW) of Solution Manager. This parameter impacts directly the BW storage.
Note: If the number of systems is big or if one of the following columns is flagged
Definition
Solution Manager This represents the Business Process Monitoring scenario of Solution Manager. This scenario collects performance KPIs
Business Process for specific Business Processes.
Monitoring
Specifics for sizing element BP-MON
BP-MON
Business processes (BP)
This represents the number of Business Processes that will be described in the Business Blueprint or that will be
selected for Business Process Monitoring. This influences the necessary DB storage for Solution Manager.
Alerts:
Number of alerts produced per connected host.
Servers:
Number of hosts per system.
Systems:
Number of manager systems included in BP Monitoring scenario.
Months (Mon.):
The number of months that the service desk objects (incidents and so on) will be kept in the Database.
Definition
Solution Manager This section describes the usage of the Service Desk included in Solution Manager and is complementary to the SERV-
Service Desk DES-U entry. It describes how many users will be using the service desk for their daily work (entering incidents or
SERV-DESK problems for instance).
Specifics for sizing element SERV-DESK
You can enter several lines representing different types of users (Customer Interaction Center, or development support
for instance). By default there are two lines: one for the average usage and the other one for the peak usage. For each
line you can specify the following parameters:
Objects:
Represent the number of tickets (incidents, problems, messages…) that will be created during the specified time
period.
Months (Mon.)
The number of months that the service desk objects (incidents and so on) will be kept in the Database.
Back to Top
Expert Functions
Status "Final"
Final projects cannot be modified anymore.
Status "Inactive" You can use this function for projects that are not required anymore.
Inactive projects are not listed in your project list, if you search for all your projects (using your customer number and a
wildcard for the project name). Also, you cannot change the project or use it as original for a create-with-reference
procedure.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012
SAP Quick Sizer Help Page 59 of 59
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries,
System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for
any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains
only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at
any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information,
text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or
implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result
from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access
through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty
whatsoever relating to third-party Web pages.
https://websmp205.sap-ag.de/~sapidb/011000358700000519272005e 16/03/2012