QuickSizer BI

Question

hello Gurus
I want to do the sizing with the quick sizer from marketplace, but i don t have clearly the terms, please send me info about sizing in BI, the help indicates:
<b>Business Intelligence
SAP NetWeaver Business Intelligence      Find information about SAP NetWeaver Business Intelligence at  the Service Marketplace -> Business Intelligence, for example information about Performance Tuning.
User Groups Business Planning
Planning 1,
Planning 2,
Planning 3      Definition
The general idea is to define user groups which are determined by the number and size of data records they work with and the types of planning functions they execute. If you are not sure exactly how many data are involved, you can take the proposed values, which are  based on internal measurements and customer feedback.
Specifics for User Groups Business Planning
Users
      Estimate the highest number of active users per hour. Opposed to other sizing approaches in the Quick Sizer you can arbitrarily include users in a specific group. Normally the user groups reflect the fact that you have power, medium and occasional users (example at "Planning steps per user").
Planning steps per user
      Estimate the peak number of planning steps per user and hour.
      Example for "Users" and "Planning steps per user"
      A user carries out six planning functions, the first three work on the same set of data (5,000 records), the other ones each work on separate set of 600 records. If this sequence is carried out every 20 minutes, we were faced with 18 planning steps per hour and user.
Average number of data records per planning step
      A planning step always contains exactly one planning function, for example a formula function. If that planning 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
          o 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.
          o 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.
Maximum data per planning step
      Estimate the maximum number of data records manipulated by one single planning step.
      Example
      As mentioned above the planning functions work through different sets of data. The maximum number is 5,000 per hour and user.
Maximum data per user
      Estimate the maximum number of data records a user holds in memory simultaneously. This is needed to estimate the memory consumption of a 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
BI-INFO,
BI-BUSIN.,
BI EXPERT      Definition
In NetWeaver BI, we distinguish roughly between user types according to their frequency of activity and the reporting they will normally do.
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.
User Groups Reporting & Analysis
     Definition
Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
For sizing purposes we distinguish between three query types which are defined by the load they create in the system.
Report Viewing: Predefined, static, reports using optimal aggregates
OLAP Analysis: Slicing and dicing, navigating in reports, using various aggregates
Data Exploration: Data mining, that is ad-hoc reports with unpredictable navigation paths, access of detail data, full table scans
Any user can do any type of query. However, experience shows a certain activity pattern, as you can see in the table below.
Query Type       Report Viewing      OLAP Analysis      Data Exploration      Total Percent
Information Consumer      80%      20%      0%      100%
Business User      50%      50%      0%      100%
BI Expert       0%      0%      100%      100%
Data Upload
UPLOAD      Definition
In this section you can specify how many records you need to upload within your peak time interval.
InfoCube
INFOCUBE
IC-APO
IC-CO
IC-CRM
IC-FI
IC-HR
IC-MM
IC-PP
IC-PS
IC-SD
IC-SEM
     Definition
The central objects upon which reports and analyses in NetWeaver BI are based, are called InfoCubes. An InfoCube describes (from a reporting point of view) a self-contained dataset, for example, of a business-orientated area.
An InfoCube has a particular type:
BasicCube which is a collection of relational tables arranged according to the star schema: A large fact table in the center, surrounded by several dimension tables.
MultiCube which is based on the basic cube. It combines data from several BasicCubes/RemoteCubes, and brings it together into one context. The MultiCube itself does not contain any data; its data comes exclusively from the BasicCubes it is based on.
RemoteCube to carry out reporting using data in external systems without having to physically store transaction 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
Insurance           0IS_CS_C1      9      8      226
Inventory Management           0COPC_C04      7      6      172
Investment Management           0IMFA_C02      7      3      121
Marketing           0CRM_MC05      12      43      851
Marketplace           0MA_OP_C1      9      13      311
Media Enterprises           0MEMAMC04      11      16      382
Mobile Sales      MSA      0MSA_C05      8      6      182
Oil & Gas      Oil & Gas      0OI_SSC01      9      16      362
Personnel Management           0PACM_C01      10      17      389
Point of sale      POS      0RT_C06      9      33      651
Retail - Logistics           0RT_C41      7      183      3181
Sales and Distribution Analyses           0CSAL_C09      12      29      613
Service           0CRM_PRI      14      47      939
Strategic Enterprise Management      SEM      0SEMPA_C2      13      68      1286
Strategic Enterprise Management           0SEM_MC01      6      9      213
Traffic Analysis           0MA_C02      15      21      507
Treasury      TR      0TRCM_MC1      6      2      94
Utility Company           0UCSA_C01      12      20      460
Specifics for InfoCubes
Dimension
      A grouping of those evaluation groups (characteristics) that belong together, as regards contents, in one generic term. With the definition of an InfoCube, characteristics are summarized into dimensions in order to store them in a table of the star schema (dimension table). An InfoCube has no more than 16 dimensions, of which three are standard (package, time, unit) and included in the sizing by default. You can therefore enter only 13 dimensions at most.
Key figures
      Values or quantities, such as sales revenue, fixed costs, sales quantity, or number of employees.
      In addition to the key figures saved on the database, you have the option of defining derived (calculated) key figures in the query definition in the Business Explorer. Such key figures are calculated using a formula from the key figures of the InfoCube.
      Examples of derived key figures are "sales revenue per employee" (sales revenue divided by number of employees), "variance as a percentage", or "contribution margin".
Initial load & periodic load
      Initial load: Specify the estimated number of records which you plan to load into the cube initially.
      Periodical load: Specify the estimated number of records which are loaded in your periodical upload process. You should take into account that you upload data volume grows with time.
Number of periods
      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.
DataStore Object
DS OBJECT      Definition
A DataStore Object serves to store consolidated and debugged transaction data at a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query.
A DataStore contains a key (for example, document number/item) as well as data fields that can also contain character fields (for example, order status, customer) as key figures. The data of a DataStore Object can be updated with a delta update into InfoCubes and/or other DataStore Objects in the same system or across systems.
In contrast to multi-dimensional data storage with InfoCubes, the data in DataStore Objects is stored in transparent, flat database tables.</b>

Answer 1

Hi,
BPS ;- Here you need to decide if you r really going to use this...If your are not going to use Business planning and simulation then skip this part.
In case of no. of users ....Take information from your client that how many no. of users will be there and then distribute these user as per gide lines given by sap. ( In quick sizer this help is available on market place )
Then decide which modules u r going to take in BW.
( In our case BW implementation is limited to SD, FI and CO. )
After this talk to your functional people and decided how many records will be generated per day for each module and for each functionality.
This is required to decide disk space.
Then list down all the infocubes and ods which are installed count dim. and key fig. for each cube. For ods count key fields and data fields.
Hope this helps....
Regards,
Mahendra