SAP ERP
| General remarks for Logistics | There are functions that are either not implemented in Quick Sizer or that have - dependent on the individual implementation - very different resource consumption.
In the following, some examples for functions that are out of scope of the Quick Sizer tool are listed:
Create purchase requisition
Create customer order (Expensive functions which are not reflected in the Quick Sizer)
Create delivery note
Post goods issue
Invoice
|
| Some workarounds for SD, LE, and MM | Challenges are how to do the implementation of big projects and critical business functions in order to balance the load and to ensure scalability which is the prerequisite for the validity of a sizing.
Find some examples for workarounds below:
Rescheduling
Post goods issue
Mass processing of invoices (VF04, VF06)
Printing
Invoice verification
Rush order
|
SAP ERP Financials
| Financials | Definition
SAP ERP Financials comprises
Financial Supply Chain Management includes functions such as Treasury and Risk Management, Cash and Liquidity Management (CLM), Credit Management, and Dispute Management. The dominating functions of Financial Accounting are General Ledger, Accounts Receivable and Payable, Fixed Asset Accounting, and Financial Statements. Amongst others, Management Accounting includes Profit Center Accounting, Project Accounting, Revenue and Cost Planning, and Transfer Pricing.
The Quick Sizer maps most of the sizings of FSCM and FA to FI, Management Accounting is predominatly reflected in CO. From a sizing perspective Corporate Governance plays a subordinate role.
| ||||||||||||||||||
| FI UserFI-USER | Definition 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.
NoteBusiness Warehouse with its Strategic Enterprise Management comprises the functions that were formerly accounted for by Enterprise Controlling.(see Business Warehouse)
| ||||||||||||||||||
| Controlling CO-USER CO | Definition of CO documents A proof of a cost accounting posting. This posting can be made both within (for example, distribution) and outside of (for example, primary cost posting in FI) CO.
Example
Line items: Because of double accounting, every document contains at least two line items. The number of line items in CO-OM and CO-OM-ABC (Activity-Based Costing) are posted to CO objects (such as orders, cost centers, and projects). Postings to statistical orders consist at least of three line items, because a statistical order contains booking, counter-booking and a separate display of the costs to enable descriptive reporting. Activity allocations add another line to the posting, because additionally the amount of services (non-monetary) are booked separately.
Example
| ||||||||||||||||||
| Comment If you use detailed planning, you should add line items created during planning.
| |||||||||||||||||||
| Profitability Analysis CO-PA-BIL CO-PA-FI CO-PA-SLS | |||||||||||||||||||
| Comment In our experience, the number of documents that you transfer to CO-PA from Sales and Distribution (SD) or Financial Accounting (FI) serves as a good indicator of the disk space and system load that CO-PA represents. Using this indicator simplifies the sizing process because the Quick Sizer no longer needs to take into account the contributions from planning, cost center assessment, the information system, realignments, or settlement. If your requirements in one of these areas are high (for example, a large volume of data needs to be processed by a large number of users during peak system load times), you should contact your hardware partner or SAP. To gain a deeper understanding of the factors that can influence sizing and performance, see the information contained in at service.sap.com/co-pa.
Transferred Objects: If you use Profitability Analysis, SD billing documents (SD-BIL) and FI documents are transferred to CO-PA automatically. The transfer of orders (SD-SLS), on the other hand, is optional. For objects, enter the number of documents transferred per year from the respective components to CO-PA. For sub objects, enter the average number of document items in each case. You can also use the above methods to display how external data is transferred to CO-PA.
| |||||||||||||||||||
| Profit Center Accounting Documents EC-PCA | Definition Number of documents that are posted to Profit Center Accounting (EC-PCA). For sizing we assume that the majority of postings are created in other components and then posted to EC-PCA. Enter the number of documents that are created in PCA with their respective lines items and the number of orders that have been posted by other components. | ||||||||||||||||||
| Business Accounting Documents FIN-BAC | Definition The proof of a business transaction. A distinction is made between original documents and data processing (DP) 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.
| ||||||||||||||||||
| AssessmentCO-OM | Definition 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 |
| Overhead Rates & Order SettlementCO-OM-RATE CO-OM-SETT | Definition Overhead rate refers to a rate at which overhead is allocated to direct costs to charge cost objects with the proportion of the overhead costs attributable to them. This can be a lump sum, percentage, or quantity-based rate.
An example of the use of overhead rates is to allocate overhead from material cost centers to orders by debiting the orders 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.
|
Contract Accounting
| Contract Accounting | Definition
Find more information on Contract Accounting within the document "Sizing Contract Accounting with the Quick Sizer" at the Service Marketplacewww.service.sap.com/quicksizing -> Quick Sizer documentation -> Experts.
The whole sizing is split into one mandatory and four optional blocks:
.
|
| BIT Upload (optional)BIT-UPL | DefinitionA billable item (BIT) is a line which tells about an event for which the business partner has to pay a certain amount. This can be a phone call, the purchase of a good at an online store, a package or letter send or a road toll. These records are loaded into the system and later, during the billing, they are grouped together according to certain grouping criteria.
The tables keeping the BITs on the database contain required fields and additional fields, depending on the scenario and usage. Many of these fields are provided by SAP, but the customer may add further fields. As the lengths of a record can have a big impact on the database, no fixed value can be used here and hence the length of a single record is requested. In case more than one BIT class is used, the sizing must be done for each BIT class separately. You need to know how many BITs of each class are to be expected every year. (Tip: keep the row lengths of a BIT as short as possible. These tables can easily be 30 % or 50% of the whole database size)
Specifics for this sizing element for CPU Sizing
Specifics for this sizing element for Disk Sizing
One line per BIT class is required as the row length is depends on the class.
|
| BIT Billing (optional)BIT-BILL | Definition
During the billing run billing documents are created by aggregating BITs. The aggregation is based on billing accounts and certain grouping criteria which cannot be specified more in detail as they are customer specific. The resulting billing documents consist of a header and a certain number of billing lines. This number is usually lower than the average number of BITs that is processed per billing account.
A phone company might usually have one line for each of the following services: landline calls, mobile calls, internet access and other services (such as the purchase of a new cellphone). Each BIT is sorted into one of the four buckets during the billing, so the average number cannot be higher than four. However, in this example the answer to this question is more likely to be three, as not many customers purchase a new cellphone every month.
Specifics for this sizing element for CPU Sizing
Specifics for this sizing element for Disk Sizing
.
|
| Upload of Billing Documents (optional)LOAD-BILL | Definition
This section and hence the parameters are only important, if it is planned to upload billing documents from an external source, e.g. SD. In a hybrid scenario where the majority of billing documents come from the BIT billing and only some are uploaded from an SD, the values to be entered herein might be different from those entered in the BIT billing section.
Specifics for this sizing element for CPU and Disk Sizing
|
| Convergent Invoicing (optional)CONV-INV | Definition During invoicing billing documents are converted into invoicing and subledger documents. In most cases there is a 1:1 relationship amongst them, one billing document gives one invoicing document and one subledger document, therefore this assumption has been built into the Quick Sizer. (Tip: in cases where multiple billing documents are aggregated into one invoice, the number of billing lines per invoice document should be used as input in ‘Lines per invoicing document’. This gives a better result)
The relation between billing lines and invoicing lines is difficult to estimate, it can be everything from less lines to more lines. Invoicing can aggregate billing lines but also adds tax lines to the document, hence this behavior. Example: For each phone in a company's office a bill is created and there might be only one bill for the whole office. However, it would be possible to create two invoices, one for the head of the office and one for the other employees. In this case, there would always be two invoices per contract account.
These phone bills may consist out of landline calls, mobile calls, internet usage and cellphone purchase, but there might be five lines on the invoice, one for mobile and landline calls, one for internet usage, one for cellphone purchase and one additional for VAT.
Specifics for this sizing element for CPU and Disk Sizing
|
| Subledger Documents (optional)SUBLEDGER | DefinitionSubledger documents are financial documents that are finally posted in an aggregated form in the general ledger (GL). They consist of a header and two different types of lines that represent the document as the business partner sees it and as it is seen by the general ledger. If business partners purchase a book, they might see two lines on the bill, one is the price of the book and one is the tax. These lines printed on the bill to the customer are the so-called business partner line items. The vendor might see the book sale from a different view and post the tax on one GL account. The price however is split into two parts, one to be transferred finally to the publisher, the second one to the author; hence s/he wants to post them to two different GL accounts.
When a subledger document is balanced usually another subledger document is created for which only the GL items are replicated.
Specifics for this sizing element for Disk Sizing
|
| Upload of Subledger Documents (optional)LOAD-INV | Definition
This section and hence the parameters are only important, if it is planned to upload subledger documents from an external source, e.g. a billing system. In a hybrid scenario where the majority of billing documents comes from the convergent invoicing and only some are uploaded from a billing system, the values to be entered herein might be different from those entered in the previous sections.
The disk sizing is done via sizing element SUBLEDGER.
Specifics for this sizing element for CPU Sizing
.
|
| Payment Run (mandatory)PAY-RUN | Definition
Sometimes business partners give permission to take the due amount automatically from their bank account or credit card. Their open items are closed automatically by the payment run which creates lists to be sent to the house bank and credit card companies.
Specifics for this sizing element for CPU and Disk Sizing
Note: Objects in high load phase
To account for payment runs during the high load phase do not simply enter the number of open posts to be balanced. Relevant is the number of all open items in the database, this includes also those open items which are not cleared by the payment run.
Example
In the payment run those items are balanced that participate in the automatic debiting process. In addition, you have to include the number of open posts occasioned by individual debiting. This number can be considerably larger than the number of items to be balanced in general.
|
| Payment Lot (mandatory)CD-PL | Definition
A function which enters the bank files of self-payers into the system and creates payment documents that are cleared against open items or is used in case the business partners send in checks to pay for goods or services received to balance the open items.
Specifics for this sizing element for CPU and Disk Sizing
.
|
| Dunning (mandatory)DUNNING | Definition
Not always business partners pay their open items on time. In this case, a dunning procedure is started; usually a reminder is send to the customer first before other actions like cancellation of service are done. Experience from customers shows this figure is between 5 and 10% of all documents.
Specifics for this sizing element for CPU and Disk Sizing
.
|
| Deferred Revenues (optional)DEF-POST | Definition
Once an open position has been created it is immediately due in most cases. In some cases however, this is different, e.g. if the customers buy a periodical like a monthly magazine with advance payment. In this case they have to pay a certain amount of money before the shipment starts. Once the company has received the money, they ship them one issue of the periodical every month. In this case after each shipment a twelfth of the initial amount can be transferred to the general ledger.
This is done by splitting the original document in partial amounts which are kept in the system as deferred revenues. A job to be scheduled regularly then transfers these partial payments to the general ledger.
Specifics for this sizing element for CPU and Disk Sizing
.
|
| Correspondence Print (mandatory)CORR-PRINT | Definition
A correspondence is any letter send to the business partner. This includes bills, invoices, dunning letters and other mail.
Specifics for this sizing element for CPU and Disk Sizing
.
|
SAP ERP Human Capital Management
| Personnel Administration & Payroll Accounting PA-USER | Definition Personnel Administration and Payroll Accounting from the SAP ERP HCM solution includes the following areas: Personnel Administration, Benefits, Compensation Management, Recruitment, Personnel Time Management, Incentive Wages, Business Trip Management and Payroll Accounting. |
| Personnel Planning & Development PD-USER | Definition Personnel Planning and Development includes the following areas: Organizational Management, Personnel Development, Workforce Planning, Training and Event Management and Room Reservations Planning. |
| General Remarks for the ESS/MSS Scenarios | Quick Sizer offers templates for different categories of ESS/MSS scenariosThe Quick Sizer does not reflect all existing ESS/MSS solutions as we follow the 80:20 rule. That means: 80 percent of load are caused by 20 percent of the SAP solutions. As a workaround you can try to map your scenarios to the existing scenarios which are weighted as follows: "small" would mean a complexity corresponding to the "payslip (ESS) / CICO (MSS)" scenario, "medium" would be equivalent to "CATS (ESS) / CATS Approval (MSS)", and "large" would be eqvalenuit to "travel (ESS) / Manager Homepage (MSS)". Then, additional scenarios can be sized by using the ESS/MSS component which corresponds best in complexity.
Note on Portal Sizing Portal integration is per default included automatically. After calculating the sizing result, there are two lines within the sizing result: one for ERP and one for NetWeaver. The NetWeaver line contains the portal sizing. On the result level "Sizing element" you see the result for the individual ESS/MSS sizing elements and the corresponding (automatically calculated) portal sizing element "NW-EP-ESS" or "NW-EP-MSS".
If ESS/MSS is used without Portal integration, the flag should be unchecked.
Note for usage of Web Dynpro ABAP
All sizings refelct Web Dynpro ABAP scenarios. |
| Employee Self-Service (ESS) / Manager Self-Service (MSS) | Definition ESSA concept that allows employees to access information and perform routine tasks without requiring interaction with another employee. For example, users can update their bank details or enter a leave request.
Definition MSS
A concept that allows managers to access information and perform routine tasks without requiring interaction with another employee. For example, users can perform a CATS approval. |
| ESS - SmallESS-SMALL | Specifics for ESS-SMALL Payslip With this sizing element, employees request payslips in the self-service application.
Note
|
| ESS - MediumESS-MEDIUM | Specifics for ESS-MEDIUM CATS, Leave Request, Personal Information With this sizing element, employees can enter CATS information, enter leave requests, or maintain personal information in the self-service application.
Note
|
| ESS - LargeESS-LARGE | Specifics for ESS-LARGE Travel Expenses With this sizing element, employees enter travel expense information in the self-service application.
Note
|
| MSS - SmallMSS-SMALL | Specifics for MSS-SMALL CICO (Clock-in/Clock-out on behalf) With this sizing element, managers can enter clock-in/clock-out data on behalf of their team members in the self-service application.
Note
|
| MSS - MediumMSS-MEDIUM | Specifics for MSS-MEDIUM CATS Approval With this sizing element, managers approve/reject working time data entered by employees in their teams in the self-service application.
Note
|
| MSS - LargeMSS-LARGE | Specifics for MSS-LARGE Manager Homepage With this sizing element, managers view the most important data of their team members (assuming 30 team members) in the self-service application.
Note
|
| Time Evaluation - Processed Time PairsHCM-PT | Definition Time evaluation is a program which is generated daily to calculate attendance and absence times on the basis of attendance and absence data, time types (flextime balance, productive hours) and wage types (bonuses for night, Sunday and public holiday work). Assumption: Time Evaluation is processed every working day. |
| PayrollHCM-PY | Definition 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) | |
E-Recruiting | |
| SAP E-Recruiting | Definition SAP E-Recruiting has recruitment instruments that help a company find new employees, employ them in positions that suit their capabilities, and promote their professional development. The application handles almost the entire process chain, from planning and budgeting, through attracting, hiring, and retaining employees.
General Remarks
|
| Creation of Requisition (with Posting and Publication) ERC-REQ | DefinitionA requisition is an internal document created by recruiters or managers in order to search for suitable candidates for one or more positions. A requisition contains – besides the general job information – information on organizational data, support team, job requirements, education requirements, as well as attachments for additional information and a list of job postings. Vacant jobs for which potential candidates can apply are announced using postings. Job postings are based on the associated requisition. A job posting can be published in various posting channels and for various periods. Thus various publications (for example, separated for external and internal candidates) can be created for a job posting.
The current sizing scenario comprises the creation of one requisition with general job information, assignment of three support team members, various job requirements, and three education requirements. Three attachments and questionnaires are assigned. One posting is created with two publications (one for internal candidates, one for external candidates).
To simplify matters, different pieces of information of a requisition are treated in the same way in the current sizing scenario. In order to determine the sizing of an average requisition, you add the various pieces of information (for example, number of job requirements, number of education requirements, number of postings) and enter the sum as the average number of line items. If you are unsure, just use 15 items for an average requisition.
Note that attachments of requisitions are not taken into account for disk sizing as the percentage for these attachments should be very small compared to the attachments for candidate registrations.
Specifics for this sizing element
|
| List of Candidate Assignments to Requisition (with Subsequent Processing Steps)ERC-CA-LST | DefinitionList of Candidate Assignments to Requisition is one of the SAP E-Recruiting worklists for recruiters and shows the candidates (as well as information on those candidates) that are assigned to a requisition. From this list, you can execute other steps in the recruiting process for one or more candidates (for example, invite a candidate to an interview, send an interim notification, reject unsuitable candidates).
The current sizing scenario comprises calling a list of candidate assignments to a requisition as well as 100 subsequent process steps being executed per worklist call (interim notifications, rejections).
In the current scenario, ‘Number of Sizing Objects Created per Time Unit’ refers to the frequency with which worklists are called by the recruiter and subsequent processing steps are executed. It is assumed that candidate selection lists can be seen – from a sizing point of view – as a prototypical worklist. It is further assumed that subsequent processing steps often are related to only few candidates (for example, invite to an interview) but are from time to time related to the majority of candidates (for example, rejection) who are assigned to a requisition. In order to determine the number of sizing objects, consider how many processing steps are executed overall by recruiters during peak time (including mass processing, for example of rejections). Divide this number by 100 and enter it as the number of sizing objects.
Specifics for this sizing element
|
| Candidate RegistrationERC-CA-REG | DefinitionCandidate registration means that a person who is interested in a work relationship registers in the Talent Warehouse and stores his or her data there (‘Candidate Profile’). For internal candidates (employees of the company), part of his or her data is usually already available and can be transferred to Talent Warehouse; external candidates (not belonging to the company) have to enter all of their data. Candidate data, that is, the candidate profile, comprises personal data, communication data, information on work experience, education, qualifications, and desired job conditions and work location. Attachments (such as resumes) can be uploaded by candidates.
The current sizing scenario comprises the registration of an external candidate with the following profile data: personal data, communication data, information on desired job conditions and work location, information about three different work experiences, three educations and on various qualifications. Three attachments are also uploaded.
To simplify matters, different pieces of information of a candidate registration are treated in the same way in the current sizing scenario. In order to determine the sizing of an average candidate registration, you add the various pieces of information (for example, number of work experiences, number of educations, number of attachments, and so on) and enter the sum as the average number of line items. If you are unsure, just enter 15 items for an average candidate registration.
For a Distributed Candidate scenario, the ‘Distributed Candidate Scenario’ (DCS) checkbox has to be selected for all candidate and applicant scenarios (Candidate Registration, Application for Job Posting, Job Search).
Specifics for this sizing element
|
| Application for Job PostingERC-APPL | DefinitionAn application for a job posting is a candidate´s formal statement of interest in entering a working relationship or changing an existing work relationship. An application contains the following data: a letter of application, questionnaires completed by the applicant, as well as information and documents stored by the candidate in his or her profile in the Talent Warehouse (see Candidate Registration). Thus candidate profile (such as education, work experience) can be maintained independent of an application as well as during the course of an application.
The current sizing scenario comprises the application of a registered candidate, which consists of an application letter, one completed questionnaire, and the display of profile data that has already been maintained. This means that the maintenance of profile data is not taken into consideration for the sizing of the application.
However, if your standard application scenario also includes the maintenance of all profile data, we recommend you calculate the sizing as the total for the 'Application' scenario and the ‘Candidate Registration’ scenario.
In the current scenario, the number of sizing objects refers to the number of applications you expect within peak times. The average number of line items refers to the number of steps executed for an application. If you are unsure, just enter 8 items.
For a Distributed Candidate scenario, the ‘Distributed Candidate Scenario’ (DCS) checkbox has to be selected for all candidate and applicant scenarios (Candidate Registration, Application for Job Posting, Job Search).
Specifics for this sizing element
|
| Job SearchERC-JOB-SE | DefinitionPersons who are interested in a work relationship (employees or externals) can search for jobs.
In the current scenario, the number of sizing objects refers to the number of searches you expect during peak times.
For a Distributed Candidate scenario, the ‘Distributed Candidate Scenario’ (DCS) checkbox has to be selected for all candidate and applicant scenarios (Candidate Registration, Application for Job Posting, Job Search).
Specifics for this sizing element
|
Logistics Execution
| Logistics ExecutionLE-USER | Definition Logistics Execution contains Warehouse Management as well as Inbound and Outbound Logistics |
| Stock Movement LE-WM | Definition The business object transfer order is an instruction to move materials from a source storage bin to a destination storage bin within a warehouse complex at a specified point in time.
Line items: A transfer order consists of items that contain the quantity of the material to be moved and specifies the source and destination storage bins.
|
| Delivery Notes & Goods IssueLE-SHP | Definition Number of delivery notes and goods issue.
Line items: Average number of line items for delivery notes and goods issue.
|
Product Development & Execution
| PM OrdersALM-USER ALM-PM | Definition Orders in the sense of maintenance orders. Requirement to execute a maintenance task on a maintenance object for a 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 ManagementMM-USER | Definition Materials Management contains Inventory Management as well as Purchasing. |
| Materials MovementMM-IM | Definition Physical or logical movement of materials which leads to a change in material stock levels or results in direct consumption 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 OrderMM-PUR | Definition Request or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a certain quantity of material or to perform certain services.
Line items: A purchase order consists of a number of items, each of which will have a procurement type defined.
|
| Comment We assume a purchase order has two text lines on average. 30% of the purchase orders are assigned to an account.
10% of the line items have delivery costs. There is one goods receipt line item per purchase order line item. There is one invoice line item per purchase order line item.
| |
| Production Planning and ControlPP-USER | Definition Production Planning contains Sales & Operations Planning, Master Planning Capacity planning as well as Material Requirements Planning. Production Control deals with Production Orders, KANBAN and Repetitive Manufacturing. |
| ConfirmationsPP-CONF | Definition Documents the processing status of operations or sub-operations. A final confirmation is used to determine:
|
Comment
| |
| Repetitive Manufacturing (Planned Orders)PP-REM | DefinitionA component in the SAP System for planning and controlling repetitive manufacturing and flow manufacturing.
It enables the period-dependent and quantity-dependent planning of production lines and reduces the work involved in production control and simplifies backflushing (confirmation, goods receipt posting).
|
| Production OrdersPP-SFC | Definition 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.
|
![]() | |
| 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:
Note
| |
| Comment We assume:
| |
| Project SystemPS-USER PS | Definition Projects: A complex structure of tasks within a controlling area which is used to control and monitor the schedule, resources, capacities, cost, revenues, and funds availability.
Specifics for PS
Due to the nature of project plans the procedure for entering data is slightly different from that in other components. Each year, usually only a few projects with many WBS elements are created. In contrast to other objects, such as FI documents projects are changed frequently, sometimes several times per day. This aspect of Project System is addressed in the Quick Sizer as follows
For average load
For peak load
For example:
Every year, 150 projects are created with an average of 500 WBS elements. They remain in the database for about five years. On the average, each project consists of 20 networks and 100 activities per network. The estimation of the total number of changes and displays per project bases on the assumption that a project is changed three times and displayed once per working day over a period of 2 years. In a high load phase, 300 projects are changed five times and displayed once during a day. Additionally, on these very busy days, 10 projects are created. The sum of the number of new projects, changes, and displays is:
10 + 300*5 + 300*1 = 1.810
You enter the following data in the Quick Sizer:
Average load:
Peak load:
|
| Comment For calculation we assume:
| |
| Inspections in Quality ManagementQM-USER QM-IM | Definition Tasks for determining the actual status of a technical system (for example, a machine) or a material.
Inspection Characteristics: The basis on which an inspection is performed.
|
| 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 Requirements Planning MRP RUN | Definition Material Requirements Planning (MRP) Generic term for procedures in materials planning which take into account and plan every future requirement during the 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
|
| Comment We assume the following:
| |
Sales & Service
| Customer ServiceCS-USER CS-AG | Definition Application component that can be used to process services. Customer Service mainly comprises the following functions:
Components:
The sub-object of an order is a component. In an order, components are usually materials assigned to an operation. Enter the average number of components per order. |
| Comment We assume that one operation is valid for five components. |
| Incentive and Commission Management ICM | Definition Incentive and Commission Management delivers the capability to define various commission plans and render payment through the SAP payroll solution, thus rounding out the compensation solution. Please note that Sizing measurements are based on the standard table widths of ICM. |
| ICM Case ProcessingICM-CASE | Specifics for ICM Case Processing
|
| ICM Document PostingICM-DOC | Specifics for ICM Document Posting
|
| ICM SettlementICM-SET | Specifics for ICM Settlement
|
| Sales & DistributionSD-USER | Definition Sales & Distribution contains Sales and Billing as well as Shipping. |
| Customer InquiriesSD-CUST | Definition A customer request to the company for a quotation or sales information that is not binding. The request can refer to 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
|
| InvoicesSD-BIL | Definition Sales and distribution document used to charge a customer for a delivery of goods or for services rendered.
Line items: Number of line items per invoice.
|
| Sales Data and IDocs SD-POS | Definition Number of Sales Data and IDocs created per year. The Quick Sizer assumes that for every Idoc, one material document and one billing document are generated with subsequent postings to FI. The IDocs themselves are assumed to be archived immediately.
The column "number of objects created per year" refers to the number of documents created per year. The next column "number of subobjects....." refers to the number of line items per document.
The Quick Sizer considers aggregated upload (WPUUMS). In the case of WPUBON, you will have to consider the following:
The total number of line items is the product of number of customers and the number of articles per customers.
Example: You have 500 stores with an average of 300 customers per day and an average of three articles per customers. Assuming one IDoc per store this will give you:
|
| Comment Number of Sales Data and Idocs created per year. The System creates one goods issue and one bill per document/IDOC including the respective number of line items. With each bill and material movement, one FI document with the respective number of line item is created. Additional postings are not considered.
When processing different IDOC-types (e.g. store order), enter any follow-on documents separately (such as SD order line-items in SD-SLS).
| |
In the following graph you can see the factors that influence sizing.![]() | |
| Sales OrdersSD-SLS | Definition A customer request to the company for delivery of goods or services at a certain time. |
Corporate Services
| Travel ReceiptsTV-RECEIPT | Definition Enter the number of receipts from business trips. These can be
Line items are the average number of line items per receipt, for example travel costs, meals, or accommodations.
|




