Skip to Content
This blogs succeeds the one on determining the sizing KPIs Efficient SAP Hardware Sizing: Quick Sizer. For more information on Quick Sizer results, see Interpreting Quick Sizer results.

Quick Sizer for Initial Sizing

As mentioned before, initial sizing, when you have only a vague idea of the expected workload is dominated by a user sizing. Sizing for your concurrent active users is pretty straight-forward in the Quick Sizer. It only takes into considerationusers that are logged on and consume system resources, for example in the Enterprise Portal or in mySAP CRM. In some solutions the Quick Sizer requires you to specify in which application the users work predominantly, in mySAP CRM, for example, it distinguishes between Opportunity Management, Activity Management, sales transactions or service transactions. In some user sizings you are requested to specify an activity profile, for example: how many users have a low, medium or high activity? The activity patterns merely expresse the number of screen changes per user per hour. A highly active user, for example, corresponds to a power user with a think time of 10 seconds between screen changes.

When you’ve entered the user information and choose “calculate result”, you’ll get the following information for each SAP solutionThe required

  • CPU power in SAPS (hardware-independent, see above)
  • Disk space in MB
  • Memory in MB (in units of 256 MB)

For your convenience, there are categories for the disk and CPU result that indicate whether you are in a small or medium sized environment. As explained above, the initial sizing is only a very rough ballpark estimate which is why I would not recommend relying only on a user-based sizing if the result is higher than 5000 SAPS. User sizing per se is very inaccurate in the sense that it does not account for background processes, interfaces, and so on, and therefore the Quick Sizer provides high sizing results as compared to throughput sizing. So if you happen to do both user sizing and throughput sizing and find that the results deviate significantly, this can be either because you have specified a user activity that is too high or because the throughput sizing is more accurate.

The Quick Sizer does not offer user sizing for all applications. The Exchange Infrastructure (XI), for example, has no user sizing. As a pass-through engine, it has no dialog load. For this, we provide an initial throughput sizing for SAP XI.

Quick Sizer for Advanced Sizing

When you are a little more familiar with how SAP software represents your business applications, you’re ready for advanced sizing based on throughput numbers. This sizing is usually more accurate for several reasons. The Quick Sizer contains some 120 sizing elements for throughput sizing that reflect the most common and potentially most load-consuming transactions and business applications for mySAP.com. The information the Quick Sizer wants to know follows a simple pattern: Number of objects (projects, printed documents, sales orders or travel receipts) per year, number of sub objects (networks, activities or line items) and how many months these data will remain in the database until they are archived. If you enter this information and choose “calculate result“, the Quick Sizer renders basic CPU and disk requirements (remember that memory is dominated by users). This sizing method is called “average sizing” from which you can build on towards a peak sizing.

The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing). You enter the number of objects and sub objects and specify the time period when these objects are being processed, for example: The payroll of 200,000 employees from 2 am to 4 am. If this run coincides with the nightly background run for the materials requirements planning, the Quick Sizer shows the peak CPU requirement. When we say peak sizing, we mean the peak over all individual sizing results. If the average sizing for a sizing element renders 1000 SAPS, and the peak sizing 1200 SAPS, the overall result of the sizing is 1200 SAPS. If the peak sizing should render a value below the average sizing (if specified by you), the Quick Sizer issues a message.

You can then go on redefining your sizing:

  • For example, you can enter how often an object is changed per year or per peak phase. This influences the CPU sizing.
  • You may also want to change the average workday. Per default, the Quick Sizer assumes that an average workday ranges from 9am to 6pm, which you can easily change, thus influencing the CPU result.
  • The Quick Sizer also assumes 220 work days per year as a default. If you adapt this value to your needs, this also influences the CPU result for the average sizing. By the way, the number of workdays also influences the disk sizing for the users.
  • You can extend the average sizing by allowing for multiple averages. For example: in a customer system, orders are created in mySAP CRM, by handhelds and by Interaction Center users. The orders are transferred to the ERP system for full order processing. By adding lines, you can distinguish between the orders that were originally passed on from the handheld scenario and the Interaction Center. To make this information transparent you can add a short text to each line. The Quick Sizer will add the averages and calculate the result for you.
  • One function that, strictly speaking, is not relevant for the sizing calculation is the archiving flag. If you enter this, the Quick Sizer checks whether an archiving object for this sizing element exists.

Below find an example for a simple sizing of travel receipts. The “number of objects” field contains the number of travels, and the “Line items” field refers to the number of receipts.
image
Figure 1: Example for simple average sizing.

If you use all these functions, you can get a pretty accurate representation of the hardware required to run the business. However, this sizing will always be based on standard processes that SAP has designed and measured.

Quick Sizer for Expert Sizing

Expert sizing makes the utmost use of the standard functions of the Quick Sizer. Expert sizing is for customers whose business requirements encompass the rule of 80/20 (80% of the load is created by 20% of the transactions), first-and-foremost because of custom modifications, system to system data exchange, customization, and so on.

One standard function of the Quick Sizer that can be exploited for expert sizing is the possibility to set multiple averages against multiple peaks. The Quick Sizer always checks which sizing method renders the higher CPU value, average or peak. Using a function called “ID” for identification, you can specify which averages are calculated against which peaks. This is very helpful for complex scenarios, for example in the retail business or in the example above, where orders come in from very different sources. The figure below shows you an example. CRM-SLS is the CRM sizing element “sales orders”, “A” specifies average sizing, “Y” stands for objects per year.
image
image
Figure 2: Example for multiple averages.

If you do not enter anything in the ID column, all averages are added and calculated against all peaks, which may blur the result.

Also, you can use rules of thumb mapped to the Quick Sizer to account for special processes. For example, there is a rule that says “to account for additional load caused by RFC processing, add 10% load on the sales orders that are transferred to another system”. In this case, you would add an additional line for peak, enter 10% of the number of orders and add in the short text field “additional RFC load”.
image
image
Figure 3: Example for multiple averages against mutiple peaks and rule of thumb.

In principle however, expert sizing can only take place if the customer already has a test system up and running. Then we recommend using standard SAP system monitors to obtain sizing relevant information such as CPU time, table size and memory consumed – per business process. If you have this information you can relate it to the Quick Sizer. For example, you have written your own sales order application and your measurements show that this is 1.5 times as expensive as the Quick Sizer sales order. Then you can simply exploit the functions of the Quick Sizer for your own software by applying a factor of 1.5.

Quick Sizer and GoingLive

SAP Support offers the GoingLive Check (GLC), and one of the features of GoingLive (GL) is the plausibility check of the sizing where the Quick Sizer entries and sizing results are checked against the performance capabilities of the hardware the customer has purchased.

This can be done on the basis of the sizing data. In some cases, GLC offers additional checks if certain business processes are not (yet) included in the Quick Sizer. When you are ready, you can simply set the status of your sizing project in the Quick Sizer to “GoingLive”. Then the ownership of the sizing projects changes to GoingLive, to SAP Support, that is. You yourself are not able to make modifications to this project until SAP Support has changed the project status to “in process after GL”. That way, SAP and customer can work together on the hardware plausibility check relying on the same data. If you set the project to final, no one can change the project anymore.

Interpreting Quick Sizer Results

For reasons of better analysis, the Quick Sizer allows you to analyze sizing results at very different levels of detail. Here are the most important ones.

Result at solution level

By default, the Quick Sizer displays the sizing result by sizing method (user and throughput) and by SAP solution, for example mySAP ERP or SAP Netweaver. For each solution the Quick Sizer displays the required:

  • CPU power in SAPS (hardware-independent, see above)
  • Disk space in MB
  • Memory in MB (in units of 256 MB)

For easier analysis, there are also categories provided. If you only have a user-based sizing and if this result exceeds category 7, you should either perform a throughput sizing or contact your hardware vendor or SAP. If you did both sizing methods and the category exceeds 15, you should also contact the hardware vendor or SAP for help. For your convenience, you can display a chart of the CPU load over the day.

Result at software component level

To plan your system landscape it is helpful to know the hardware requirements for each software component, for example Enterprise Core Component (ECC) or Portal Server. On this result level, the results are also split to reflect load on the application server and on the database server, for example.

Display all inputs and all results

This function is predominantly useful for documenting the sizing project as it contains all the data you entered and all the results of the Quick Sizers. With the print function you can download this information to save on your PC. This function is also helpful if you want to analyze the sizing data in more detail. More often that you think you can detect erroneous entries by simply doing a plausibility check on the highest CPU or disk contributors. This result level also provides detailed information on the top disk contributors, the table names, the projected growth, available archiving objects, and so on.

For more information, see Blog on interpreting Quick Sizer results.

To report this post you need to login first.

80 Comments

You must be Logged on to comment or reply to a post.

  1. Hi Susanne,

    Thanks for the useful blog. I have few questions about the quicksizer :
    1) Why does not let me changed the name from the standard name? I am using the BI part and want to name the InfoCubes & ODS with the real names than just INFOCUBE or ODS.
    2) Is there a way to quickly copy paste into the table control. I have nearly 70 InfoCubes to size, I want to avoid hitting the insert button and typing in manually!
    3) Why doesn’t the sizer taken InfoObjects into consideration?

    Thank you.

    (0) 
    1. Susanne Janssen Post author
      Hi Sridhar,
      Thanks for your comment.
      1) because it’s atechnical component, but you can name it using the short text function in each line.
      2) I’m, afraid, not at this stage.
      3) What do you mean by info objects?
      Regards,
      Susanne
      (0) 
  2. Mike Woodward
    Suzanne, for FI-CA, I notice you now have added Utilities to the Insurance model that you had before.  I want to size PSCD (Public Sector FICA flavour).  We used to use the Insurance one for this. I have 3 Questions:
    1. Do you intend to do a specific one for PSCD & if so, when?
    2. If not, would it not be a good idea to make Insurance easier to use, by, in the help, to specify which PSCD metrics map to which Insurance metrics?
    3. For the new Insurance model,
    a) the master data metrics (BP’s, CA’s i-objects) have now disappeared- where do we enter them?
    b) In “SubLedger”, is the “Payments” metric absolute or “payments per posting doc”?

    Thanks in anticipation,
    Mike

    (0) 
    1. Susanne Janssen Post author
      Mike,
      Thanks for getting back to me. There is a guideline how to map PSCD available at service.sap.com/sizing -> sizing guidelines -> business suite and services, it explains exactly how to use the Quick Sizer to size this feature.
      Best regards,
      Susanne
      (0) 
      1. Stephan Fabrizius
        Hello Susanne,

        is there an update available where to find those PSCD related doc?
        Can not find it under /sizing –> siziing guidelines –> business suite and services.

        Thx a lot,
        Stephan

        (0) 
  3. Jes Hvoldal Nielsen
    Hi Susanne

    How should I use the BPM Ratio parameter for Split/Collect BPM Patterns?
    I have tried entering a few numbers dependant upon how I read the explanation for this column
    and it has a big impact on the calculations.
    Could you please give a hint on how to find the correct value to enter.

    Thanks and best regards /Jes

    (0) 
  4. Fernando De Mattos
    Hello Suzanne – Hope this note gets to you. I have a very basic question, once I know my sizing results on SAPS what does it mean? I guess my question is what does 100 or 1000 SAPS translate to?

    Last question, I couldn’t find a specific sizing tool for MSS, is there one? If not, is it okay to use the ESS one instead?

    Thanks in advance,

    Fernando De Mattos

    (0) 
  5. I want to enter 1500 for a concurrent number of users in EP.  When I hit save it changes it to 1.500.  The same for the hits per hour and searches per hour.  How do I have it accept 1500?  I tried entering 1500 with a decimal at the end and it didn’t like that.

    Regards, Scott

    (0) 
    1. Susanne Janssen Post author
      Hi Scott,
      This is the right number format, only in European format which separates the 1000 with a dot (1.000) instad of a , (1,000) . Which format is being displayed depends upon your seetings in the Service Marketplace. I have US-settings and it displays as “1,500”.
      Best regards,
      Susanne
      (0) 
  6. lareina liu
    Hi, want to ask whether there is any specific concerns should be taken into account regarding SAP IS Retail hardware sizing?  Many Thanks
    (0) 
    1. Susanne Janssen Post author
      Hi Lareina,
      Retail, as high volume business, has a number of specific processes. In general, you can map a high number of them to the Quick Sizer, for some specific sizing guidelines apply. There is a dedicated retail offline questionnaire available at service.sap.com/sizing -> sizing guidelines -> solutions % platform (ID required).
      Best regards,
      Susanne
      (0) 
  7. Hervé Cayetanot
    Hi,

    Our BW 3.1 systems are going to be upgraded to BI 7.0 this year and we’re going to deploy BI-Java and Portal 7.0 for web reporting in addition to traditional Bex reporting.
    How can quick sizer be used to evaluate the additional load caused by Java & Portal on the existing infrastructure ?

    Thanks

    (0) 
    1. Susanne Janssen Post author
      Hi Hervé,
      Thanks for your question, a good one, too. We are currently preparing a sizing for this, which we will include in the Quick Sizer. Until the Go-Live, there will be a note.
      best regards,
      Susanne
      (0) 
  8. Andrea Vitolo
    Hi Susanne, thank you for this great weblog.

    I have to do a sizing for an R/3 Enterprise ext. sets 1.00, but the Quick Sizer don’t let me to choose this product. Can I use this tool for the Enterprise? The results obtained for ECC 6.0 can be used for R/3 Enterprise?

    Thanks in advance.

    (0) 
    1. Susanne Janssen Post author
      Hi there,
      Indirectly, you can use the Quick Sizer for sizing R/3 Enterprise. Just create a sizing and reverse-apply note 774778 and attached, which describes the additional load required for an upgrade from 4.7 to 5.0.
      Best regards,
      Susanne
      (0) 
      1. Andrea Vitolo
        Hi Susanne, thank you for your response.
        I’m not shure but maybe the SAP note number is wrong. May you confirm this?

        Best regards

        Andrea

        (0) 
  9. Thomas Bauer
    Hi Susanne,
    erstmal danke für den sehr informativen Blog. Für Sizing Dummies wie mich ist das ein super Einstieg. Aber ich habe trotzdem noch eine Frage: Wie kann man denn mit dem Quicksizer noch BW 3.5 Landschaften sizen? Oder mit welchem Faktor muss man ein 2004s Sizing bewerten um auf ein 3.5 System schließen zu können? Soweit ich gesehen habe kann man das BI Release nicht auswählen. Besten Dank schon mal und viele Grüße,
    Thomas
    (0) 
    1. Susanne Janssen Post author
      Hi Thomas,
      Thanks for your feedback.
      You question was, if you can use the QS to calculate BW 3.5, even if the QS is on 7.0, as our measurements have shown that overall the utilization on the ABAP stack is the same. Make suer you only takte the ABAP SAPS and not the JAVA SAPS.
      Best regards,
      Susanne
      (0) 
      1. Hi Susanne,

        Your answer was very helpful but now how to size an complete BW 3.5 environment.
        Scenario: the customer would like to buy a new host but he wants a new sizing using his BW 3.5, can I use the QS available?? I have tried the old QS but now is only for Display… Could you help me??

        (0) 
      2. Hi Susanne,

        Your answer was very helpful but now how to size an complete BW 3.5 environment.
        Scenario: the customer would like to buy a new host but he wants a new sizing using his BW 3.5, can I use the QS available?? I have tried the old QS but now is only for Display… Could you help me??
        Thanks in advance
        Luis

        (0) 
  10. Kentaro Takao
    Hello Susanne.

    I’m not sure if this is the right place to ask, but it’s quite urgent.

    I’m trying to input to BW SEM-BPS-2, but the values don’t meet the requirement, which is 900,000 after some calculations inside the QS.
    These values are the real numbers taken from an active system.
    It seems the system is running fine, but I need to calculate SAPS for the correct sizing.

    I appreciate if you could provide a solution.
    Input values can’t be changed because as I said, the values are taken from an active system.

    Thank you in advance for your support!!

    (0) 
    1. Susanne Janssen Post author
      Hi Kentaro,
      there are two answers to your question.
      1: Apparently you are re-sizing you system, either you are adding load or upgrading. For this exercise you should never use the Quick Sizer but interpret your live data. For the procedure of re-sizing, please see service.sap.com/sizing -> sizing guidelines -> general -> “re-sizing”.
      2: not knowing your inputs, it may be that you already entered multiplied data that the Quick Sizer would usually multiply taking different input fields into consideration.

      Best regards,
      Susanne

      (0) 
  11. Xiaogang Pan
    Hi,

    Not sure if here is right place to ask, but I do have problem with CRM 5.0 sizing.
    We are upgrading our CRM system from 4.0 to 5.0 by adding new functions (Campaign Management and Segmentation) and more users (adding 150 Maketing users), but the quick sizer doesn’t have function to sizing those two modules, the guideline I found for sizing those two modules is base on CRM 4.0, can we use those 4.0 document to sizing 5.0?

    Thanks,
    Xiaogang Pan

    (0) 
  12. Yes SAP Team
    Hi Suzan.

    Since the last comment was long time ago I hope this one will be answered.

    1.
    I don’t understand how can I add a line and insert a new Element since this column looks read-only.

    2.
    This is a problem all over when you want to communicate with SAP and you need to choose a component. We only know Transaction-codes and we don’t know how to relate (for example) Transaction “F-43” to a component.

    thanx.
    ayal.

    (0) 
    1. Susanne Janssen Post author
      Hi Ayak,
      Let me try to answer your questions.
      1: Is your question: “How can I insert a new sizing element”?
      Sizing elements are predefined by SAP and cannot be created on the fly. They represent business objects or business scenarios that representing sizing-influencing patterns.
      2: Is your question: “Why are sizing elements not aligned to transaction codes?
      The Quick Sizer is targeted at initial, i.e. new sizings, where users are not familiar with transaction codes but rather think in scenarios or business objects.

      (0) 
      1. Glen Canessa
        Hello Susanne. Thanks for your response.

        But what about a user based sizing, where no retention periods are specified.
        The DB size result is for 1 year period?

        Even when retention periods are specified, they may be different for each type of document (6, 12, 18 month, etc.), and the database will keep growing forever. So, the calculated size will correspond to what period?

        (0) 
        1. Susanne Janssen Post author
          Hi Glen,
          for the users its one year, depending on the number of workdays.
          Please note that an exact disk sizing can only be done based on the actual business objects and their residence time on the DB. Anything other doesn’t make much sense.
          For more info on this see service.sap.com/sizing -> guidelines -> general -> principles of user and throughput sizing.
          (0) 
  13. David Braithwaite
    Hi Suzanne

    Is there a way to know the version of the Quick Sizer used at the time data is entered and the features  (such as applications where sizing results include unicode requirements).

    (0) 
    1. Susanne Janssen Post author
      Hi David,
      Sure. you’ll find the version on the project information page and on the print files whenever you print or save the project to disk.
      The features are listed in the change history. The Quick Sizer is completely unicode.
      Best regards,
      Susanne
      (0) 
      1. Susanne Janssen Post author
        Hi David,
        The calculation is independent of UTF, as we collect the table sizes from the “SAP-side” and not from the database.
        Best regards, Susanne
        (0) 
  14. Chaitanya Shah
    I changed my status of the project to going Live when is sap support team going to change it from Going live status to in process. Can I contact the SAP support team directly.
    (0) 
  15. Wajid Mir
    Hi Susanne,

    In order to evaluate

    1. the application architecture (business processes, transactions involved, functionalities implemented – e.g. E-commerce in CRM)

    2. technical architecture (OS, DB, CPUs, Users, Network speed etc.)

    at a given customer site, is there a questionnaire available for each (application & technical) that can be sent to the Business Analysts & Sys Admins to fill out?

    This information can be later translated into input for the Quick Sizer tool.

    Thank you,
    Wajid.

    (0) 
    1. Susanne Janssen Post author
      Hi Wajid,
      The Quick Sizer is only meant for initial sizings, therefore we do not provide such a document to return-feed the customer information into the tool. Customer data as a basis for production sizings is much more valuable than turning it into a tool which is geared at initial budget planning.
      For more information on production sizings see service.sap.com/sizing –> guidelines –> procedures –> Post Golive Sizings.
      Best regards,
      Susanne
      (0) 
  16. Francois Blanck
    There is very little information on the “%chg. %dsp” fields, neither here or in the “Sizing” Service Marketplace. They must however have a major effect.

    1) What is the recommendation for using these fields?

    2) Are there any “used case” figures (e.g. 30% of MM-IM Objects get changed and each CO-PA-FI Object is displayed at least 3 times i.e. %chg = 300%)?

    3) If the Object is printed, would that be reflected in these fields? Or is BC-Print to be used with a total of all Objects actually printed?

    (0) 
    1. Susanne Janssen Post author
      Hi Francois,
      There is a small documentation in the Service Marketplace in the area of “using the Quick Sizer”, Quick Sizer for beginners where these fields are explained. % Changes/Displays affect the CPU calculation only.
      1) This is a very general question. there is no particular recommendation other than: if you can estimate on average, how often a document is being changed, just enter 100 for each change.
      2) Use cases depend very much on the customer. There are certainly objects that are changed more often than others. Projects ought to be changed hundreds of times.
      3) printing is not included, you can use BC print, but please note that BC Print reflects SAP scripting.
      Best regards,
      Susanne
      (0) 
  17. MaryJane Steele
    When I try to calculate my results I get the following messages

    Questionnaire ERP-SLSSRV, element SD-SLS, starttime 08:00: peak sizing <= daily sizing

    Questionnaire ERP-SLSSRV, element SD-SLS, starttime 09:00: peak sizing <= daily sizing

    It makes no sense to me because of course my peak sizing is less than my daily sizing. How do I fix this?

    (0) 
    1. Susanne Janssen Post author
      Hi Mary Jane,
      I think there is a small misunderstanding. Sizing is all about peaks and providing sufficient hardware for peak usage.
      When you say: “… of course my peak sizing is less than my daily sizing”
      Frankly, this doesn’t make sense from a sizing perspective. As the description in the blog says:
      “The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing).”

      The Quick Sizer shows this error message when the result for the peak sizing is below the average in your case the hours specified are between 8-10.

      Best regards,
      Susanne

      (0) 
    2. Susanne Janssen Post author
      Hi Mary Jane,
      I think there is a small misunderstanding. Sizing is all about peaks and providing sufficient hardware for peak usage.
      When you say: “… of course my peak sizing is less than my daily sizing”
      Frankly, this doesn’t make sense from a sizing perspective. As the description in the blog says:
      “The peak sizing method helps you to identify CPU peaks during the busiest day of the year (for example right before Christmas or year-end closing).”

      The Quick Sizer shows this error message when the result for the peak sizing is below the average in your case the hours specified are between 8-10.

      Best regards,
      Susanne

      (0) 
  18. Martin Rodriguez
    Hi!

    I hope you can help me with this.
    I’m using QuickSizer to estimate a production environment.
    Can you tell me more information about this comments in help page:
    – In line BWP enter the number of lines per mail in the field for sub components.
    – In the lines for the emails enter the number of recipients for external and internal mails in the field for sub components.

    What information is necessary to be filled in elements BWP?
    Thank you in advanced.

    (0) 
    1. Susanne Janssen Post author
      Hi there,
      SAP has an e-mail capability called the Business Workplace. In case you are using it, you can fill in the fields. Otherwise, you just may want to skip it.
      Best regards,
      Susanne
      (0) 
  19. Eric Poellinger
    Hello,

    I was curious how the average number of workdays (220) was arrived at as an assumption. 

    I am attempting to do an initial sizing for a global system, so my thinking is that I would increase the number of workdays, since the concept of a “weekend” is reduced due to a near 24 hour business day. 

    Thank you

    (0) 
  20. Hello,
    in the way of sizing we have to check the sap product configurator. Where can I find informations to use the quick sizer? Also, we have a complex pricing and use the online availibility check for material.
    Can You help me?
    Thanks
    Andreas Vogts
    (0) 
    1. Susanne Janssen Post author
      Hello,
      product configuration and extensive pricing are usually too custom-specific in order to be reflected truthfully in standard sizing guidelines. For these, I suggest you make an expert sizing (checking the relavant monitors) to be a accurate and custom-specific
      The ATP check can be sized in the SCM section of the Quick Sizer.
      Best regards,
      Susanne Janssen
      (0) 
  21. Satya Praveen
    Hi Susanne,

    Could you suggest ,which all aspects we need to consider for EP7 sizing on Unix boxes ?

    I have gone through quicksizer tool, but it considers only concurrent users,avg think time, iviews as inputs based on which the calculation of sizing is difficult as we need to take into consideration infrastructure specifications like …. High availibilty, load balancing and also application usage , implementation of KM , collobration other componenents of portal , NWDI implementation, Trex and integration with back end SAP systems , portal access for external user in addition to intranet users.

    May I know , how do we analyse the above aspects as I mentioned for sizing or
    quicksizer is the only tool for sizing ?

    Regards
    Praveen

    (0) 
    1. Susanne Janssen Post author
      Hi Praveen,
      The Quick Sizer does include KM, TREX and backend applications. NWDI sizing guideline is available on the Service Marketplace. H/A and Load balancing is not part of sizing, but rather config and landscaping.

      Regards,
      Susanne

      (0) 
  22. Vivek Ashok Pai
    Hello Susanne,

    Can you pls let me know what the Columns Numfld , txtfld stand for in the BI Datastore Object sizing . Does it mean Key figures and characteristic ?

    Thanks for your support.
         
    Regards,
    Vivek

    (0) 
  23. Vivek Pai
    Hello Susanne,

    Thank you.

    One more doubt as it is not clear from help .Pls let me know whether the Data Upload during Peak time corresponds to data loaded from source system or it takes into account data loaded into different levels of BW as well . For eg. A data record can be loaded to PSA , Active data table, Change logs , Cube etc. do we need to count the record multiple no of times or we should count the record as one only  ?

    Thanks for you support,

    Vivek Pai.

    (0) 
    1. Susanne Janssen Post author
      Hello,
      I asked a BI colleague. Here’s the answer:

      The peak data load describes the amount of records than need to be loaded into the first persistence level of BI in a given time frame. In detail this means that it includes extraction from the source system, transfer of the data to the PSA, and then either update into an InfoCube or into a DataStore object (including activation). If you plan to have several data staging layers, then you should (as a rough estimate) add the same amount of records for each additional stage, e.g. extraction of 1 million records to PSA, DataStore and then from DataStore to InfoCube would render twice the amount of records extracted from the source system.

      Best regards,
      Susanne

      (0) 
  24. Oscar Fernandez Moreno
    Hi,
    I am planning sizing a Production environment for an upgrade from 4.7 to ECC 6.0 including change to UNICODE installation (old version is non UNICODE). Is there any way to calculate or estimate the impact using Quick Sizer?

    Thanks and regards.

    (0) 
    1. Susanne Janssen Post author
      Hi Oscar,
      we recommend to use the Quick Sizer only for initial (new) sizings. For upgrade please check SAP note 901070 for delta information. The process is described in a PPT called “sizing from blueprint to upgrade” which you can find at service.sap.com/sizing –> general sizing guidelines.

      Please also check service.sap.com/unicode reagrding the additional requirements through unicode.

      Best regards,
      Susanne

      (0) 
      1. Danesh Osman
        Hi,

        Would like to know after doing sizing I  got 4200 SAPS

        is that we need to divide 4200 sap  between  whole ERP landscape DEV , QAS and PRD   or it is for PRD  system

        Mazhi

        (0) 
        1. Susanne Janssen Post author
          Hello,
          this is not really a unicode-related question, is it? The Quick Sizer sizes according to the input. If you entered business data from the production system, then the result is valid for the production system. DEV, QAS and PRE-Prod need to be sized separately.
          Best regards,
          Susanne Janssen
          (0) 
    2. it’s an additional one.

      For new sizing, is Quicksizer result includes yet Unicode Impact????????

      Best regards!
      bobis

      (0) 
      1. Susanne Janssen Post author
        Hello,
        Basically, all Quick Sizer results include
        Unicode.

        If you have additional questions on using the Quick Sizer, please refer to a document on the SAP Service Marketplace:

        http://www.service.sap.com/sizing –> Quick Sizer Tool –> Using the Quick Sizer
        –> Experts–> Quick Sizer Best Practices

        Best regards,
        Susanne

        (0) 
  25. Diana Gomez Rio
    Hi,

    I am performing the sizing of my system. In my landscape there is no PI and we will perform the interfaces directly from the ECC system. How can I check the impact of this in my system? I have not found any clue about how to reflect it in the Quicksizer. Any idea?

    Thanks

    Diana

    (0) 
    1. Susanne Janssen Post author
      Hello Diana,
      the load depends a bit on the protocol you will be using and you need to size the interface load on the sending and the receiving system. Please see service.sap.com/sizing –> guidelines –> sizing from blueprint to upgrade.
      Best regards,
      Susanne
      (0) 
  26. Glen Canessa
    Hi Suzanne,
    SAP recently changed its SD benchmark from 2 sec to 1 sec response time. So, now we have vendor benchmarks with 2sec-SAPS and with 1sec-SAPS. Has this change been reflected in quicksizer? If not, when quicksizer results are, for example, 10,000 SAPS, if I select a platform with 1-sec benchmark, I will be oversizing. Conversely, if quicksizer now reports 1-sec SAPS and I select a platform with a 2-sec benchmark, then I will be undersizing it (40% I estimate).
    Is this correct?
    Are there any plans to normalize this / Instructions for users?

    Regards
    Glen

    (0) 
    1. Susanne Janssen Post author
      Hello Glen,
      the Quick Sizer team states the following: In the benchmarks you need to factor in a wait time of 10 seconds between the interaction steps. This means for example, that 6000 steps in the old Benchmark take about 11/12 of the time compared to the old Benchmark, and not 50%. This results in a difference of about 5 % for the SAPS of a hardware.

      We carefully discussed the question, whether this (and other changes in the SD benchmark) should have an influence on the existing sizing calculation in the Quick Sizer. We decided to keep the values for the majority of the sizings, with the exception of CRM, were we adjusted the calculation as of March 2009.

      Best regards,
      Susanne

      (0) 
  27. John Marshall
    Hi Susanne,

    I have a client who want to implement Enterprise Portal. Basically, it is just to be used as a front-end to their backend ECC/SRM/BW systems to avoid having to logon multiple times via the SAP GUI. There won’t be any Business Packages loaded or any fancy development or any use of KM, at least not initially.

    My question is which area of the Quicksizer should I be using? The only scenario which seems appropriate is the ‘SAP Netweaver -> Portal and KMC’, and then use the NW-EP-URL element within that. Is this correct? I can’t see any other portal-related scenarios.

    Kind regards…John

    (0) 
    1. Susanne Janssen Post author
      Hello John,
      Thanks for your question.
      For your purpose the sizing element NW-EP-URL (NetWeaver Portal for launching back-end transactions using URL iViews) is indeed the appropriate one.

      Please make sure you also read the extensive help using the help button on each Quick Sizer page.

      Best regards

      (0) 
  28. SAPLOVER Ali
    Hello,

    We have requirement to process payroll for 10,000 employees and we are expecting at a peak we would have 19 retros. So would it be right to enter the value below in the element HCM-PY:

    (no. of emp) * (1+no. of retro)
    = 10,000 * (1+19)
    = 200,000

    Therefore, HCM-PY = 200,000; would that be right to say? Also, if we need to retain the payroll result for 7 years. Where can I specify the retention period. Kindly suggest.

    Thank you very much.

    saplover

    (0) 
  29. Anish John

    Hi Susanne,

     

    Nice blog . Just a question. I did the sizing and the total SAPS came as 2000 . 500 for DB and 1500 for App. We have 8 App Servers .Do I need to assign 1500=(CPU) for each app or is it 1500/8 SAPS for each App

     

    Regards

    A

    (0) 
    1. Glen Canessa

      A,

      it is supposed to be 1500/8 for each App. But it is nonsense. A VM with 1 vCPU on x86_64 architecture is about 1000 SAPS.

      Why you have 8 App servres? Is this an existing system? If it is so, Quicksizer does not apply.

      Hope this help you.

      Glen

      (0) 
      1. Anish John

        Hi Glen,

         

        Ours is a live system and We are expecting more customer orders with a new project go live in some time .So if we size for the new expected value and add the hardware equivalent to existing system will it not be correct ?

         

        Regards

        A

        (0) 
        1. Glen Canessa

          A,

          your case is a Delta Sizing, so your approach is correct. But something is wrong: if you have 8 app servers then your current sizing could be over 20000 SAPs or so. If your new quicksizing result is 2000 SAPS (quicksizer minimum), then you are now extremely oversized, or your new sizing is incorrect.

          Regards,

          Glen

          (0) 
          1. Anish John

            Hi Glen,

             

            Thanks for that ..How does quick sizer knows what your system looks like and how much its sized ? Does it pull the data from system data section ?

             

            Regards

            A

            (0) 

Leave a Reply