IS INITIAL EXERCISE. This material is inspired by and partially based on the IBM s DB2 OLAP Server exercises produced by Doreen Fogle.

Transcription

1 DSV, KTH / SU PETIA WOHED IS5/2I1224 INTEGRATION SERVER IS INITIAL EXERCISE This material is inspired by and partially based on the IBM s DB2 OLAP Server exercises produced by Doreen Fogle. In this exercise, you will start by learning the basic functionality of DB2 s OLAP Integration Server. To do this you must first brows a completed OLAP model as well as a number of Metaoutlines based on it. An OLAP model is a dimensional model and it defines the logical structure for the warehouse. Based on this OLAP model, several metaoutlines may be defined. A metaoutline can be considered as a view definition, i.e., as a logical structure which is materialised during execution and physically stored in form of cubes (or DB2 OLAP Database in Fig 1). After that, you will create your own model and a couple of metaoutlines. Desktop OLAP Model Integration Server desktop Integration Server OLAP Metaoutline Server TCP/IP TCP/IP DB2 OLAP server Relational data source ODBC OLAP Metadata Catalog ODBC TCP/IP OLAP Command Interface DB2 OLAP database Fig 1. DB2 OLAP Integration Server Architecture PART 1 BROWSING A COMPLETED OLAP MODEL Start the DB2 OLAP Integration Server Desktop (in Windows, choose Start > Programs > Database Management Systems > IBM-Database-Systems > IBM DB2 OLAP Server 7.1 > DB2 OLAP Integration Server > Desktop. It may happen that for your account the path you need to go for opening the program is only a part of the path suggested here.). Connect to the server OLAP, and the OLAP metadata catalogue IDB for your account. E.g., in Fig 2 IDB049 is in this exercise the metadata catalogue for the account jdb049, which is my account. (NB! Do not mix up IDB catalogues with the JDB catalogues, which also exist but are not relevant for this exercise. Note also that you need to enter your password twice.)

2 Fig 2. The Login Window for the DB2 OLAP Integration Server Select the Existing tab to see the list of existing models, see Fig 3. Fig 3. IBM DB2 OLAP IS model and metaoutline meny Open The Beverage Company Model by selecting it and pressing the OPEN button. When prompted select TBCWHS as data source and enter user name and password to connect to 2

3 the source database, see Fig 4 (in Fig 1, the source database in the left-hand side is refereed to as Relational data source. All of you will select data from one and the same data source, i.e., TBCWHS). Fig 4. Login window to the data source The model is opened in a two frame window. The left frame displays the list of source tables, i.e. the tables in the source DB. For the moment it is only possible to build a dimensional model based on a single source DB (see the single DB symbol in the left part of Fig 1). This source DB is the result received from the staging area where a number of different data sources, data bases and/or flat files, are integrated. In this frame you can also see the columns of the source tables (by clicking on the plus symbol ahead a table name), the instances of a table (by right clicking on a table and selecting View Table Data menu), as well as the views defined on the tables (by selecting View > Show Views from the menu). Feel free to test these options. The right frame is the area where a dimensional model is displayed, and also the area where you can build and/or modify your own dimensional model. You drag source tables from the left frame to the right frame to create fact tables and dimensions. You can then perform different operations on the columns of a table, e.g., add, hide, delete, transform. We will come back to this functionality later on, when creating a new model. But before this we will browse through the example model you just opened. Select View>View All Columns to see the columns in each of the dimensions. (You can also do this by right clicking on a dimension and selecting View Columns menu.) You will receive the model shown in Fig 5. 3

4 Fig 5. The Beverage Company Model The join (i.e., the relation) of the fact table to a dimension table is shown by a line. To view the join information you can either hover over the join line, or you can right click on the line and select Properties. It is worth to note that IBM s terminology is slightly different from the terminology we so far have used in the course. One major difference is the distinction made between a dimension and a table. For instance the dimension Market consists of the tables Geography and Customer_Order (see Fig 5). (The terms Dimension table = table and Dimension branch = Dimension are also introduced in Integration Server s documentation, but for simplicity we will avoid using them.) The dimension properties (Fig 6) then differ from the table properties (Fig 7). We open these windows by right-clicking on a dimension name or a table name, correspondingly, and selecting Properties from the pop-up menu. Try to do this. The difference is that hierarchies are only defined for dimensions, whereas the column properties, and joins are matters for the tables. 4

5 Fig 6. Dimension Properties window Fig 7. Table Properties window Another difference is the explicit differentiation between the time dimension (called in our example Year) from the rest of the dimensions (note the clock symbol, contra the cube symbols ahead the dimension names). Furthermore, one more dimension category is introduced, namely an account dimension (which is called Measure in our example). This dimension is an exact copy of the fact table, and according to IBM s recommendations it must be introduced if there is more than a single measure (i.e., a single fact) in the fact table. (Note that ALL_FACTS which is the fact table in our example and the Measures dimension have exactly the same content). We can modify either of the tables and the other is always the same. Furthermore, a lot of symbols are used beside the columns. Their semantic is as follows: Symbol Meaning Description A string column A measures column in the fact table A numeric column in any dimension table other than the fact table A date/time column A hidden column, i.e., a column that will not be available for analysis use in the user interface. Keys have usually this setting. A drill-through column A primary key column A column on which a hierarchy filter is defined A column on which a column transaction is defined A column on which hierarchy transaction is defined A foreign key in the fact table A primary key in a dimension table, This property can be changed from the Table Properties window by pressing the Hide button, see Fig 7 This property can be changed from the Table Properties window by pressing the Drill-Through button, see Fig 7 5

6 which is used as a foreign key in the fact table An attribute column This property can be changed from the Table Properties window by pressing the Attribute button, see Fig 7 Now, after you have been introduced to some basic terminology and symbols, you are ready to brows through the table properties for the tables from the example. Please, follow the steps described below. During your browsing you can try to change some settings, but please do not save your changes, or restore the current settings at the end of your browsing. 1. Browse the Account table (by right-clicking on the table name and selecting Properties and then Columns button) Fig 8. the Table Properties window for the Account table In the displayed table: Name shows the name of the columns in the table Table Name shows the name of the table which we are browsing Column Name shows the source column on which the dimensional model column is defined Hidden (H ) shows whether a column is hidden or not Drill-Through (D..) shows whether a column is defined as a drill-through column or not Attribute (A ) NA shows whether a column is defined as an attribute or not means not applicable a) Notice that the key columns are all hidden b) Notice that the Sales column and the Unit Prise column are both based on the Charge source column. 6

7 2. Close the Table Properties window for the Account table (by selecting Cancel) and browse the Product table columns (by right-clicking on the table name and selecting Properties and then Columns button) a) Notice that the key column is hidden b) Notice that Caffeinated and Diet are defined as attributes. 3. Close the Table Properties window for the Product table and browse the Time table columns a) Notice that, also here, the key column is hidden. b) Notice that there are several columns derived from the Date source column, e.g., Day, Month, Quarter, Week and Year. This is shown by a + (red plus symbol) included into the date/time symbol. 4. Close the Table Properties window for the Time table and browse the Geography and the Customer_Orders tables one after another. View the column properties first (by as earlier selecting the Column tab). After that view the general properties for those tables (by selecting the General tab in the Table Properties window). The windows in Fig 9 and Fig 10 will be displayed for the two tables. a) Notice the Drill-Through columns for the Customer_Orders table. b) Notice the difference in the Level field in the Table Properties window General tab for the two tables. Fig 9. The Table Prop General tab for Geography table Fig 10. The Table Prop General tab for Customer_Orders table 5. For the sake of completeness brows also the fact table Now after have browsed through all the tables it is time to brows trough the dimensions. (Recall the difference in the IBM s terminology, we displayed earlier). 6. Brows the Time dimension, which is in our example called Year (by right-clicking on Year dimension and selecting Properties and then press the Hierarchies tab). You will get to the window in Fig 11. This is the place where the hierarchies are defined, edited and deleted. 7

8 Fig 11. The Dimension Properties window for the Year dimension 7. Select for instance the Year_Quarther_Month_Week_Day hierarchy and press Edit button. The window from Fig 12 will appear. This hierarchy contains five levels. Fig 12. The Year_Quarther_Month_Week_Day hierarchy in the edit hierarchy window 8. Select Time.Day and press the View Sample pushbutton to see a sample of the hierarchy members. (See Fig 13). 8

9 Fig 13. Sample for the Year_Quarther_Month_Week_Day hierarchy PART 2 BUILDING AN OLAP MODEL 1) Start the DB2 OLAP Integration Server Desctop (if it is not already started) Connect to the data source TBCWHS (see Fig 4). If the DB2 OLAP Integration Server Desktop is already open go to File > Open 2) Select the New tab 3) Select the OLAP Model tool (not the assistant 1 ) and press the Open pushbutton. 4) Select TBCWHS as the data source and provide your user name and password. Select OK. 5) Create the Fact table and the Account Dimension. Select the TBC.ALL_FACTS table and drag it to the right hand panel of the window 2. Drop the fact table somewhere in the middle of the Model panel. Select No when you are promted to create the time dimesnion from the fact table. (Selecting Yes would result in an automatic creation of the time table as a copy of the fact table. Adjusting then the time dimension would require more work than creating it manually from scratch, and we are therefore not interested in this option.) Select Yes to add an Account dimension. The accounts dimension will have all the same columns and members as the fact table. This will be the dimension that is tagged with the Accounts tag. (Unless the fact table does 1 The assistant is limited and does not support some important functionality, e.g. create a fact table from multiple source tables [p3-10, OLAP Integration Server Model User s Guide]. Therefore we will only use the standard user interface in this exercise. 2 The Integration Server automatically defines the first table drown to be the fact table. 9

10 not consist any facts, the existence of an Account dimension is required by the Integration Server, so it is equally well to create it now.) 6) Create the Time Dimension Drag the TBC.Time table to the model window placing it on empty space in the upper right corner of the model diagram. The dimesnion will be created but will not be named until it is joined to the fact table. Select the Join mode (Under Edit in the commando line Add Join Mode setting should be marked. If not, do it.). Draw a line from ALL_FACTS to the new dimension (click on ALL_FACTS name and draw a line holding the mouse button pressed down) Accept the default dimension name of Time (from the table name) and select a dimension type of Time. Press OK. Define the join as the Key column in the TIME table and the Time_key in the ALL_FACTS table. Select Add to define the join and then close the window. You will see the join appear in the diagram. (If in the underlying RDB schema, the primary and foreign keys were defined on these tables, the Integration Server should automatically create this relation.) 7) Create the Product Dimension Drag the TBC.PRODUCT table to the model window placing it on empty space in the upper left hand corner of the model. When defining the join, let the Dimension Type be Default. Define the join from the PRODUCT.key column to the product_key column in the ALL_FACTS table. 8) Create the Geography Dimension Drag the TBC.GEOGRAPHY table to the model window placing it on empty space in the left side of the model. When defining the join, let the Dimension Type be Default. Define the join from the GEOGRAPHY.key column to geography_key column in the ALL_FACTS table. 9) Verify that your model looks like the model in Fig

11 Fig ) Save the model by selecting File > Save As. Name the model Live TBC Model. 11) Modify the dimension names (right click on the dimension and select rename) Rename PRODUCT -> Product Rename GEOGRAPHY -> Market Rename TIME -> Year Rename Accounts -> Measures 12) Modify the Product dimension columns. (Right click on the PRODUCT table and select properties. Select Columns tab.) Hide the Key column (select the column and press the Hide button) Define CAFFEINATED and DIET as attributes (select both columns by the use of the shift key and select the Attribute button) Select OK. Note that the model icons are updated for the Product dimension. 13) Hide the Key column for the Time table, the Accounts Table (which contains a compound key), and the Geography table. Go to the corresponding Table Properties window, Columns tab. Select the Key column and press the Hide pushdown button. 11

12 14) Create the Product hierarchy. Right click on the Product dimension and select properties. Select the Hierarchy tab. Select Add button to define a hierarchy Name the hierarchy ProductGroup-ProductID Expand the Product dimension (on the left hand side) Define the top level of the hierarchy by either double-clicking on the PRODUCT_GROUPID or dragging and dropping the PRODUCT_- GROUPID to the hierarchy window. If you use the drag and drop method, you must drop it on the parent in this case the parent is the name of the hierarchy. Define the next level of the hierarchy to be PRODUCT_ID. View a sample of the hierarchy to see if this is the way you want your hierarchy to look. Select OK to add the hierarchy. Select OK to exit the dimension properties Save the model 15) Create a Date-hierarchies for the Year dimension, using the predefined in the Integration Server time hierarchies. Go to the Table Properties window for the Time table, Columns tab. Select the Date column and press the Date-Hierarchy pushdown button (see Fig 15) Select Year, Quarter, Month, Week, Day hierarchy and press OK to define this hierarchy and return to the Table Properties window. Fig 15. The Date Hierarchy window Creating a time-hierarchy in this way, will create new columns for each level in the hierarchy. Browse through the columns and pay attention to the columns Year, Quarter, Month, Week, and Day created during the last step. Select OK to return to the Model window. 12

13 16) Adjust the time hierarchy you just created. This is to ensure meaningful and unique names. Go to the Dimension Properties window for the Year dimension and select the Hierarchies tab. The Year_Quarther_Month_Week_Day hierarchy which appears in the window is the hierarchy which we created in the pervious step. Select this hierarchy and press the Edit button. (You will reach the Edit Hierarchy window in Fig 16.) Fig 16. The Edit Hierarchy window View a sample of this hierarchy by selecting TIME.Day and pressing View Sample. (see Fig 17) Fig 17. A sample for the time hierarchy Even if the instance we see is logically correct it is not precisely user friendly. Let improve its presentation. Close the Sample window and return to the Edit Hierarchy window. 13

14 Starting with the lowest level of the hierarchy define the following transformation for it: Select TIME.Day and press Transform pushdown button Select the Prefix/Suffix tab Select Parent Name as Prefix and print.day. in the Custom Prefix input field. Select the option None for Suffix. (see Fig 18) Select OK to define this transformation and return to the Edit Hierarchy window. Fig 18. The Edit Transformation window for Day Now, define the following transformation for the next lowest level, i.e., week. As Prefix select Parent Name, in the Custom Prefix field print.week., and finally select the None option for Suffix. Define the following transformation for Month. Select TIME.Month and press Transform pushdown button Select the Replace tab Enter 1 in the Search for field and enter Jan in the Replace with field. Select Match Whole Word and Replace All Occurrences options. Push the Add to List button Do the same for 2-12 replacing them with Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. See Fig 19. (If you do not specify Match the whole word you will end up with JanJan for month 11) 14

15 Select the Prefix/Suffix tab. Select None for Prefix Fig 19. Select Grandparent Name for Suffix and a. for Custom Suffix (i.e., your input should be a single dot.) Press OK to return to the Edit Hierarchy window. While TIME.Month is still selected press the Filter pushdown button. Select the Ordering tab in the Edit Filter TIME:Month window. The Sort Order should be Ascending, to guarantee than the months will appear in chronological order. Select OK to return to Edit Hierarchy window. Transform quarter so that the Prefix is None, Custom presifx is QTR and no suffix. Now, check that your hierarchy look like the hierarchy in Fig 20 (To do this select TIME.Day and press the View Sample button in the Edit Hierarchy window) Fig 20. The definition of this time hierarchy is now completed. Select File>Save to save the definition of the model. 15

16 17) Now, define a Year-Period-Week hierarchy for the Year dimension (based on Year, Period_Num, and Week_of_year attributes), so that a sample of it will look like the sample in Fig ) Define also a 2000-Quarter-Month-Week hierarchy for the Year dimension (based on Year, Quarter, name_of_month, and week_of_year attributes), so that a sample of it will look like the sample in Fig 22. Furthermore, to guarantee that this hierarchy only will select information for the year 2000, we need to define the following filter. Select TIME.Year in the Edit Hierarchy window for the 2000-Quarter- Month-Week hierarchy and press the Filter pushdown button. Select the tab (next to the Condition input field), select 2000 from the list and press OK. Be sure to select the Add button to add the filter to your conditions and press OK to define the filter and return to the Edit Hierarchy window. Fig 21. A sample Fig 22. A sample 19) Create a Region-State-City hierarchy for the Market dimension (based on Region, State and City attributes). Adjust the hierarchy so its lowest level will have the form city.state. 20) Create four hierarchies for each region in the US (West, East, Central and South). Each of those hierarchies should have region, state, and city. City should be transformed to city.state. A filter should be defined on each region to match the region name. 21) Create a hierarchy for Europé, i.e. Europé-Country-City (based on region, state, and city). The region filter should naturally be Europé. City should like earlier be transformed to the form city.state. 22) You should now have defined six hierarchies for the Market dimension, see Fig 23. Return to the OLAP Model window and save the model. 16

17 Fig 23. The hierarchies for the Market dimension Now, after have modified the dimensions it is time to modify the fact table. 23) Go to the Table Properties window, Columns tab, for the fact table. Rename the CHARGE column to Sales (by simply left hand side mouse clicking on it after it has first been marked.) Hide the key attributes (Geography_key, time_key, product_key), if you have not already done it. Hide also the TIMESTAMP column. Define a new column, based on the Sales column by performing the following steps. Select the Sales column Press the Add button Type Unit Price in the Name input field. Note that the new column will be based on the CHARGE Physical Column. (see Fig 24) Select OK. You are now prompted to define the transformation for the new column. Press the Transformation Rule tab button Choose the division operator Select the QUANTITY column from the list Check that the formula at the bottom of the window is the same as the one in the window in Fig 25. Select OK to complete the definition of the transformation Select OK to exit the properties of the table and to return to the OLAP Model window. Note that the Unit Price column you just crated appears now in the fact table, as well as in the Accounts table. 17

18 Fig 24. The Add New Column window Fig 25. The Column Properties window 24) Verify that your model looks like the model in Fig 26 and save it. Fig 26. The Model 18

19 PART 3 BROWSING A COMPLETED METAOUTLINE If it is not already started, start the DB2 OLAP Integration Server Desktop (Fig 2). Connect to the data source TBCWHS (Fig 4). Select the Existing tab to see the list of existing models. Expand the model named The Beverage Company Model. You will see all the metaoutlines defined for this model. Select the metaoutline named Traditional Beverage Co Metaoutline and select the Open button. When prompted, select TBCWHS for the source database and log in. The left pane of the window, the Model Pane, shows the Dimensions in the star-join schema. (Note that the Fact table is indirectly shown by the existence of the Measures dimension, which also may be an explanation for the existence of this special kind of dimension) If you expand the dimensions, you will see the columns of the dimensions and the hierarchies which have been defined. The right pane of the window, the Metaoutline Pane, shows the definition of the metaoutline. Expand the plus signs in the model and metaoutline window panes and you will receive the metaoutline in Fig 27. Fig 27. Traditional Beverage Co Metaoutline 19

20 The metaoutline definition contains: - Dimensions and type of dimension e.g., the dimension Measures is of the type Accounts - Dimension storage type i.e., Sparse (which is explicitly written in the Metaoutline window), and Dense (all dimensions that are not defined as Sparse. Dense is not explicitly written in the Metaoutline window.) - The member consolidation i.e., Addition, Subtraction, Do not consolidate - Member properties i.e., Label only, Dynamic calc, expense reporting - Alias definitions e.g., Alias: PRODUCT_GROUP - Formulas e.g., Margin % Sales - Members not sourced from the Model e.g., Profit, Margin, Total Expenses (in the Measures dimension) Diet Drinks - Dimensions not sourced from Model e.g., The Scenario dimension and its attributes Actual and Budget, was not sourced from the Model. - Attribute dimension and their associations to a dimension e.g., Caffeinated and Diet associated to the Product dimension - The deep of a hierarchy e.g., The red X on the TIME.Week and TIME.Day shows that the hierarchy built in this metaoutline will not contain those last two levels. If you want to see a sample of the metaoutline, right click on the metaoutline name (at the top of the right pane) and select Sample. The order of the dimensions in the metaoutline is significant for the DB2 OLAP Server performance. Therefore the order should be: Large dense dimensions Small dense dimensions Small sparse dimensions Large sparse dimensions Attribute dimensions A short description of the metaoutline dimensions from Fig 27 follows: The Time Dimension The Time dimension is tagged as time dimension type (the red text in the Type/Consolidation column). It is a dense dimension (which can be seen by right clicking on it and selecting properties and then Member info tab). It contains a five-level hierarchy: Year, Quarter, Month, Week, Day. The time dimension is dense which implies that it will be physically stored as a block. The lowest two levels of the Time dimension hierarchy have a cross through them which means that they will not be included in the final outline. This makes Month to the lowest level of detail in the outline. The remaining members of the hierarchy, above the Month, are defined as dynamic 20

21 calculation which means that they will be dynamically calculated at run-time. The Measure Dimension The next dimension is the Measures dimension, tagged as Accounts dimension type. It is also defined as label-only. The label only tag reflects the business requirement to have members which function only as headings or grouping members. Their value is in providing a placeholder for grouping like members together, not in their quantitative value [DB2 OLAP Server Theory and Practices: Redbooks]. The Measure dimension contains a number of members which are not source from the model: Profit, Margin, Total Expenses, Inventory, Ratios, Margin%, and Profit%. This is graphically shown by the rectangle preceding each of them. Furthermore, the consolidation properties shows the following connections: Profit = Margin Total Expenses Margin = Sales COGS Total Expenses = Marking + Payroll + Misc Margin and Total Expenses will be dynamically calculated at retrieval time. Moreover, two Ratios are defined in this dimension, namely: Margin% (defined as Margin%Sales, where % is the modulus operator) and Profit% (defined as Profit%Sales). Finally, the tag Expense Reporting is set for a number of members. Try to find out what it stands for. (Hint: Use the help function. Since, it is rather a product specific feature, it is almost impossible to guess it.) The Product Dimension The product dimension is a sparse dimension. The Diet and Caffeinated attribute dimension are associated with it and we will return to them later on. Two hierarchies are defined in this dimension: ProductGroupID-ProductID and Diet drinks ProductID. Diet drinks is manually defined in the metaoutline (indicated by the rectangle symbol). Right click on Product.PRODUCT_ID under Diet drinks and select Filter to view the filter. Take also a look at a sample for the product dimension (by right clicking on it selecting sample, and expanding the hierarchies). Note also the alias definition both for the PRODUCT_GROUPID (Alias: PRODUCT_GORUP) and for PRODUCT_ID (Alias: PRODUCT_NAME). An alias is defined through the corresponding Member Properties window Member Info tab (reached by right clicking on the corresponding member and selecting properties). The Market Dimension The Scenario Dimension The Attribute Dimension The Market dimension is a sparse dimension and it is defined as a three-level hierarchy: Region, State and City. View a sample of this dimension. The Scenario dimension is one more dimension defined manually (and not sourced from the model.) It is created to group together the Actual and Budget data and is therefore tagged as Label only. Finally, there are two attribute dimensions: Caffeinated and Diet. Both of them are Boolean. The source attributes, i.e., Product.CAFFEINATED and Product.DIET, are shown for the respective attribute dimension. 21

22 1) Browse through the rest of the metaoutlines defined on The Beverage Company Model i.e., Browse through the Holidays Metaoutline Browse through the Periods Metaoutline Browse through the TBC Europe Metaoutline 2) Try to identify the differences between the four metaoutlines. 3) Close all the metaoutlines by selecting Close under the File menu for each one. PART 4 CREATING AN OWN METAOUTLINE 1) Create a new metaoutline If it is not already started, start the DB2 OLAP Integration Server Desktop. If you have any Models or Metaoutlines open, close them. Select File>New from the commando line. Select the OLAP Metaoutline. In the entry list at the bottom at the window, choose Live TBC Model (the model you created during PART 2 of this exercise). Select the Open button to crate a new metaoutline. When prompted, connect to the source database (TBCWHS). An empty metaoutline appears (it is untitled until the metaoutline is saved). Save the empty metaoutline under the name The Traditional Live Metaoutline 2) Create the Time dimension Expand the Year dimension in the Model pane Drag the Year-Quarter-Month-Week-Day hierarchy from the Model Pane (the left pane in the window) to the Metaoutline Pane (the right pane in the window). This creates the entries in the time dimension. Rename the Year dimension in the Metaoutline to TIME (This can be done by right clicking on it, selecting properties, and retyping the name) When still on the TIME dimension Member Property window, select the Member Info tab and ensure that this dimension is defined as a Dense dimension (a setting in the lower part of the window). Set also the Data Storage setting (on the same window) to Dynamic Calc. Press OK to confirm the new settings and return to the Metaoutline window. Set TIME.Year, and TIME.Quarter to be Dynamic Calc, and set TIME.Month to be Store Data. This setting is done from the respective Member Properties window (reached by right clicking on the member and selecting Properties), Member Info tab. 22

23 Choose Month to be the lowest level of detail for this hierarchy. (Right click on TIME:Month and cross Build down to here option). Finally, overwrite the transformation of the TIME.Month in the Metaoutline by removing its suffix. (Right click on TIME.Month and select Transformation. Set the Suffix setting to None and remove the. from the Custom Suffix input field.) Save the Metaoutline (ignore the Warning message.) 3) Create the Measures dimension Drag the Measures dimension from the Model pane to the Metaoutline pane. Ensure that it is defined as type Accounts and Dense dimension. Set its Data Storage setting to be Label only. Create the Profit members (not based on the attributes from the star-join model). Select the Measures dimension in the right pane Select Edit>Add Member as Child.., from the commando line Type Profit as Member Name when required. Create the Margin member as a child of Profit. Create the Total Expenses as a child of Profit (or as a sibling to Margin) Create the Ratios as a sibling to Profit (or as a child to Measures) Create Margin% and Profit% as children to Ratios Create Inventory as a sibling to Ratios Check that the structure you have created so far (containing in the Measures dimension of only manually defined members, which is shown by the rectangle preceding them) corresponds to the one in Fig 27. If the order of your members differs from the one in the example, it can easily be changed by dragging and dropping the members into the desired position. Define now the Measures dimension members in the Metaoutline which are based on the Live-TBC Model, so that you will end up with a Measures dimension identical to the one in Fig 27. This is achieved by dragging and dropping the members from the Model to the desired position in the Metaoutline. Set the properties for the newly defined members as given below. (This is done from the corresponding Member Properties window, reached by right clicking on a member and selecting Properties). Member Consolidation Data Other Formula Storage Profit addition Dynamic Calc - - Margin addition Dynamic Calc - -..Sales addition Store Data - - COGS subtraction Store Data - - Total Expenses subtraction Dynamic Calc Expense Reporting - MARKETING addition Store Data Expense Reporting - 23

24 Member Consolidation Data Other Formula Storage PAYROLL addition Store Data Expense Reporting - MISC addition Store Data Expense Reporting - Ratios ignore Label only - - Margin% ignore Dynamic Calc Two Pass Calculation Margin%Sales Profit% ignore Dynamic Calc Two Pass Calculation Profit%Sales Inventory ignore Label only - - OPENING_ INVENTORY ignore Store Data Time Balance: First, Expense Reporting Typed in footnote 3 ADDITIONS ignore Store Data Expense Reporting - ENDING_ INVENTORY ignore Store Data Time Balance: Last, Expense Reporting - Verify that your metaoutline looks so far like The Traditional Beverage Co Metaoutline (if it is difficult to do this by using Fig 27, open both metaoutlines in the Integration Server Desktop and compare them) Save The Traditional Live Metaoutline (the Metaoutline you are creating right now). 4) Create the Product dimension Drag the ProductGroup-ProductID hierarchy from the Product dimension in the Model pane to the Metaoutline pane (dropping it on a blank area of the window below all other dimensions). You will of course first need to expand the Product dimension in the star-join schema in order to be able to see its hierarchies. Create the Diet Drinks hierarchy Create a new child to the Product dimension called Diet Drinks (for example by selecting Product and choosing Edit>Edit Member as Child) Expand the PRODUCT table in the Model window Drag the PRODUCT_ID from the Model pane and drop it on the Diet Drinks in the Metaoutline pane. If you get a message indicating that PRODUCT_ID is already member of this dimension (as a part of the PRODUCT_GROUPID-PRODUCT_ID hierarchy) answer YES, to add it anyway. Limit the instances of the Diet Drinks hierarchy to only include diet drinks - Right click on the PRODUCT_ID in the Diet Drinks hierarchy and select filter. - Pull down the column list and choose DIET - The operator should be in - Select the ellipsis (..) and choose Y for the value of the filter - Select Add to add the filter to the list - Select OK to complete the definition of the filter. 3 ENDIF; "ENDING_INVENTORY"="OPENING_INVENTORY"+ADDITIONS-Sales; 24

25 Define the Product dimension to be of the type Standard and to be a sparse dimension. It is done from the Dimension Properties window, Member Info tab. Select the Outline Build tab and choose the Add as shared members option to automatically tag the PRODUCT_ID, which appear in both hierarchies, as a shared member. Press OK. Define the consolidation properties for Diet Drinks to be ignore. Create aliases as given bellow, by selecting the desired Alias name from the pull down list in the corresponding Member Properties window, Member Info tab. PRODUCT_GROUPID Alias: PRODUCT_GROUP PRODUCT_ID Alias: PRODUCT_NAME. Save the metaoutline 5) Create the Market dimension Drag the Region-State-City hierarchy from the Market dimension in the Model pane to a blank area in the Metaoutline pane. Verify that the Market dimension in the metaoutline is a sparse dimension. Verify that all its members are defined as addition. Save the metaoutline 6) Create the Scenario dimension Select the Add members as siblings when Market dimension is selected, enter the dimension mane Scenario, and press OK. Set the properties for this dimension to be Sparse and Label Only. Create a Budget member and an Actual member, as children to Scenario and both with the consolidating property Ignore. Select the Default Load Member setting for Actual (which you reach by right clicking on Actual). Save the metaoutline 7) Create the attribute dimensions: Caffeinated and Diet Expand the Attributes within the Product dimension in the Model pane (NB! do not mix the Attributes in the Product dimension with the PRODUCT table) Drag PRODUCT.COFFEINATED from the Model pane to some free space in the Metaoutline pane. Do the same for the PRODUCT.DIET attribute. Change the Attribute dimension type to Boolean (for both Attribute dimensions). This is done from the Attribute Dimension Properties window for the respective Attribute dimension which is reached by right clicking on the Attribute dimension and selecting Properties. (Press OK in the warning window to confirm the type change.) 25

26 Note that the Attributes dimensions were automatically associated with the Product dimension since these attributes were defined in the Product dimension in the star-join schema. Associate the members of the Attribute dimensions with the members of the Product dimension. Right click on the PRODUCT.COFFEINATED member of the Attribute dimension COFFEINATED and select Properties. Select the By Metaoutline Member option under Association (under the General tab) Choose PRODUCT.PRODUCT_GROUPID -> PRODUCT.PRODUCT_ID from the drill down list and press OK. Associate PRODUCT.DIET member of the Attribute dimension DIET to PRODUCT.PRODUCT_GROUPID -> PRODUCT.PRODUCT_ID Define the Attribute member names Select Edit from the commando line and choose Attribute Member Names On the Member Name Format tab, choose Parent option for Value, the _underscore option for Separator, and the Prefix option under Prefix/Suffix. Under the Boolean and Date tab, change True with Y and False with N (because these are the values present in the source data.) Press OK to confirm the new settings. Verify that your Metaoutline looks like The Traditional Beverage Co Metaoutline Save your Metaoutline PART 5 MATERIALISING A METAOUTLINE Now, after you have created a metaoutline you can materialise it (i.e. execute it and physically store the results in a cub), see the right most part of Fig 1. However one last setting you need to do before going on with this is to set the TIME.Month data store property to be STORE DATA (which is done from TIME.Month property window, Member Info tab). Save your metaoutline and follow the steps below: 1) Go to Outline>Member and Data Load.. under the commando line. 2) In the appeared window, fill in your user name under Application Name and Trad under the Database Name. Select Use Default Calc Script option (The second time you are doing this you will also need to select the option: Delete all members first, in order to overwrite the already existing data with the new one. But, do not bother about this now, we are not going to do this in this exercise.) See Fig

27 Fig 28. 3) Select Next 4) In the appeared window select the option for Now for Loading Essbase (see Fig 29) and press Finish. Fig 29. 5) When the data load is ready you will receive a confirmation message: Successfully loaded OLAP:jdb049:Trad. Press OK to confirm this message, then Close the Data and Member Load window. 6) When you have finished with your work do not forget to Exit Hyperion Integration Server Desktop. 27