Professional Documents
Culture Documents
Table of Content
Industry Solutions
SAP for Banking
Analytical Banking
Core Banking
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 2 of 76
Insurance
Retail
Utilities
NetWeaver
Portal
Business Intelligence
Process Integration
Application Server
NetWeaver Standalone Engines
Expert Functions
The sizing elements from the questionnaires are written in italics.
In former CRM releases, the IPC was a separate component which was also installed separately.
Activity Definition
Management Within Activity Management, your employees can:
ACT-USER Create business activities to document any interaction they have with customers
CRM-ACT Create tasks to manage their own workload
Manage their work in the Application Workplace
View appointments and activities in the calendar
Access the Business Workplace for using workflow items
The two main elements in Activity Management are the application workplace and the calendar. Each provides a different
view of your workload and you can switch between them.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 3 of 76
The calendar displays all your appointments in a daily, weekly, or monthly overview. The inbox, on the other hand,
provides you with a personal workplace or file manager, where all your activities, whether they have been given fixed
appointments or not, are clearly sorted into different folders.
Activities often are some kind of follow-on actions, for example a follow-up call after an initial sales conversation with a
customer.
Changes to an activity are regular. Make sure you include this information in the sizing.
Comments
Users are very rarely entered in this component because they are usually more involved in order processing or
opportunity processing. Therefore, you should attribute users to these components rather than to Activity
Management.
Note that attached documents (typically PC type documents such as text files, presentations, or documents in print
format) which are uploaded into CRM are not considered in this approach.
Opportunity Definition
Management The Opportunity describes the sales prospects, their requested products and services, the sales prospect’s budget, the
OPP-USER potential sales volume and an estimated sales probability. This information becomes concrete in the course of the sales
CRM-OPP cycle, and can be displayed and evaluated in the system.
Opportunity Management provides the framework for presenting sales projects from the very start, and tracking their
progress. In this way, it provides the basis for an analysis and optimization of your Enterprise.
Users in Opportunity Management can use the following functions:
Presentation of the Sales Cycle
Reason for Status
Working With Products
Management of Attachments
Transferring Data for Sales Volume Forecast
Classification of Opportunities
Texts in Opportunities
Opportunities - Fast Change
Comment
Make sure you (determine and) enter the number of times the opportunities are displayed or changed (in percent).
This is important for the sizing because the typical lifecycle of an opportunity includes several changes (for example
the status or phase) as well as several display actions (for example, to check the ongoing status or the final
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 4 of 76
success).
Note that attached documents (typically PC type documents such as text files, presentations, or documents in print
format) which are uploaded into CRM are not considered in this approach.
Service Definition
Transactions You can use the component Service transaction to represent business processes in the service area in your company.
SRV-USER Service transactions can be entered in the following ways.
CRM-SRV By an employee in the CRM System
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 5 of 76
Customer Definition
Interaction Center The Customer Interaction Center (CIC) is a key technology of Customer Relationship Management with the SAP Business
IC-USER Suite. It is designed as a multi-channel, blended business process interaction center to empower call centers to provide
the highest level of customer service. It provides robust technology for contact center operations. It tightly integrates a
highly customizable and full-featured front office with your back-office as well as your entire range of customer-centric
processes. The Customer Interaction Center is the common state-of-the-art technology for any business transactions via
phone, email, letter or face to face. It’s used in the following CRM Business Scenarios: Service Interaction Center,
Telesales and Telemarketing. Highlights of CIC include:
Processing inbound and outbound telephone calls with customers and other business partners using Computer
Telephony Integration (CTI) technology as middleware.
An Email Office system for processing incoming and outgoing emails. Also included are Planned Activities for the
agent to execute.
A comprehensive Interaction History log to provide one view of a customer. This enables agents to view planned
and historical activities along with sales and service orders.
Comment
For user-based sizing we assume that the CIC creates additional load. Basic load is created by the business transactions
called through CIC, such as Opportunity Management, Activity Management, Customer Order, and Service Transaction.
Therefore we recommend you enter a CIC user in the line for CIC as well as in the line of the respective business
transaction.
To reflect CIC orders in the Quick Sizer use the line for customer orders and add the number of calls.
Example
Altogether, 100,000 customer orders are being created, 50,000 of them through CIC. To reflect this, you enter 100,000
under customer orders and 50,000 under calls.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 6 of 76
Note
Here you can also enter users who use Handheld Sales and Handheld Service.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 7 of 76
Back to Top
Financials
Financials Definition
SAP ERP Financials comprises
Financial Supply Chain Management (FSCM)
Financial Accounting (FA)
Management Accounting (MA)
Corporate Governance (CG)
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 8 of 76
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 Intelligence with its Strategic Enterprise Management comprises the functions that were formerly accounted for
by Enterprise Controlling.(see Business Intelligence)
Example
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)
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 9 of 76
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 planning,
CO-PA-SLS 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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 10 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 11 of 76
in proportion to the material withdrawals and crediting the material cost centers with the same amounts. Also used to
allocate sales and administration overhead.
Order settlement is the complete or partial crediting of an order. The costs which have accrued to an order are debited to
one or several allocations.
Overhead rates: Enter the number of orders, cost centers and projects, that receive an overhead rate per period.
Order settlement: Enter the number of orders (from PP, PM, and CO) which are settled per period. We assume that your
orders are settled without using the original cost element.
Back to Top
Personnel Definition
Administration & Personnel Administration and Payroll Accounting from the Human Resource (HR) component includes the following areas:
Payroll Personnel Administration, Benefits, Compensation Management, Recruitment, Personnel Time Management, Incentive
Accounting Wages, 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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 12 of 76
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
Logistics Execution
Logistics Definition
Execution Logistics Execution contains Warehouse Management as well as Inbound and Outbound Logistics
LE-USER
Back to Top
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 13 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 14 of 76
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 15 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 16 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 17 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 18 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 19 of 76
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
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 20 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 21 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 22 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 23 of 76
Back to Top
Corporate Services
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 24 of 76
Line items are the average number of line items per receipt, for example travel costs, meals, or accommodations.
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 BI 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 BI 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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 25 of 76
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 be
Timeseries 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 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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 26 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 27 of 76
is generated at higher level, then only a percentage of the characteristic combinations is used to generate a plan.
So, the amount of CPU processing time is reduced in direct linear proportion to the percentage of characteristic
combinations used to generate a forecast. The totals can be disaggregated to lower levels in the planning book, or
summed up to a higher level in the hierarchy. For example, if a planner generates forecasted demand for a region,
then the system does not plan forecasts for all of the different sales channels, product families, brands, products,
and customers in that region. Those values are calculated in the planning book when displaying those characteristic
combinations, and are based on the results of the forecast at the region.
Periods for planning run is a count of time buckets used in planning. CPU process time increases as the time
bucket count grows.
The duration of planning run time frame is determined by a Company's planning and operating requirements.
The shorter the required time frame, the more CPU processing power is required to complete the planning run. The
impact required for CPU processing power versus process time is in reverse linear proportion.
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.
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 28 of 76
APO - Master Data Specifics for Master Data - SAP liveCache Memory
- SAP liveCache
The number of product-location 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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 29 of 76
The average number of alternative resources per activity can be one or more, depending on the number of
resources that can perform the same activity used to produce a product. (A resource can be a production line, a
work center or any other manufacturing facility.)
Determine the average number of parallel capacity requirements per operation step (activity). This can
be one or more constraining resource in an operation. For example, this can be a work center and a specific tool or
person, all required performing a specific operation step.
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 product-location
SAP liveCache
combinations, with a forecast that is released from Demand Planning to Supply Network Planning. Each product-
Memory
location 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 APO
TRANSFER 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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 30 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 31 of 76
ATP-SIMPLE company can provide the requested product at the requested time in the quantity requested by the customer.
The simple ATP check is carried out based on the ATP quantity (Available-To-Promise). The ATP quantity is
calculated from stock, planned receipts (production orders, purchase orders, planned orders and so on), and
planned requirements (sales orders, deliveries, reservations and so on).
Back to Top
Sizing Elements We size the disk and the CPU requirements in order to process and to store the messages.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 32 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 33 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 34 of 76
In the Quick Sizer we distinguish between inbound and outbound delivery processes.
Back to Top
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 35 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 36 of 76
Example
During the peak hour the following process steps are executed in the system:
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 37 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 38 of 76
Warehouse Task
OEWM-PACK
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 39 of 76
Back to Top
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 40 of 76
SRM) more effectively with your vendor pool, and thus to gain long-term benefits from all your vendor relationships.
With SAP SRM you can examine and forecast purchasing behavior, shorten procurement cycles, and work with your
partners in real time. This allows you to develop long-term relationships with all those vendors that have proved
themselves to be reliable partners.
The efficient processes in SAP SRM enable you to cut down your procurement expenses and to work more intensively with
more vendors than ever before.
Contract Description
Management The Contract Management business scenario allows you to create, process, and monitor purchasing contracts and global
CTRCT-USER, outline agreements (GOA). It also provides a means to renegotiate existing contracts directly with the vendor or by
SRM-CNTRCT creating a bid invitation. A contract can be automatically assigned as a source of supply or displayed as a possible
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 41 of 76
selection.
A strategic purchaser creates a contract or a GOA whenever a long-term relationship is anticipated and the vendor can be
considered as a source of supply. Contract management enables purchasers from various parts of the company at different
locations to take advantage of the terms of globally-negotiated contracts for specific product categories.
You can provide users with specific levels of authorization to contracts and GOAs, and also categorize these documents as
confidential. You can distribute a GOA to the release-authorized purchasing organizations and these organizations can use
the contracts and scheduling agreements created from the distributed GOA. You can use hierarchies to organize, structure,
display, and search for your contracts.
If you use SAP Business Intelligence (SAP BI), you can view various consolidated reports of contract management. For
example, you can view the aggregated value released against all the contracts in a contract hierarchy.
Typical tasks for the Contract Management business scenario include:
A strategic purchaser negotiates a long-term contract with a vendor to deliver goods of a specific commodity.
A strategic purchaser monitors contract compliance.
An operational purchaser searches for applicable contracts within a central contract database and puts contracts into
effect.
The Quick Sizer scenario includes the business objects Purchaser Order and Contract.
Plan-Driven Definition
Procurement Plan-Driven Procurement automates and streamlines ordering processes for regularly needed core materials. You can use
PLAN-USER, this business scenario to procure requirements for materials that have been generated in systems other than SAP Supplier
SRM-PLAN Relationship Management (external systems). By integrating the SRM System with planning, design, and maintenance
systems, you can accelerate your procurement and integrate the operational procurement with your Supply Chain
Management solution. The business scenario supports third-party order processing, a special kind of procurement. Here
the product goes directly from the vendor to the customer of the purchasing company. The purchase order to the vendor
contains the necessary information for this.
You can set up the business scenario in such a way as to link one or more Materials Management systems (SAP-MM) with
Materials Requirements Planning (SAP-PP-MRP) to one or more vendor systems (SAP Supplier Self-Services).
You can continue to plan requirements in SAP Advanced Planner and Optimizer (SAP APO).
Examples of tasks for Plan-Driven Procurement include:
A manufacturing company with many disparate planning systems consolidates all procurement (direct and indirect)
in one e-procurement hub.
A company performing planned and unplanned maintenance centralizes procurement activities in a single
application.
The Quick Sizer scenario includes the business objects Shopping Cart, Purchaser Order, Purchase Order Confirmation,
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 42 of 76
Self-Service Definition
When using Self-Service (Indirect) Classic Procurement solution, employees use a self-service application to select items
Classic
such as office material, for example, from a catalog and add them to a shopping cart in the EBP system. When the
Procurement
shopping process has finished, the shopping cart is transferred to an SAP R/3 Material Management (SAP MM) backend
CLASSIC-U,
system where it is further processed in the form of a purchase order.
CLASSIC
Note
Note that you must account for the orders processed in MM and possible follow-on documents separately so that the
backend system is sized properly. The backend systems being in these cases both MM and FI backend systems.
Self-Service Definition
Both scenarios, Extended Classic Procurement and Standalone Procurement, can be sized with the same methodology.
Extended Classic
Procurement & Extended Classic Procurement
Standalone
Whereas in the Classic Procurement scenario, all materials management takes place in the backend system, with this
Procurement
scenario the shopping cart and purchase order are created locally. If the data in the shopping cart is insufficient to
EXT-USER,
generate a complete purchase order, the data is supplemented manually within Enterprise Buyer before being transferred
EXTENDED
to the backend system. The purchase order in Enterprise Buyer is the leading purchase order. The version that is
transferred to the backend is not an exact copy, rather it is a much leaner version of the leading purchase order, a read-
only copy. This copy supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in
the backend system. Confirmations and invoices can also be pre-entered in Enterprise Buyer.
Standalone Procurement
This scenario handles the entire procurement process in Enterprise Buyer: The shopping cart and follow-on documents are
created locally. You have no materials management in your ERP system and are using the Materials Management functions
in the Enterprise Buyer system for all procurement. Accounting processes (incl. FI, CO and AM) must still be handled by a
backend system. All validations and approvals are handled directly within Enterprise Buyer rather than in a backend
system. Migration tools are provided to bring materials management data from SAP backend systems into the application
product master.
Note
If you want to size both scenarios, just add the figures or, if they differ to a great extent, create a new sizing
project
Note that you must account for any follow-on documents or objects processed in the backend system separately.
The backend systems being in these cases both MM and FI backend systems.
The Standalone Scenario can be deployed using single or multiple FI backend systems. Or alternatively, in the case
of a marketplace scenario no FI backend system is necessary.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 43 of 76
Service Definition
Procurement You can use this business scenario to cover the entire service procurement process. Before ordering external staff or
SERVC-USER, services, you can send a request to one or more suppliers for detailed information on a specific service or the availability of
SRM-SERVIC individual service agents, for example. After receiving the suppliers’ responses and accepting one of these bids, the
corresponding purchase order is automatically created. Next, time and expenses have to be entered into the system and,
finally, the invoice is created.
You can integrate your suppliers into the procurement process by connecting a supplier system like Supplier Self-Services
to your procurement system. In this way, the service agents can enter services performed and create invoices for these
services. You have to approve all documents created by your suppliers and you always retain a complete overview of all
business processes.
The Quick Sizer scenario includes the business objects Shopping Cart, Purchaser Order, Purchase Order Confirmation,
Confirmation and Invoice.
Note:
If you also want to size sub-items, simply add them to the number of items and insert this number in column "items".
Back to Top
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 44 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 45 of 76
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 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)
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 46 of 76
GTS-RI-BOM, of Sizing it is assumed that one preference agreement is set up for preference processing.
GTS-RI-MM,
SAP GTS supports preference processing issues in the following main areas:
GTS-RI-SO,
GTS-RI-INV, Master data transferring - Bills of Material, Procurement Indicator and Price transfers.
GTS-RI-SOL, Transactional data from feeder system- Purchase Orders, Sales Orders, Invoices.
GTS-RI-AGG, BOM Preference Determination
GTS-RI-PRD, Long Term Vendor Declarations (LTVDs) processes - Solicitation, aggregation, issuing.
GTS-RI-ISS
The following are the technical elements used for GTS Risk Management sizing and their short text explanation:
GTS-RI-BOM – Bill of material transfer
For transferring Bills of Materials (BOMs). Here what you have to enter is the sum of the number of items (including
the top material itself of all the BOMs to be transferred. That means that for a one level BOM with five
subcomponents the number to be entered is six (five subcomponents + one top material).
GTS-RI-MM – Worklist for requesting long-term vendor declarations based on MM Purchase Orders and MM Goods
Receipts
For MM Documents (Purchase Orders and Goods Receipts) being sent to GTS. In case the Purchase Orders are also
to be screened with SAP GTS Compliance, you should make a separate entry in GTS-SLS.
GTS-RI-SO – Preference status determination in sales process (SD SO)
For Sales Orders Documents being sent to GTS. In case the Sales Orders are also to be screened with SAP GTS
Compliance, you should make a separate entry in GTS-SLS.
GTS-RI-INV – Worklist for issuing long-term vendor declarations based on SD Invoices
For Invoice Documents being sent to GTS. In case the Invoice Documents are also to be processed within SAP GTS
Customs, you should make a separate entry in GTS-CUMA.
GTS-RI-SOL – Request of long-term vendor declaration
For the solicitation of long-term vendor declarations.
GTS-RI-AGG – Aggregation of long-term vendor declarations
For the preference status aggregation into the GTS product master based on long-term vendor declarations.
GTS-RI-PRD – Preference determination of bills of material
For the preference determination of in house production according to Bills of Materials (BOMs).
GTS-RI-ISS – Issuing long-term vendor declarations
For issuing and revocation of long-term vendor declarations.
Back to Top
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 47 of 76
Solution SAP Basel II provides a standard platform for accurate calculations of credit risk and capital adequacy involving all types of
assets and calculation methods. The application's flexible structure and open reporting functions help banks improve
internal risk management and meet external risk-reporting requirements. Part of the SAP for Banking analytical solutions,
SAP Basel II gives banks broad, long-term support for regulatory compliance by integrating information for all finance and
risk-related business processes.
The most prominent business processes of this solution handle mass data. The main process in the SAP Basel II solution is
divided into the following steps:
1st step: Upload of the financial data from the front office systems to the source data layer (SDL; can be done
daily)
2nd step: Execution of the pre-run or general method (optional; no sizing available)
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 BI (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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 48 of 76
Position
Enter the number of changed positions
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 49 of 76
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 50 of 76
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 51 of 76
Back to Top
Insurance
SAP Financial Services - Collection & Disbursement
Subledger Definition
Document & A subledger document consists of one header with 1...n Business Partner items (e.g. receivables, payables) and 1..m
Payment General Ledger items. A payment document is a subledger document which represents a payment from/to the customer.
Document In the most common case the payment documents are directly cleared against open items and point to the Business
SUBLEDGER Partner item of the cleared item. Therefore payment documents normally don't create physical entries for their Business
Partner items in the database.
Enter the total number of subledger documents to be created per year in the field "Postings", enter the total number of
payment documents to be created per year in the field "Payments". Specify additionally the average number of Business
Partner items per posting document and the average number of General Ledger items per posting and payment document.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 52 of 76
Account Note: We assume that the invoices and account statements are printed.
Statement
ACC-STAT
Dunning Definition
DUNN The number of dunning notices that are produced. Note: We assume that the notices are printed. The calculation includes
the dunning proposal run, the dunning activity run, and the print run for the dunning procedures.
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 53 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 54 of 76
Back to Top
Retail
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 55 of 76
Please enter the number of objects and sub-items and the number of months that this data stay on the database.
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".
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 56 of 76
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.
Back to Top
Utilities
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 57 of 76
For explanation see ‘Posting relevant line items on consumption bill’. However, the same figure of a partial bill is
asked for there. Usually, it is smaller then the one of the real, final bill. If no partial bills or budget billing amounts
are made, the correct answer here is 0.
Example
Enter “2” to reflect basic fee deposits and deposits on utiltiy services.
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 58 of 76
same collection/payment agreements apply. Contract accounts are managed on an open item basis within contract
accounts receivable/payable. In the case of utility companies, a contract is assigned to one contract account only.
However, and depending on the contract account category, several contracts can be assigned to one contract
account. The relation between business partners and contract accounts is 1:n but in most cases the relationship is
almost 1:1. Nevertheless, this rule of thumb should only be used if there is no figures about “contract accounts”
available.
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 59 of 76
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.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 60 of 76
Sizing)
MOVE IN
MOVE OUT
Back to Top
Portal
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 61 of 76
In an Intranet scenario, the Portal is used as an Enterprise Information Portal. Users typically read news, access
documents, and occasionally launch transactions in other business systems. Enter the number of users. You can
modify the default suggestions at your discretion. The Intranet scenario is an example of a medium-weight Portal
application.
NetWeaver Portal for People-Centric CRM (PCC) scenario
This scenario is based on an example from SAP CRM with the end user role Sales Representative. An EP-PCC user
typically navigates in the Portal to perform actions such as
Launching BSP-based CRM transactions (1 URL iView, 0 Java iView)
Displaying overview information from CRM and NetWeaver BI backend system (Java iViews).
A NetWeaver BI (BEx) iView that does not use the Portal application cache is a URL iView. If it does use the Portal
application cache, it creates a load similar to a Java iView. The PCC scenario is an example of a medium-weight
Portal application.
NetWeaver Portal for custom-defined scenario
You should use this scenario if you have more detailed information available on the Portal usage by specifying not
only the users and the think time, but also the different numbers and types of iViews in different custom application
scenarios. To reflect different scenarios, use the insert button to create any number of scenarios.
Specifics for Active Users - NetWeaver Portal
Number of concurrently active users
To determine the high load phase, enter the highest possible number of users working simultaneously in the
system.
Average think time in seconds
This is the average elapsed time between two successive clicks of a user to the Portal Server, that is, between two
navigation steps. Note that the think time is often higher than most customers assume, as end users type, read,
use other applications, take a phone call and so on. As this field has a strong influence on the sizing result, you
should consider the figures carefully.
Number of Java iViews on an average Portal page
Specify the number of Java iViews of a typical Portal page of a specific scenario. A Java iView retrieves business
content from back-end systems via JCo/RFC and renders the unformated business content in HTML.
Number of URL iViews on an average Portal page
Specify the number of URL iViews of a typical Portal page of a specific scenario. For a URL iView, the Portal
generates the URL and sends it to the browser. The browser then sends the URL to the back-end system and
retrieves the HTML content from there.
Percentage of requests using Knowledge Management & Collaboration (% KMC)
Enter how many clicks out of 100 access KMC content.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 62 of 76
Enter the highest number of users (2,000, for example) who log on to the Portal within one hour (e.g. 8 am - 9 am). If the
Active Users -
users will log on to the Portal over a period of two hours (e.g. 8 am - 10 am), you then need to size only half of the users
NetWeaver Portal
(e.g. 1,000 logons per hour).
Logon
NW-EP-LOG
Back to Top
Business Intelligence
SAP NetWeaver Find information about SAP NetWeaver Business Intelligence at the Service Marketplace -> Business Intelligence, for
Business example information about Performance Tuning.
Intelligence
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 63 of 76
sequences are used, these cannot be calculated as a planning step, instead the number of planning functions
contained must be entered. The average number of data records manipulated by one single planning step has an
impact on the CPU time consumed by a 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 BI server must be sized separately. However, the sizing
result includes the part of NetWeaver BI that is used to deliver the transaction data to "User Groups Business
Planning". For sizing the load generated on the NetWeaver BI system by "User Groups Business Planning" we
assume that 30% of all executed planning steps access NetWeaver BI. For the remaining 70% of the planning steps
we assume that they manipulate data records which have already been read by NetWeaver BI.
BI Users Definition
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 64 of 76
BI-INFO, In NetWeaver BI, we distinguish roughly between user types according to their frequency of activity and the reporting they
BI-BUSIN., will normally do.
BI 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
BI 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 BI environment is 71% : 26% : 3% (Information
Consumer : Business User : BI Expert).
Comment
The system automatically calculates the Java parts which are shown at the result level.
If BI Java is not used, you should add 5 % to the SAPS of the application server.
Definition
User Groups
Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoProvider. A
Reporting &
query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
Analysis
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.
Query Report Viewing OLAP Analysis Data Exploration Total Percent
Type
Information 80% 20% 0% 100%
Consumer
Business 50% 50% 0% 100%
User
BI Expert 0% 0% 100% 100%
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 65 of 76
InfoCube Definition
INFOCUBE The central objects upon which reports and analyses in NetWeaver BI 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-HCM 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 BI.
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
External Market Data 0DB_MC01 9 5 175
Financials Management & Control 0FITV_C02 12 13 341
Healthcare 0HC_C01 9 16 362
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 66 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 67 of 76
Specify the total number of uploads which will be kept in the InfoCube. Example: if you want to keep weekly data
for 5 years, you should enter 260 (52*5)
Short text
If you have several different InfoCubes of the same type, use short text to attribute names in order to identify them
more easily.
Back to Top
Process Integration
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 68 of 76
Advanced Sizing requires advanced knowledge about the PI architecture and the used scenarios.
You can combine both approaches to obtain sizing figures for generic and detailed scenarios.
Note
The results from all sizing tables (initial sizing, advanced Integration Server sizing, and advanced non-central Adapter
Engine sizing) are added up. Therefore, the same scenario should not be entered in more than one sizing table.
Basic sizing information needed for PI:
Message size
Average size for XML representation of messages of a scenario. If the size for XML representation is unknown, you
can use the following guidelines to estimate the XML size:
- For flat files, calculate a factor of 10 for conversion to XML (multiply flat file size by 10).
- For IDocs, you can use the following approach: In a sender or receiver system, use the IDoc test tool (transaction
WE19) to write a sample IDoc to a file using an XML File port (or a File port if an XML File port is not available);
then use the file size as XML message size.
Number of messages
Peak number of outbound messages to be processed in a given timeframe for a scenario. For the Integration
Server, only messages sent out from the Integration Server are counted; for a non-central Adapter Engine, all
processed messages must be counted. For peak load calculation it might be helpful to distribute processing over
time (e.g. by using batch functionality).
Processing mode
Synchronous or asynchronous processing mode determines how messages are handled in PI.
- Synchronous messaging means that a sender application has to wait until a message is delivered to a receiver
application, and that the receiver sends an immediate response like in a synchronous remote function call. This
applies to Quality of Service BestEffort.
- Asynchronous messaging means that a sender application sends a message to the Integration Server and receives
a technical OK that the message has been received; the sender does not wait for immediate response by the
receiver application. With this processing mode, the Integration Server needs to store data and deliver the message
later (asynchronously) to the receiver application. Asynchronous processing is standard in PI and applies to Quality
of Service ExactlyOnce and ExactlyOnceInOrder. If you use this mode in order processing (serialized), the
Integration Server cannot make use of parallel processing.
Business Process Management (optional)
Business Process Management (BPM) provides stateful message processing capabilities with PI. An integration
process is an executable cross-system process for the processing of messages, including process steps and
parameters relevant for process control. The status of an integration process is persisted on the Integration Server.
For sizing calculation, it is important to determine if messages of a scenario are handled by integration processes in
the Business Process Engine (BPE), the runtime component for process execution. Within the sizing procedure, BPM
usage is categorized in predefined BPM patterns (see process definitions in software component SAP_BASIS for
namespace http://sap.com/xi/XI/System/Patterns in the Integration Repository).
Disk sizing:
The Quick Sizer result includes an offset for the initial system setup (installation) and additional disk requirements per day
(calculated by scenario timeframes) driven by temporary storage of messages. The needed database size then depends on
the residence period for the data. In general, processed messages should be archived and/or deleted on a daily basis.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 69 of 76
Asynchronous messages are calculated to use two persistence steps (message is persisted twice). If data is persisted more
than twice by activating logging, additional disk space will be required.
Memory sizing:
Memory sizing is based on the number of required CPU resources (SAPS value). Memory requirements raise as additional
Application Server instances (ABAP or Java) need to be installed. Additionally, individual memory requirements by single
messages due to their message size are considered. As result, the maximum for both memory requirements is calculated.
The number of parallel messages to be processed is derived from the given throughput value. Depending on the type of
adapter or mapping, at least six to eight times the message size is required as memory for processing. Therefore,
available OS heap limits must be taken into consideration. Use of 64-bit environments is strongly recommended. For more
information, see SAP Service Marketplace at http://service.sap.com/installnw70 → Operations → Process Integration →
Tuning Guide.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 70 of 76
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 71 of 76
- Multicast: Sends one message to a receiver list and receives response messages.
- Serialize: Serializes a number of messages.
- Split: Splits one message into several messages.
- SyncAsync: Synchronous to asynchronous bridge.
- Other: Generic BPM scenario based on message forwarding (receive to send ratio 1:1, receive and send one
message); includes additional process steps.
BPM Ratio
The BPM ratio is used to adapt or configure specific BPM patterns (if no value is entered, an internal default is
used):
- Collect: Defines the average collect factor; specify 10 for a 10:1 merge (merge 10 messages into 1 message).
- Multicast: Defines the average number of receivers; specify 5 for an average of 5 receivers per process execution.
- Serialize: Defines the average number of serialized messages; specify 3 for serialization of 3 messages per
process execution.
- Split: Defines the average split factor; specify 10 for a 1:10 split (split 1 message into 10 messages).
- SyncAsync: Not relevant for this pattern.
- Other: Defines the average number of additional process steps per process execution.
Inbound Adapter
Inbound adapters receive requests from a sender application and are therefore also called sender adapters.
Available adapter types are:
- IDoc: Standard IDoc adapter.
- XI (Proxy): Standard XI message protocol (used within proxy communication) based on SOAP/HTTP.
- HTTP (Plain): Adapter for message exchange using the plain HTTP protocol.
- J2EE: J2EE-based adapters (File, FTP, JDBC, JMS, RFC, SOAP, Mail).
- J2EE w/conversion: J2EE-based adapters including content conversion (for example, conversion of flat files to
XML).
- Industry Speak: B2B adapters (RNIF, CIDX).
- 3rdParty: Certified 3rd party adapters from partners.
Outbound Adapter
Outbound adapters send requests to a receiver application and are therefore also called receiver adapters.
The available adapter types are the same as for the inbound adapters.
TREX
The Search and Classification engine (TREX) provides various software applications with intelligent search, retrieval,
and classification functions. With XI, TREX can be used for Payload-based Monitoring. Cost calculation for monitoring
on one component is included.
Adapters are divided into different categories referring to the adapter type. Several adapters are grouped together in
subcategories as the sizing estimate is quite comparable (for example, J2EE-based adapters like File, FTP, JDBC).
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 72 of 76
PI-ADAPTER Adapter Engine has an own database (based on AS Java). All J2EE-based adapters can be used with this type of Adapter
Engine.
Comment
The sizing information needed for advanced sizing of a non-central Adapter Engine is the following:
Message size, Number of messages, Processing mode
Acknowledgements
Acknowledgements enable the confirmation that an asynchronous message has been received. Acknowledgements
must explicitly be requested by an application. Acknowledgements require that additional messages are transferred.
Adapter Type
- J2EE: J2EE-based adapters (File, FTP, JDBC, JMS, RFC, SOAP, Mail).
- J2EE w/conversion: J2EE-based adapters including content conversion (for example, conversion of flat files to
XML).
- Industry Speak: B2B adapters (RNIF, CIDX).
- 3rdParty: Certified 3rd party adapters from partners.
TREX
The Search and Classification engine (TREX) provides various software applications with intelligent search, retrieval,
and classification functions. With XI, TREX can be used for Payload-based Monitoring. Cost calculation for monitoring
on one component is included.
Adapters are divided into different categories referring to the adapter type. Several adapters are grouped together in
subcategories as the sizing estimate is quite comparable (for example, J2EE-based adapters like File, FTP, JDBC). Only
adapters implemented in the J2EE Adapter Framework can be selected.
PI Sizing Example
Examples This section describes some sizing examples derived from customer projects.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 73 of 76
Back to Top
Application Server
Business Definition
Workplace The Business Workplace provides a standard working environment in which every SAP user can carry out their share of the
BWP business and communication processes in the enterprise. There, they receive all the work items that are assigned to them
in the course of SAP Business Workflow and process the documents that were sent to them from people or from SAP
applications.
This can include the following actions:
Processing work items
Receiving and sending mails
Administrating documents and work processes
Distributing and processing companywide and group internal information
Comment
- In line BWP enter the number of lines per mail in the field for sub components.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 74 of 76
- In the lines for the emails enter the number of recipients for external and internal mails in the field for sub components.
Back to Top
Note
Enter the number of searches per time period.
Comment
For sizing TREX we currently consider only the search function.
Back to Top
Expert Functions
Status "Final"
Final projects cannot be modified anymore.
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 75 of 76
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.
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
https://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007
SAP Quick Sizer Help Page 76 of 76
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://websmp202.sap-ag.de/~sapidb/011000358700000519272005E 10/30/2007