Lab 2: BSO Cube

1 Overview
This lab steps through the process of building an Essbase BSO cube using Essbase Studio. The Studio is designed to provide a single modeling interface for the creation of analytic applications. It simplifies cube construction by delivering a single environment for performing tasks related to data modeling, cube designing, and analytic application construction. With a wizard-driven user interface, Essbase Studio supports modeling of the various data source types from which Essbase applications are typically built as well as exposing a number of new data sources. A single common metadata repository, or catalog, captures all metadata related to all Essbase applications built in the enterprise and allows the reuse of metadata at the lowest level of granularity. The catalog makes Essbase Studio inherently aware of the common metadata that is shared across the various applications enterprise wide. Essbase Studio supports several drill-through options: relational databases, OBIEE, BI+ reports, URLs, Essbase applications (drill across), custom SQL, and Java methods. Essbase Studio also supports lineage tracking through a rich graphical view of metadata relationships, allowing users to follow application lineages to their metadata components and through to the data sources from which they were sourced.

2 Start Servers
There are five services that will need to be started before you can complete the lab: • • • • • Shared Services Essbase Essbase Administration Services (EAS) Analytic Provider Services (APS) Essbase Studio Server

1. Ensure that your VM instance is running and you are logged in as: Username: oracle Password: oracle

In the Linux VM, you will need open multiple terminal sessions to start up the Hyperion services. You can open a terminal window in one of three ways: 1. Click on the terminal window icon on the toolbar at the top of the screen.

1 Lab 2: BSO Cube

2. Right-click anywhere on the desktop and select “Open Terminal” from the top of the list.

3. Go the Applications menu, select System Tools and then Terminal from the list of programs.

The resulting Terminal Window will appear as below:

2 Lab 2: BSO Cube

As a convenience, a text file on the Linux Desktop called “Start Stop Services.txt” can be used to copy/paste the directories and scripts for the subsequent steps. To access the file, double-click on the file or right-click and select “Open with Text Editor”. If it asks whether you want to run or display the file, choose “Display”.

To copy/paste text, highlight the text, copy the text by pressing “CTRL+C” or selecting “Edit | Copy”. In a terminal window, press “SHIFT+CTRL+V” or select “Edit | Paste” to paste the text in the terminal window.

3 Lab 2: BSO Cube

sh <Enter> Shared Services must be started before any of the other services. 3. Start Shared Services. you will know that Essbase has started properly. For this step. DO NOT CLOSE this window. Once you see the line “Waiting for Client Requests…”./startSharedServices9. 4 Lab 2: BSO Cube .txt” file or type in the terminal window: cd /software/hyperion/products/Essbase/EssbaseServer/bin .sh <Enter> This starts up the Essbase server in the foreground.2. Copy the following two lines from the “Start Stop Services. Wait approximately 30 seconds before continuing to the next step. Minimize this window (DO NOT CLOSE). Copy the following two lines from the “Start Stop Services. Start Essbase.txt” file or type in the terminal window: cd /software/hyperion/deployments/Tomcat5/bin/ . so the prompt will not be returned./startEssbase. you can either open a new terminal window or use the previous one since Shared Services is running in the background and returned the prompt.

txt” file or type: cd /software/hyperion/deployments/Tomcat5/bin/ . You can use this terminal for the next step or minimize the window (DO NOT CLOSE). Start Essbase Studio. Open another terminal window and copy the following two lines from the “Start Stop Services.4.txt” file or type in the terminal window: cd /software/hyperion/products/Essbase/EssbaseStudio/Server ./startServer. Copy the following two lines from the “Start Stop Services.txt” file or type in the terminal window: cd /software/hyperion/deployments/Tomcat5/bin/ .sh <Enter> This starts up the Studio server in the background. 5. Start APS.sh <Enter> This starts up the APS server in the background. You have completed all the start ups for this lab.sh <Enter> This starts up the EAS server in the background. Start EAS. Open a new terminal window or use the one from the previous step since EAS is running in the background and returned the prompt. Open a new terminal window or use the one from the previous step since APS is running in the background and returned the prompt. 5 Lab 2: BSO Cube . You can use this terminal for the next step or minimize the window (DO NOT CLOSE)./starteas. Copy the following two lines from the “Start Stop Services./startaps. 6. DO NOT CLOSE this window.

make sure that the Data Sources tab is selected in the right panel. select or type “ptsessbase” for the Server. To begin. The left panel in Studio has the Metadata Navigator. Click “Log In” 3. Folders can be created under the root directory to manage and organize metadata elements. 2. it must first be saved as a CSV file. 1. which provides a tree view of your metadata repository. Open the Essbase Studio Console by selecting the following shortcut: Start | Programs | Oracle EPM System | Essbase | Essbase Studio | Essbase Studio Console. At the log in screen. “admin” for the User and “password” for the Password.3 Adding Data Sources In this release of Studio the following can be sources for Studio (a JDBC driver is required for each source): • • • • • • • Oracle database Oracle Business Intelligence Enterprise Edition Enterprise Performance Management Architect SQL Server DB2 Teradata Delimited text files Note: Excel cannot be used directly as a source. The right panel contains the data sources and minischemas that you will need for building your cubes. Right-click on “Data Sources” and select “New | Data Source…”. 6 Lab 2: BSO Cube .

Click “OK”. Provide the following information in the Define Connection screen: Click on “Test Connection”. click “Next” in the Define Connection screen. We will first add an Oracle schema as a data source.4. If the connection was successful. 7 Lab 2: BSO Cube .

Click “Finish”. 8 Lab 2: BSO Cube . Right-click on a table and select “View Sample Data”. Click “OK” when completed. We will be creating the minischemas and hierarchies later. Expand on TBC and on one of the tables to view the fields.In the Define Tables screen. select all tables.

5. 9 Lab 2: BSO Cube . Type “Text” as the Connection Name and select “Text File” for the Data Source Type. Click on the “X” to close the table. Click “Browse” next to Location. Repeat adding a new data source by selecting “File | New | Data Source…”.The first 200 rows of the table will appear in the middle panel. Ensure that “Comma” is selected as the Delimiter.

The root directory is set as <HYPERION_HOME>\products\Essbase\EssbaseStudio\Server\datafiles by default.Select “tbc_samples” and click “OK”. The tbc_samples directory was placed in there during the installation.properties file found in the <HYPERION_HOME>\products\Essbase\ EssbaseStudio\Server directory: server. 10 Lab 2: BSO Cube . Click “OK” when successful.dir=<directory path> Click “Next” to the Model Files screen. Click on the “Select all” button and click “Finish”. You can change the location of the root directory by adding the following line to the server.datafile.

There is no requirement to have a fact table for hierarchy creation for Essbase deployment.Expand Text and right-click on one of the files to view its content. 1. 11 Lab 2: BSO Cube . right-click on “Minischemas” and select “New | Minischema…”. The process for modeling a relational source captures the join relationships between tables. In the Minischemas tab on the right panel. This is a preliminary step in data modeling using Essbase Studio to create analytic applications. Other important points regarding minischemas are as follows: • • • Text files can be added to minischemas for the purpose of logical grouping only. Minischemas are first-class objects used to create logical groupings of tables from various data sources in order to construct a subject area to work with. Essbase Studio minischemas present a logical representation of the relational schema and provide the mappings to allow Studio to traverse the data source. They cannot be joined to other text files or relational tables.Minischemas The process of modeling data sources in Studio varies depending on the type of source you are modeling. The modeling process for flat files is taken care of in the wizard used to map the data source. 4 Modeling Data Sources . you can leverage columns out of a relational source for building the model without a minischema and use a flat file to load the data. Studio supports the use of multiple fact tables in the schema. both can provide fact data to the model. To that end.

Click “Finish”. type “TBC_Schema” for the Minischema Name.2. Select “TBC” from the Connections drop down. Click “Next”. Select all the tables to the schema. 12 Lab 2: BSO Cube . At the Create Minischema screen.

The tables should be joined based on the joins that were created in the physical schema. 13 Lab 2: BSO Cube . Locate the PRODUCTDIM table (may be out of view below the other tables) and move it underneath the FAMILY table. The minischema for TBC should appear in the middle panel. go to the next step. If no joins were created.3. The only required join that was not created in the physical schema is the join from the PRODUCT to the PRODUCTDIM table. Click on the “SKU” field in the PRODUCT table and drag a join line to the “SKU” field in the PRODUCTDIM table.

Inspection will yield all the matching field names between tables. Click “OK”. If no joins appeared in the minischema. select only the ones identified below. right-click on any whitespace in the work area and select “Add Joins By Inspection…”. Since we do not need all those joins.4. 14 Lab 2: BSO Cube .

select “CHILD”. . select “MEASURES”. Right-click on the Measures table and select “Add Join” In the second Table drop down. starting and ending with the joining fields. In the first column. you can join tables manually by dragging join lines across the tables. 5. Click “OK”. 15 Lab 2: BSO Cube . select “PARENT” and in the second column. You can also arrange the tables and joins by right-clicking on any whitespace in the minischema viewer and selecting “Lay out schema”.Alternatively.

or both is completely up to you. It simply makes the process easier. For example. you can create a folder in the Metadata Navigator that contains the raw columns and files you want to use to create hierarchies. Save (“File | Save”) and close (“X”) the minischema. it is recommended that you create folders to organize elements prior to creating hierarchies. You can create as many folders and sub-folders as desired to organize your deployment. The Studio allows you to organize elements into logical groups that can be used to create other elements. However. Your minischema should now look similar to the one below. 5 Modeling Data Sources . The resulting hierarchies can then be stored in a folder of their own.Organizing Metadata Elements A metadata element in the studio is one of the following: • • • • • Relational column (based on the source or customer created) Field from a text file Hierarchy Drill-through report Cube schema In short. Whether you separate by element type. 16 Lab 2: BSO Cube . 6. model. The following exercise serves as an example of how metadata can be arranged in Studio and is by no means mandatory or definitive. Personal preferences and differences from project to project will also determine how metadata is organized.This creates a recursive join on the table allowing for parent-child queries. a metadata element is anything that you can use to create an analytical model.

3. Create the following folders under TBC: Dimension Elements. Hierarchies. 17 Lab 2: BSO Cube . Type “TBC” for the Name. Cube Schemas and Drill-through Reports. First. Click “OK”. Right-click the “Root” folder in the Metadata Navigator (left panel) and select “New | Folder”.1. 2. create folders for the metadata elements.

Right-click on the Dimension Elements folder and select “Paste”. They are then used to form levels within hierarchies or as distinct members. Copy STATE by right-clicking on it and selecting “Copy”. Once the hierarchy dialog is open you drag and drop the sources in for each level either from the data sources panel or the metadata navigator. hierarchies. Creating hierarchies in the Studio is a matter of drag and drop. Start by expanding the TBC data source in the Data Sources tab on the right. generations. and alternate hierarchies all in the same fashion. It is also important to note that you can cross data sources and data source types during the hierarchy creation process. They can be columns from a data source or they can be derived (logical). parents or children in order to build hierarchies. At any point during the process you can perform a full preview of the resulting hierarchy. You initiate the hierarchy creation wizard via the right-click menu or through the menu system. attributes. You can create custom members. This is possible with or without the presence of a fact table. Expand the Market table and drag the “STATE” field to the “Dimension Elements” folder in the Metadata Navigator. 1. The term “level” is used in a very generic sense in that there is no requirement to understand the concepts of levels. 18 Lab 2: BSO Cube .6 Modeling Data Sources – Dimension Elements and Hierarchies Dimension Elements make up the hierarchies.

REGION’. Expand TBC and REGION. Click in the Filter box. Edit EAST_STATE by double-clicking or right-clicking and selecting “Edit…”. Double-click on the “REGION” field or click on the icon next to the Filter box so that the following string appears in the Filter box: connection:\’TBC’::’TBC. 19 Lab 2: BSO Cube . Click “OK”.Rename STATE_copy to “EAST_STATE”.REGION’ Type: ==“East” at the end of the string.

Drag the following columns from the TBC data source to the Dimension Elements folder: MEASURES.PKGTYPE REGION. 2.FAMILY PRODUCT.REGION REGION. We will do other examples of this later in this lab. Logical columns such as this can be created by filtering existing columns or by using a variety of Date.TRANSDATE SCENARIO.DIRECTOR SALES.Right-click on “EAST_STATE” and select “View Sample Data”.OUNCES PRODUCT.SKU PRODUCT.CHILD MEASURES. String and Numeric functions.CAFFEINATED PRODUCT.SCENARIO 20 Lab 2: BSO Cube .PARENT PRODUCTDIM.

Adding a sort order. Expand TBC > PRODUCTDIM and select “FAMILY”. This will order the Product Families in ascending order in the Do the same for SKU.3. Double-click on “FAMILY” in the Dimension Elements folder. Expand TBC > PRODUCT and select “SKU”. Click “OK”. 21 Lab 2: BSO Cube . icon under Sort Order. Click on the outline.

Highlight $$DateOperand$$. we can use the time wizard. For this exercise. Select the “Functions” tab and expand Date. ‘year’($$DateOperand$$) should appear in the Caption Binding box. 22 Lab 2: BSO Cube . Double-click on the “year” function. Type “Year” for the name.4. Create custom dimension elements. For the Time dimension. we will create the Time dimension elements using Date functions in order to build a standard hierarchy. Right-click on Dimension Elements and select “New | Dimension Element”. or we can build a standard hierarchy and tag it as “Time” during the cube deployment process.

View the data for the Year field. 23 Lab 2: BSO Cube . This will order the years in ascending order in the outline. Click “OK”. with “TRANSDATE” highlighted.'TRANSDATE' ). Also. The Caption Binding box should now read: 'year'( connection : \'TBC'::'TBC.SALES'.Go to the “Source” tab and expand TBC | SALES. click on the icon under Sort Order. Double-click “TRANSDATE”.

'TRANSDATE' ) With “TRANSDATE” highlighted. The formula in Caption Binding should read: 'quarterAsString'( connection : \'TBC'::'TBC. The formula in Caption Binding should read: 'monthShortName'( connection : \'TBC'::'TBC. Click “OK” and view the data. click on the in the outline. icon under Sort Order.'TRANSDATE' ) || "-" || 'year'( connection : \'TBC'::'TBC.SALES'. This will order the months in ascending order 24 Lab 2: BSO Cube .'TRANSDATE' ) With “TRANSDATE” highlighted. Create a dimension element called “Month” using a similar method. Click “OK” and view the data.'TRANSDATE' ) || "-" || 'year'( connection : \'TBC'::'TBC.SALES'.Create a dimension element called “Quarter” using the quarterAsString and year functions and concatenating a “-“ between the two functions. click on the icon under Sort Order. This will order the quarters in ascending order in the outline.SALES'.SALES'.

click on the icon to move SKU below FAMILY.5. In that case. Expand the Dimension Elements folder and drag the “FAMILY” field to the Hierarchy data area. Drag the SKU field on top of the FAMILY field so that it is a level below FAMILY. 25 Lab 2: BSO Cube . SKU will be at the same level. Right-click on the Hierarchies folder and select “New | Hierarchy”. If you drag it to the line below FAMILY.

Click “OK”. 26 Lab 2: BSO Cube . Click “Save”.Add 3 other hierarchies below the first one: Name the hierarchy “Product”. Click “Close” to close the Product hierarchy. Click the “Preview” button to see how the hierarchies would look.

Create the Market hierarchy in a similar fashion. 7. Create the Measures and Scenario hierarchies 27 Lab 2: BSO Cube .6.

8.Cube Schemas Cube schemas are simply collections of hierarchies that make up the dimensions in a cube. you can select a preexisting hierarchy and tag it as “measures” in the cube deployment process. The generic process of modeling and the specific process of setting Essbase properties are intentionally separated in the Studio. The current incarnation of the deployment wizard has four fundamental steps: 1. Click “Close”. You specify which Essbase server (mapped as a connection when creating data sources) and execute the deployment. These properties might include consolidation operators. Click “OK”. Click “Save”. Set deployment options. Validate the model prior to deployment. 7 Modeling Data Sources . 3. The Studio will perform the same syntax and logic checks done in Integration Services and the Data Prep Editor to ensure that the deployed model is valid. Set Essbase properties for a dimension. dimension level. 4. During the cube schema creation process you select which hierarchies you would like to include in each dimension. or specific member (in the case of measures). Alternately. data storage. You also have the option of hand creating a custom Measures dimension. Click “Preview” to see how the hierarchy would look like. This allows for possible future projects that would allow the Studio to model independent of destination and only in the deployment wizard would a user have to call out destination specific properties. etc. Name it “Time”. Additionally. data only or both) you want the model deployed. or XOLAP model for example. you can choose when and how (metadata only. You select whether you want an ASO. Make Year the top of the hierarchy then Quarter and then Month at the bottom. Create the time hierarchy. 28 Lab 2: BSO Cube . BSO. Upon execution the Studio logs into the specified target server and creates the application and database as specified. formulae. During the cube schema creation process you can preview full versions of each dimension or all dimensions at once as they would look in an outline. 2.

Drag “SALES. In Data Sources panel expand TBC and Sales. 29 Lab 2: BSO Cube . Right-click on the Cube Schemas folder in the Metadata Navigator and select “New | Cube Schema”.1. 2.AMOUNT” to the Dimensional Elements folder in the Metadata Navigator.

b.3. Click the “Preview Hierarchies” button and review the dimensions. c. and click “Next” in the Cube Schema Wizard. e. Click “Finish”. d. Measures Time Scenario Product Market Expand the Dimension Elements folder and add “AMOUNT” to the Measures area. Expand the Hierarchies folder and add the following to the Hierarchies area (keep in this order): a. On the Cube Schema Options screen. select “Measures”. On the Accounts Dimension drop down list. 30 Lab 2: BSO Cube . Name the cube schema “TBC1”. check the “Create Essbase Model” box. Click “OK” to close the Preview dialog.

The next step towards deploying an application is to set all the Essbase properties in the Essbase Model. Set Data Storage to “Label Only”. In those cases. This is because there is a separate Measures dimension table that contains the Measures hierarchy. Right-click any whitespace in the model and select “Essbase Properties…”. Note: The Measures hierarchy was built as a standard hierarchy as opposed to being built as a “Measure Hierarchy”. 4. 31 Lab 2: BSO Cube . a fact (“AMOUNT”) was designated as the “Measure” in the first step of the Cube Schema Wizard and an “Accounts Dimension” (“Measures” hierarchy) was selected in the second step.The TBC1 Model will appear in the middle panel. On the Model Properties screen. Click “Apply”. select Measures and go to the “Info” tab.

Expand Measures | Parent under TBC1Model and select “CHILD”. Set Skip to “External Source” and select “SKIP” in the drop down. Click “Apply”. Go to the “Account Info” tab and set Time Balance to “External Source” and select “TIMEBALANCE” in the drop down. Click “Apply”. Set Variance Reporting to “External Source” and select “VARIANCEREPORTING” in the drop down. Go to the “Info” tab and set Consolidation to “External Source” and select “CONSOLIDATION” in the drop down. Set Data Storage to “External Source” and select “STORAGE” in the drop down. Set Two Pass Calculation to “External Source” and select “TWOPASSCALC” in the drop down. 32 Lab 2: BSO Cube .

Go to the “Formula” tab and set Formula to “External Source” and select “FORMULA” in the drop down. Click “Apply”.

Select “Time” under TBC1Model. Go to the “Info” tab and set Dimension Type to “Time”, Dimension Storage to “Dense” and Data Storage to “Dynamic Calc”. Click the “Dynamic series…”button next to Time.

33 Lab 2: BSO Cube

Check the “H-T-D” box and set its Generation to “1”. Check the “Q-T-D” box and set its Generation to “3”. Check the “Y-T-D” box and set its Generation to “2”. Click “OK” to close the Dynamic Time Series dialog.

Select “Year” under Time. Set Data Storage to “Dynamic Calc”.

34 Lab 2: BSO Cube

Select “Quarter” under Year. Set Data Storage to “Dynamic Calc”. Click “Apply”.

Select “Scenario” under TBC1Model. Go to the “Info” tab and set Data Storage to “Label Only”. Click “Apply”.

35 Lab 2: BSO Cube

Expand the Product dimension under TBC1Model and select “OUNCES”. In the General tab, check the “Essbase Attribute for SKU” box. Change the Attribute Type to “Numeric”. Click “Apply”.

Select “PKGTYPE”. In the General tab, check the “Essbase Attribute for SKU” box. Verify the Attribute Type is set to “String”. Click “Apply”.

Select “CAFFEINATED”. In the General tab, check the “Essbase Attribute for SKU” box. Change the Attribute Type to “Boolean”. Click “Apply”.

36 Lab 2: BSO Cube

Expand the Market dimension under TBC1Model and select “DIRECTOR”. In the General tab, check the “Essbase Attribute for STATE” box. Verify the Attribute Type is set to “String”. Click “Apply”.

5. Run the Validation by clicking on the

icon.

If you receive a message stating that the selection of External source for data storage for the column “CHILD” could cause errors during the dimension build, ignore this message. Click “Close”.

. Close the Essbase Properties dialog.

37 Lab 2: BSO Cube

Save TBC1Model (if grayed out. 38 Lab 2: BSO Cube . Select “Tools | Alias Set Manager”.6. Click on the icon under Alias Sets to add a new alias table. Name the table “TBCAlias”. Click on the icon under Bindings to create a binding between a member column and an alias column. then it is already saved). Aliases are set a little differently in Studio. 7. Instead of specifying aliases at each level of the hierarchy. alias tables are built in the Alias Set Manager and then assigned to a Model.

39 Lab 2: BSO Cube . Under Binding Expression. expand TBC | Dimension Elements and click on “SKU”.Under Binding Source. expand PRODUCTDIM and double-click “SKU_ALIAS”. Click “OK”.

Repeat with “FAMILY” / “PRODUCTDIM | FAMILY_ALIAS” and “CHILD” / “MEASURES | MEASURES_ALIAS”. TBCAlias should now have 3 rows. 40 Lab 2: BSO Cube . Click “OK”.

If you closed TBC1Model. Right-click in the work area and select “Essbase Properties”. Click on “TBC1Model” and select the “Alias” tab. Ignore the warning if identical to the previous and click “Close”. right-click on it and select “Edit”. Run a validation. Click “Apply”. Select “TBCAlias” under Available Tables and click the right arrow to add to Selected Tables. 41 Lab 2: BSO Cube .

Several options for drill back targets. The following improvements have been added to the drill-through reporting capabilities: • Can drill back to sources not related to cube definition. drill-through reports are specific to dimensional intersections not to a deployed model. right-click the Drill Through Reports folder and select “New | Drill-through Report”.1 release. Drill through supported for both metadata (member) and data (cell) Horizontally scales with user population as APS (Provider Services) supports app server clustering. This means that you no longer need to create multiple iterations of the same report (one for each deployed model). post 11. there is no need to refresh drill-through data. you can drillthrough to: o Relational sources o Other Essbase cubes (scheduled for future release. Automatic association of report to matching models.8 Drill-through Reports The drill-through reporting options in Essbase Studio are much improved over previous drill-through incarnations in the legacy Essbase stack. Drill through support from HVE. drill-through reports will display in and can be launched from the Visual Explorer UI. drill-through reports automatically associated to models. This lets you test the results prior to deploying to a cube or set of cubes. you can drill back to any data source added to studio. As such. drillthrough requests can work across a JVM cluster lightening the load on a specific machine.1. the Studio UI provides full capability to put in test parameters and see the result of a drill-through report.1) o BI+ Repository (scheduled for future release. In the Metadata Navigator.1. So any Essbase cube that contains a dimension that is part of the drill-through can gain access to the report. 42 Lab 2: BSO Cube . If you modify an existing report or add a new report it is immediately available in all models. post 11. • Dynamic association of drill through reports. Essbase Studio allows for more drill-through target options.1. Starting with the 11.1) o URL Standard Financial Data quality Management OBIEE o Custom SQL o Java Method • • • • • • 1. Support for test / preview.

3. 4. De-select everything except “FAMILY”. click “Add”.2. In the Intersection area. Click “OK”. Expand TBC | Hierarchies and select “Product”. 43 Lab 2: BSO Cube . Name the report “Supplier”.

6. Expand Supplier and select “SUPPLIER_ALIAS”. Click “OK”.5. “STATE” and “ZIP”. Select the Report Contents tab. you could add the columns by drag and drop from either the Data Sources area or the Metadata Navigator. Alternatively. 44 Lab 2: BSO Cube . “CITY”. Click “Add” to add columns for your drill-through report. “ADDRESS”.

Go to the Report Contents tab. Go to the Associations tab. 8. De-select “Show Duplicates in Report” and click “Test”. 45 Lab 2: BSO Cube . Select the box for “TBC1Model” and click “Save”.7.

9. Scenario and Time hierarchies to the Intersections area. Click “Save” and then “Close” to close the Drill-through report. Click the “Show Results” button. The Resulting report should appear similar to the one below. Add the Product. 46 Lab 2: BSO Cube . Click “Close” to close the testing screen. Measures. Create another Drill-through report called “POS”. enter “300” next to FAMILY.Under Column Value. Market.

47 Lab 2: BSO Cube . SCENARIO. Month) 10. STATE. CHILD.Expand all the hierarchies and select only the lowest levels for each hierarchy (SKU. Add the following columns to the Report Contents.

48 Lab 2: BSO Cube . you also have the ability to review individual object properties from the lineage chart. 1. The lineage charts display information all the way back to the original source columns or fields. . Right-click on TBC1Model and select “Show Lineage”. Associate the report to TBC1Model. Moreover.11. 9 Data Lineage Through either the right-click menu or standard menu selection you can view lineage diagrams for any metadata element (up to and including deployed models). Click “Save” and then “Close”.

2. 49 Lab 2: BSO Cube .The lineage chart below will appear in the center panel. You can double-click or right-click on any element to see its lineage chart.

1. 50 Lab 2: BSO Cube . Right-click on TBC1Model and select “Cube Deployment Wizard”.10 Cube Deployment A Cube Deployment Wizard is utilized to deploy cubes in Studio. The Wizard retains Essbase server information and specific information related to the outline build and data load process.

select “Build Outline and Load Data”. 51 Lab 2: BSO Cube . Under Load Task Type. click on the “New Connection” button.If you have not connected to the Essbase server yet. Use the following parameters to log in to Essbase: Name the application “TBC” and name the database “TBC”. Click “Finish”. If the box does not appear. an Essbase login dialog box will appear.

Click “Cancel” to close the Cube Deployment Wizard. you may get a warning. Right-click on Essbase Servers and select “Add Essbase Server”. “admin” for Username and “password” for Password. Click “OK”. This does not affect the creation of the cube or the rest of the labs. Type in “ptsessbase” for the Administration Server. Open the EAS Console by selecting the following shortcut: Start | Programs | Oracle EPM System | Essbase | Administration Services | Start Administration Services Console. 4. 3. 52 Lab 2: BSO Cube . 2.At the completion of the build. Click “OK”.

On the right. Double-click “Outline” to open it. “admin” for Username and “password” for Password and Confirm password. 53 Lab 2: BSO Cube .Type in “ptsessbase” for the Essbase Server. you will need to change the active alias table to TBCAlias. 5. the Essbase outline will appear. Expand Essbase Servers | ptsessbase | Applications | TBC |TBC. Click “OK”. In order to view the aliases. Select “Set as active”. Expand the tree from ptsessbase to Applications down to the second TBC. Double-click “Outline”. Go to the “Properties” tab of the Outline and right-click on “TBCAlias” under Alias tables.

Return to the “Outline” tab and expand the Product dimension to view the aliases. 6. Click “OK” to select the “Default” calculation. 54 Lab 2: BSO Cube . Essbase Studio currently does not have an option to run a calc script. Right-click on the second “TBC” and select “Execute calculation…”.

55 Lab 2: BSO Cube .7. Right-click on the second “TBC1” again and select “Preview data”. Double-click on “Market” and “Product” to verify that data has been loaded and aggregated.

Excel 2003 Excel 2007 (Add-Ins tab) 7. refer to the installation lab for instructions on installing the Add-in manually). type in “ptsessbase” in the Server box. 56 Lab 2: BSO Cube . verify that the Menu Item Essbase is showing on the Menu Bar (if not. Select “TBC/TBC” in the Application/Database window and click “OK”. At the login prompt.6. 5. click on “Essbase” and select “Connect…”. “admin” for Username and “password” for Password. To query the cube using the Excel Add-in. Click “OK”. open Excel.

Click “OK”. In the Display tab. check Use Aliases and select “TBCAlias” from the dropdown box. Notice that the Attribute dimensions do not show up. 57 Lab 2: BSO Cube . Adjust Columns. #Missing Rows. When double-clicking (or retrieving) on a blank worksheet. type “0” (zero) into the #Missing Label text box. Attribute dimensions can be added to the query. Double-click anywhere on the blank worksheet or click on “Essbase | Retrieve” from the Menu Bar.6. the query will consist of every root (top level) member from each dimension. 7. but are not required. select Subitems. Click “Essbase | Options…” from the Menu Bar.

8. 58 Lab 2: BSO Cube . “2007” and then “Qtr1-2007” to drilldown on the Time dimension. Notice that 2006 and 2008 do not appear when you did a drilldown on Time. Double-click on “Time”. Double-click on “MARKET” to drilldown to the regions. 9. #Missing is the null indicator for Essbase. so when we checked the Suppress #Missing option. the rows with no data are not displayed.

Do the same thing with the Time dimension (click on any member of the Time dimension). “South”.10. “Central”. 59 Lab 2: BSO Cube . Double-click on “West”. 11. Drag the Measures dimension by clicking down on “Measures” with your right mouse button (do not release the button yet) and drag to where the column dimensions are located (see image below) and release the right mouse button. and “East” to drilldown to the states.

60 Lab 2: BSO Cube .12 Type over “MEASURES” with “Sales” and “SCENARIO” with “Actual”. The query now reads Actual Sales by State and Region across Time periods for total Products. Click “Essbase | Retrieve” from the Menu Bar.

“PKGTYPE” is now visible on the spreadsheet. Double-click on “PKGTYPE”. Click “OK”. Select “PKGTYPE” from the Dimension drop down box.13. click on “PKGTYPE” in the Members box and click “Add” so that “PKGTYPE” shows up in the Rules box. 61 Lab 2: BSO Cube . Click on the blank cell to the right of “PRODUCT” and select “Essbase | Member Selection…”.

Smartview uses HTTP/SOAP which allows for more flexibility in connecting with Essbase. First. some mouse actions such as double-clicking gives precedence to the Essbase add-in and may result in some undesired consequences. Before we begin with Smartview. To disable any mouse actions for the Essbase add-in. Smartview also uses a server component (Analytic Provider Services) which handles the query generation to Essbase. 1. Your query should look similar to the one below. we will first need to either remove the Essbase add-in or disable the mouse actions for the Essbase add-in. but their presence is not mandatory. go to “Essbase | Options” and de-select all the check boxes under Mouse Actions in the Global tab. Attribute dimensions can be added to any query whenever their analysis is needed. While both add-ins can run concurrently.Pivot “Can” to the columns underneath Time (right-click drag) so that Package Types no longer go down the rows. We will now use Smartview to connect directly to Essbase and query in a similar manner as the classic Essbase add-in. 11 Smartview Smartview is the successor to the Classic add-in with some important differences. while the classic add-in uses a TCP/IP connection to Essbase. 62 Lab 2: BSO Cube . Smartview works with multiple Office products and allows you to bring in content from various Oracle sources.

63 Lab 2: BSO Cube . click “Connect to Provider Services”. go to “Tools | Add-ins”. so in Data Source Manager. 2. First. navigate to a blank worksheet or open a new workbook.To remove the Essbase add-in. In Excel 2007. De-select the check boxes next to both Essbase add-ins and click “OK”. we will first need to define a connection to Essbase using the Smartview Data Source Manager. select “Hyperion | Data Source Manager…”. Next. you can either select “Hyperion | Data Source Manager…” from the Add-Ins menu or click the “Connect” icon from the Hyperion menu. Analytic Provider Services is the server component for Smartview. Since Smartview supports multiple Oracle sources. 3.

4. check the box next to “Override default” and in the URL window. replace “localhost” with “ptsessbase” in the URL. Click “OK”. In the Options screen under Hyperion Provider Service URL. 64 Lab 2: BSO Cube . Since we did not yet change the APS URL to point to the Linux VM. you will receive this message: Click “Change APS URL”.

select “All”. In the Views dropdown. 65 Lab 2: BSO Cube . Right-click on “Oracle Essbase” and select “Add”.The Smartview Data Source Manager should now look like this: 5.

“admin” for User Name and “password” for Password. Drill down on ptsessbase and on TBC. dropdown and 66 Lab 2: BSO Cube . Highlight the second TBC and click on the Ad-hoc/Open select “Ad-hoc Analysis”. Click “OK”. You can also right-click on TBC and select “Ad-hoc Analysis”.Ensure that “Oracle Essbase” is in the Product dropdown and type in “ptsessbase” for the Product Server Name.

67 Lab 2: BSO Cube . you can go to the Options (“Hyperion | Options”) screen to set your querying options such as suppression of #missing and setting different formats for drill-through report cells. As with the Essbase add-in. however. you must select an Alias table from “Hyperion | Ad-Hoc Analysis | Change Alias Table”. while allowing dimensions to be dragged to/from the spreadsheet as they are needed in the analysis.6. You can right-click drag to/from the POV Manager and set the filters while the dimensions are in the POV Manager. drill-ups and pivots work the same way as in the Essbase add-in. The POV Manager allows for a less cluttered spreadsheet. the one major difference is the introduction of the POV Manager. Try to replicate the query below based on your knowledge of the Essbase add-in and some of the tips mentioned here. To enable aliases. Smartview has similar functionality with the classic add-in. Drill-downs. 7.

68 Lab 2: BSO Cube . If you were able to replicate the query above. open the Lab_Queries.12 Drill-through Reporting 1. Go to Hyperion | Ad-Hoc Analysis | Change Alias Table and select “None”. Set formatting for drill-through cells. Run an Adhoc Analysis on TBC. In the Cell Styles tab. Otherwise. expand Analytic Services | Data cells. skip to step 2. click on the drop down box where it says Default Styles and select “Analytic Services”. You will need to use Smartview to view the drill-through report so open the Data Source Manager and connect to Provider Services.xls file from the In Class Files folder and select tab Lab 2.7. 2. If you can not expand on Data cells. 3. go to “Hyperion | Options”.

right-click on “Drill-through” and select “Font”.Check the box next to “Drill-through”. Click “OK” twice to return to the spreadsheet. Change the Font style to “Bold” and to your favorite Color. 69 Lab 2: BSO Cube .

4. Double-click on “Product” until you see the product families listed down the rows. If the product families are already going down the rows. The data should have changed to the Drill-through formatting. select “Hyperion | Refresh” or click the “Refresh” button on the POV Manager. 70 Lab 2: BSO Cube . Select one of the drill-through cells and select “Hyperion | Ad Hoc Analysis | Drill-Through Reports”. 5.

6. 7. The Supplier drill-through report should display in a new worksheet. 71 Lab 2: BSO Cube . ‘100’). Double-click on a Product Family (ie. Click “Launch” to open the Supplier report.

72 Lab 2: BSO Cube .8. 13 Visual Explorer Visual Explorer is a graphical reporting tool that allows you to “visually” navigate through the data. 1. The problem with looking at data in a spreadsheet is that unless you know what to look for. The POS drill-through report should display in a new worksheet. This is where Visual Explorer comes in. Click “Launch” to open the POS report. right-click on the TBC database and select “Ad-hoc Analysis”. 9. Insert or navigate to a blank worksheet and from the Smartview Data Source Manager. it can be difficult to spot anomalies or trends in the data without looking at the data in a graphical manner. Select one of the drill-through cells and select “Hyperion | Ad Hoc Analysis | Drill-Through Reports”.

73 Lab 2: BSO Cube . Note: in the Essbase add-in.Start Visual Explorer by selecting “Hyperion | Link View | Visualize in HVE”. access Visual Explorer from “Essbase | Visualize & Explore…” Click “Cancel” when the Show Me! screen appears.

Select “Edit | Clear | Clear Sheet” 9. 74 Lab 2: BSO Cube . Expand Margin in the Measures panel so that Sales is visible.

A single bar will appear representing Sales revenue for all Products across all Markets for the entire Year. Drag “Sales” to the Rows box. 75 Lab 2: BSO Cube .10.

Drag “Gen2. 76 Lab 2: BSO Cube . Four bars will now appear representing Sales revenue for all Products for the entire Year by each Market Region.11.MARKET” to the Columns box.

77 Lab 2: BSO Cube .12.PRODUCT” to the Color box. go to Data | Alias File and select TBCAlias. Drag “Gen2. from the menu. The four bars turn to stacked bars with different colors representing each of the Product Lines. If you are not seeing the Product aliases.

Right-click on the Y-axis of the bar chart and select “Add Reference Line…”.13. When the Reference Line dialog box appears. 78 Lab 2: BSO Cube . accept the default selections and click “OK”.

An average line will appear representing the average Sales revenue for the Regions.MARKET”. 79 Lab 2: BSO Cube . 14.PRODUCT” from the Color box to the Columns box to the right of “Gen2. Drag “Gen2.

select the radio button for “Entire Table” and click “OK”. If you would like to see an average line across all Sales categories.The bar chart now represents Sales by Region and Product Line. right-click on one of the average lines and select “Edit…”. 15. In the Edit Reference Line dialog box. 80 Lab 2: BSO Cube .

The average line will now represent the average for all the Sales categories. 81 Lab 2: BSO Cube .

16. 82 Lab 2: BSO Cube . From the Measures panel drag “Profit %” to the Color box. Further analysis could reveal the reasons for this anomaly. Note that in the West the Profit % of some Product Lines are relatively low despite the high Sales revenue. Each of the Sales bars will now turn to various shades of green. the darker the green the greater the Profit %.

Now let’s take a look at how Sales revenue gets impacted based on the amount of Marketing expenditures. remove the average line by rightclicking on it and selecting “Remove”.PRODUCT”. Expand Total Expenses in the Measures panel and drag “Marketing” to the Columns box to the right of “Gen2. 18. remove Profit % by right-clicking on Profit % and selecting “Remove”. First. Next. 83 Lab 2: BSO Cube .17.

Drag “Gen2.PRODUCT” from the Columns box to the Shape box.19.MARKET” from the Columns box to the Color box. Drag “Gen2. 20. 84 Lab 2: BSO Cube .

Each mark corresponds to a Region/Product Line combination. right-click on a white area in the chart and select “Trend Lines”. Adding a Trend Line will show the exact correlation between Sales and Marketing across all the data points. The marks on the chart represent the correlation between Marketing expenditures and Sales (as Marketing expenses increase. Color coding and the different shapes of the marks make it easy to identify which Region and Product Line the marks represent. 21. 85 Lab 2: BSO Cube .Your chart should now look similar to the one below. To add a Trend Line. Revenue should also increase by some fixed factor).

uncheck “Gen2. 22. In the Trend Lines Options dialog box. right-click on any Trend Line and select “Edit Trend Lines…”. To show only one Trend Line.A trend line will appear for each Region. 86 Lab 2: BSO Cube .MARKET” and click “OK”.

87 Lab 2: BSO Cube .PRODUCT” to the Level of Detail box. The marks below the Trend Line are the Region/Product Line combinations that are underperforming (where the Marketing expenses are high relative to Sales). drag “Gen3.MARKET” and “Gen3. The marks above the Line are overperformers (those where Sales are higher relative to their Marketing expenses). To add more data points to the chart.You should now see one Trend Line. 23.

Those below and to the far right of the trend line have extremely high marketing costs relative to the sales they are generating. Points below the trend line show below average sales relative to their marketing costs. This concludes Lab 2. 24. Move your mouse over one of the data points to get detailed information.The chart should now look similar to the one below. 88 Lab 2: BSO Cube . You may now close Visual Explorer and Excel.

Copy the appropriate script into a Terminal window to run. including Excel 2. If you started any applications. The correct shutdown procedure will ensure that the VM will function properly the next time you use it. you should always stop Shared Services after all the Essbase products have been stopped. 89 Lab 2: BSO Cube . 1. You should also stop Essbase before stopping Shared Services. Type “1” and hit <Enter>. it will ask if you would like to stop all the applications and exit Essbase. it is advised that you shut them down in the order listed on the file. All Shutdown scripts are included at the bottom of the Start Stop Services. For shutting down multiple products. Close all client tools first. Use the appropriate Shutdown scripts for each product you started (except for Essbase). For example.14 Shutting Down the VM It is important that you shutdown your VM properly at the conclusion of each day. Shut down Essbase by typing “Exit” or “Quit” in the terminal window it was started in. 3.txt file.

When you turn your VM back on. Never hit the “X” on your VMware program to shut down. The VM will take a few minutes to shut down at that point. 90 Lab 2: BSO Cube . When all the servers on the VM are stopped. shut down all servers and the VM properly and restart the VM. If this happens. Select “Shut down” and click “OK”. you can shut down the VM by clicking on “Actions” at the top and selecting “Log Out”. it may behave abnormally. This will place the VM in suspended mode and does not actually shut down the VM.5.