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

2. Start Shared Services. Copy the following two lines from the Start Stop Services.txt file or type in the terminal window: cd /software/hyperion/deployments/Tomcat5/bin/ ./startSharedServices9.sh <Enter>

Shared Services must be started before any of the other services. DO NOT CLOSE this window. Wait approximately 30 seconds before continuing to the next step. 3. Start Essbase. For this step, 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. Copy the following two lines from the Start Stop Services.txt file or type in the terminal window: cd /software/hyperion/products/Essbase/EssbaseServer/bin ./startEssbase.sh <Enter>

This starts up the Essbase server in the foreground, so the prompt will not be returned. Once you see the line Waiting for Client Requests, you will know that Essbase has started properly. Minimize this window (DO NOT CLOSE). 4 Lab 2: BSO Cube

4. Start EAS. Open another terminal window and copy the following two lines from the Start Stop Services.txt file or type: cd /software/hyperion/deployments/Tomcat5/bin/ ./starteas.sh <Enter>

This starts up the EAS server in the background. You can use this terminal for the next step or minimize the window (DO NOT CLOSE). 5. Start APS. Open a new terminal window or use the one from the previous step since EAS is running in the background and returned the prompt. Copy the following two lines from the Start Stop Services.txt file or type in the terminal window: cd /software/hyperion/deployments/Tomcat5/bin/ ./startaps.sh <Enter>

This starts up the APS server in the background. You can use this terminal for the next step or minimize the window (DO NOT CLOSE). 6. Start Essbase Studio. Open a new terminal window or use the one from the previous step since APS is running in the background and returned the prompt. Copy the following two lines from the Start Stop Services.txt file or type in the terminal window: cd /software/hyperion/products/Essbase/EssbaseStudio/Server ./startServer.sh <Enter>

This starts up the Studio server in the background. DO NOT CLOSE this window. You have completed all the start ups for this lab.

5 Lab 2: BSO Cube

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, it must first be saved as a CSV file. 1. Open the Essbase Studio Console by selecting the following shortcut: Start | Programs | Oracle EPM System | Essbase | Essbase Studio | Essbase Studio Console.

2. At the log in screen, select or type ptsessbase for the Server, admin for the User and password for the Password. Click Log In

3. The left panel in Studio has the Metadata Navigator, which provides a tree view of your metadata repository. Folders can be created under the root directory to manage and organize metadata elements. The right panel contains the data sources and minischemas that you will need for building your cubes. To begin, make sure that the Data Sources tab is selected in the right panel. Right-click on Data Sources and select New | Data Source.

6 Lab 2: BSO Cube

4. We will first add an Oracle schema as a data source. Provide the following information in the Define Connection screen:

Click on Test Connection. Click OK. If the connection was successful, click Next in the Define Connection screen.

7 Lab 2: BSO Cube

In the Define Tables screen, select all tables. Click Finish. We will be creating the minischemas and hierarchies later.

Click OK when completed.

Expand on TBC and on one of the tables to view the fields. Right-click on a table and select View Sample Data.

8 Lab 2: BSO Cube

The first 200 rows of the table will appear in the middle panel. Click on the X to close the table.

5. Repeat adding a new data source by selecting File | New | Data Source. Type Text as the Connection Name and select Text File for the Data Source Type. Ensure that Comma is selected as the Delimiter. Click Browse next to Location.

9 Lab 2: BSO Cube

Select tbc_samples and click OK.

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

10 Lab 2: BSO Cube

Expand Text and right-click on one of the files to view its content.

4 Modeling Data Sources - 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. The process for modeling a relational source captures the join relationships between tables. Essbase Studio minischemas present a logical representation of the relational schema and provide the mappings to allow Studio to traverse the data source. Other important points regarding minischemas are as follows: Text files can be added to minischemas for the purpose of logical grouping only. They cannot be joined to other text files or relational tables. Studio supports the use of multiple fact tables in the schema; both can provide fact data to the model. There is no requirement to have a fact table for hierarchy creation for Essbase deployment. To that end, 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.

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. This is a preliminary step in data modeling using Essbase Studio to create analytic applications. 1. In the Minischemas tab on the right panel, right-click on Minischemas and select New | Minischema.

11 Lab 2: BSO Cube

2. At the Create Minischema screen, type TBC_Schema for the Minischema Name. Click Next.

Select TBC from the Connections drop down. Select all the tables to the schema. Click Finish.

12 Lab 2: BSO Cube

3. The minischema for TBC should appear in the middle panel. The tables should be joined based on the joins that were created in the physical schema. If no joins were created, go to the next step. The only required join that was not created in the physical schema is the join from the PRODUCT to the PRODUCTDIM table. Locate the PRODUCTDIM table (may be out of view below the other tables) and move it underneath the FAMILY table.

Click on the SKU field in the PRODUCT table and drag a join line to the SKU field in the PRODUCTDIM table.

13 Lab 2: BSO Cube

4. If no joins appeared in the minischema, right-click on any whitespace in the work area and select Add Joins By Inspection.

Inspection will yield all the matching field names between tables. Since we do not need all those joins, select only the ones identified below. Click OK.

14 Lab 2: BSO Cube

Alternatively, you can join tables manually by dragging join lines across the tables, starting and ending with the joining fields. You can also arrange the tables and joins by right-clicking on any whitespace in the minischema viewer and selecting Lay out schema.

5. Right-click on the Measures table and select Add Join

In the second Table drop down, select MEASURES. In the first column, select PARENT and in the second column, select CHILD. Click OK.

. 15 Lab 2: BSO Cube

This creates a recursive join on the table allowing for parent-child queries. Your minischema should now look similar to the one below.

6. Save (File | Save) and close (X) the minischema.

5 Modeling Data Sources - 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, a metadata element is anything that you can use to create an analytical model. The Studio allows you to organize elements into logical groups that can be used to create other elements. 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. The resulting hierarchies can then be stored in a folder of their own. You can create as many folders and sub-folders as desired to organize your deployment. Whether you separate by element type, model, or both is completely up to you. However, it is recommended that you create folders to organize elements prior to creating hierarchies. It simply makes the process easier. 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.

16 Lab 2: BSO Cube

1. First, create folders for the metadata elements. Right-click the Root folder in the Metadata Navigator (left panel) and select New | Folder.

2. Type TBC for the Name. Click OK.

3. Create the following folders under TBC: Dimension Elements, Hierarchies, Cube Schemas and Drill-through Reports.

17 Lab 2: BSO Cube

6 Modeling Data Sources Dimension Elements and Hierarchies

Dimension Elements make up the hierarchies. They can be columns from a data source or they can be derived (logical). They are then used to form levels within hierarchies or as distinct members. The term level is used in a very generic sense in that there is no requirement to understand the concepts of levels, generations, parents or children in order to build hierarchies. You can create custom members, hierarchies, attributes, and alternate hierarchies all in the same fashion. Creating hierarchies in the Studio is a matter of drag and drop. You initiate the hierarchy creation wizard via the right-click menu or through the menu system. 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. At any point during the process you can perform a full preview of the resulting hierarchy. It is also important to note that you can cross data sources and data source types during the hierarchy creation process. This is possible with or without the presence of a fact table. 1. Start by expanding the TBC data source in the Data Sources tab on the right. Expand the Market table and drag the STATE field to the Dimension Elements folder in the Metadata Navigator.

Copy STATE by right-clicking on it and selecting Copy. Right-click on the Dimension Elements folder and select Paste.

18 Lab 2: BSO Cube

Rename STATE_copy to EAST_STATE. Edit EAST_STATE by double-clicking or right-clicking and selecting Edit.

Click in the Filter box. Expand TBC and REGION. 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.REGION.REGION Type: ==East at the end of the string. Click OK.

19 Lab 2: BSO Cube

Right-click on EAST_STATE and select View Sample Data.

Logical columns such as this can be created by filtering existing columns or by using a variety of Date, String and Numeric functions. We will do other examples of this later in this lab. 2. Drag the following columns from the TBC data source to the Dimension Elements folder: MEASURES.CHILD MEASURES.PARENT PRODUCTDIM.FAMILY PRODUCT.SKU PRODUCT.CAFFEINATED PRODUCT.OUNCES PRODUCT.PKGTYPE REGION.REGION REGION.DIRECTOR SALES.TRANSDATE SCENARIO.SCENARIO

20 Lab 2: BSO Cube

3. Adding a sort order. Double-click on FAMILY in the Dimension Elements folder. Expand TBC > PRODUCTDIM and select FAMILY. Click on the outline. Click OK. icon under Sort Order. This will order the Product Families in ascending order in the

Do the same for SKU. Expand TBC > PRODUCT and select SKU.

21 Lab 2: BSO Cube

4. Create custom dimension elements. For the Time dimension, we can use the time wizard, or we can build a standard hierarchy and tag it as Time during the cube deployment process. For this exercise, 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.

Type Year for the name. Select the Functions tab and expand Date. Double-click on the year function, year($$DateOperand$$) should appear in the Caption Binding box. Highlight $$DateOperand$$.

22 Lab 2: BSO Cube

Go to the Source tab and expand TBC | SALES. Double-click TRANSDATE. The Caption Binding box should now read: 'year'( connection : \'TBC'::'TBC.SALES'.'TRANSDATE' ). Also, with TRANSDATE highlighted, click on the icon under Sort Order. This will order the years in ascending order in the outline. Click OK.

View the data for the Year field.

23 Lab 2: BSO Cube

Create a dimension element called Quarter using the quarterAsString and year functions and concatenating a - between the two functions. The formula in Caption Binding should read:
'quarterAsString'( connection : \'TBC'::'TBC.SALES'.'TRANSDATE' ) || "-" || 'year'( connection : \'TBC'::'TBC.SALES'.'TRANSDATE' )

With TRANSDATE highlighted, click on the icon under Sort Order. This will order the quarters in ascending order in the outline. Click OK and view the data.

Create a dimension element called Month using a similar method. The formula in Caption Binding should read:
'monthShortName'( connection : \'TBC'::'TBC.SALES'.'TRANSDATE' ) || "-" || 'year'( connection : \'TBC'::'TBC.SALES'.'TRANSDATE' )

With TRANSDATE highlighted, click on the in the outline. Click OK and view the data.

icon under Sort Order. This will order the months in ascending order

24 Lab 2: BSO Cube

5. Right-click on the Hierarchies folder and select New | Hierarchy.

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. If you drag it to the line below FAMILY, SKU will be at the same level. In that case, click on the icon to move SKU below FAMILY.

25 Lab 2: BSO Cube

Add 3 other hierarchies below the first one:

Name the hierarchy Product. Click Save. Click the Preview button to see how the hierarchies would look. Click OK. Click Close to close the Product hierarchy.

26 Lab 2: BSO Cube

6. Create the Market hierarchy in a similar fashion.

7. Create the Measures and Scenario hierarchies

27 Lab 2: BSO Cube

8. Create the time hierarchy. Name it Time. Make Year the top of the hierarchy then Quarter and then Month at the bottom. Click Preview to see how the hierarchy would look like.

Click OK. Click Save. Click Close.

7 Modeling Data Sources - Cube Schemas

Cube schemas are simply collections of hierarchies that make up the dimensions in a cube. During the cube schema creation process you select which hierarchies you would like to include in each dimension. You also have the option of hand creating a custom Measures dimension. Alternately, you can select a preexisting hierarchy and tag it as measures in the cube deployment process. 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. The generic process of modeling and the specific process of setting Essbase properties are intentionally separated in the Studio. 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. The current incarnation of the deployment wizard has four fundamental steps: 1. Set Essbase properties for a dimension, dimension level, or specific member (in the case of measures). These properties might include consolidation operators, data storage, formulae, etc. 2. Validate the model prior to deployment. 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. 3. Set deployment options. You select whether you want an ASO, BSO, or XOLAP model for example. Additionally, you can choose when and how (metadata only, data only or both) you want the model deployed. 4. You specify which Essbase server (mapped as a connection when creating data sources) and execute the deployment. Upon execution the Studio logs into the specified target server and creates the application and database as specified.

28 Lab 2: BSO Cube

1. In Data Sources panel expand TBC and Sales. Drag SALES.AMOUNT to the Dimensional Elements folder in the Metadata Navigator.

2. Right-click on the Cube Schemas folder in the Metadata Navigator and select New | Cube Schema.

29 Lab 2: BSO Cube

3. Name the cube schema TBC1. Expand the Hierarchies folder and add the following to the Hierarchies area (keep in this order): a. b. c. d. e. Measures Time Scenario Product Market

Expand the Dimension Elements folder and add AMOUNT to the Measures area. Click the Preview Hierarchies button and review the dimensions. Click OK to close the Preview dialog, and click Next in the Cube Schema Wizard.

On the Cube Schema Options screen, check the Create Essbase Model box. On the Accounts Dimension drop down list, select Measures. Click Finish.

30 Lab 2: BSO Cube

The TBC1 Model will appear in the middle panel. Note: The Measures hierarchy was built as a standard hierarchy as opposed to being built as a Measure Hierarchy. This is because there is a separate Measures dimension table that contains the Measures hierarchy. In those cases, 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. 4. The next step towards deploying an application is to set all the Essbase properties in the Essbase Model. Right-click any whitespace in the model and select Essbase Properties.

On the Model Properties screen, select Measures and go to the Info tab. Set Data Storage to Label Only. Click Apply.

31 Lab 2: BSO Cube

Expand Measures | Parent under TBC1Model and select CHILD. Go to the Info tab and set Consolidation to External Source and select CONSOLIDATION in the drop down. Set Two Pass Calculation to External Source and select TWOPASSCALC in the drop down. Set Data Storage to External Source and select STORAGE 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. Set Skip to External Source and select SKIP in the drop down. Set Variance Reporting to External Source and select VARIANCEREPORTING in the drop down. Click Apply.

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 seriesbutton 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

6. Save TBC1Model (if grayed out, then it is already saved).

7. Aliases are set a little differently in Studio. 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. Select Tools | Alias Set Manager.

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. 38 Lab 2: BSO Cube

Under Binding Source, expand TBC | Dimension Elements and click on SKU. Under Binding Expression, expand PRODUCTDIM and double-click SKU_ALIAS. Click OK.

39 Lab 2: BSO Cube

Repeat with FAMILY / PRODUCTDIM | FAMILY_ALIAS and CHILD / MEASURES | MEASURES_ALIAS.

TBCAlias should now have 3 rows. Click OK.

40 Lab 2: BSO Cube

If you closed TBC1Model, right-click on it and select Edit. Right-click in the work area and select Essbase Properties.

Click on TBC1Model and select the Alias tab. Select TBCAlias under Available Tables and click the right arrow to add to Selected Tables. Click Apply. Run a validation. Ignore the warning if identical to the previous and click Close.

41 Lab 2: BSO Cube

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

1. In the Metadata Navigator, right-click the Drill Through Reports folder and select New | Drill-through Report.

42 Lab 2: BSO Cube

2. Name the report Supplier. In the Intersection area, click Add.

3. Expand TBC | Hierarchies and select Product. Click OK.

4. De-select everything except FAMILY.

43 Lab 2: BSO Cube

5. Select the Report Contents tab. Click Add to add columns for your drill-through report.

6. Expand Supplier and select SUPPLIER_ALIAS, ADDRESS, CITY, STATE and ZIP. Click OK.

Alternatively, you could add the columns by drag and drop from either the Data Sources area or the Metadata Navigator.

44 Lab 2: BSO Cube

7. Go to the Associations tab. Select the box for TBC1Model and click Save.

8. Go to the Report Contents tab. De-select Show Duplicates in Report and click Test.

45 Lab 2: BSO Cube

Under Column Value, enter 300 next to FAMILY. Click the Show Results button. The Resulting report should appear similar to the one below. Click Close to close the testing screen. Click Save and then Close to close the Drill-through report.

9. Create another Drill-through report called POS. Add the Product, Market, Measures, Scenario and Time hierarchies to the Intersections area.

46 Lab 2: BSO Cube

Expand all the hierarchies and select only the lowest levels for each hierarchy (SKU, STATE, CHILD, SCENARIO, Month)

10. Add the following columns to the Report Contents.

47 Lab 2: BSO Cube

11. Associate the report to TBC1Model. Click Save and then Close.

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). The lineage charts display information all the way back to the original source columns or fields. Moreover, you also have the ability to review individual object properties from the lineage chart. 1. Right-click on TBC1Model and select Show Lineage.

48 Lab 2: BSO Cube

The lineage chart below will appear in the center panel.

2.

You can double-click or right-click on any element to see its lineage chart.

49 Lab 2: BSO Cube

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. 1. Right-click on TBC1Model and select Cube Deployment Wizard.

50 Lab 2: BSO Cube

If you have not connected to the Essbase server yet, an Essbase login dialog box will appear. If the box does not appear, click on the New Connection button. Use the following parameters to log in to Essbase:

Name the application TBC and name the database TBC. Under Load Task Type, select Build Outline and Load Data. Click Finish.

51 Lab 2: BSO Cube

At the completion of the build, you may get a warning. This does not affect the creation of the cube or the rest of the labs. Click OK. Click Cancel to close the Cube Deployment Wizard.

2. Open the EAS Console by selecting the following shortcut: Start | Programs | Oracle EPM System | Essbase | Administration Services | Start Administration Services Console.

3. Type in ptsessbase for the Administration Server, admin for Username and password for Password. Click OK.

4. Right-click on Essbase Servers and select Add Essbase Server.

52 Lab 2: BSO Cube

Type in ptsessbase for the Essbase Server, admin for Username and password for Password and Confirm password. Click OK.

5. Expand the tree from ptsessbase to Applications down to the second TBC. Double-click Outline. On the right, the Essbase outline will appear. Expand Essbase Servers | ptsessbase | Applications | TBC |TBC. Double-click Outline to open it.

In order to view the aliases, you will need to change the active alias table to TBCAlias. Go to the Properties tab of the Outline and right-click on TBCAlias under Alias tables. Select Set as active.

53 Lab 2: BSO Cube

Return to the Outline tab and expand the Product dimension to view the aliases.

6. Right-click on the second TBC and select Execute calculation. Click OK to select the Default calculation. Essbase Studio currently does not have an option to run a calc script.

54 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.

55 Lab 2: BSO Cube

6. To query the cube using the Excel Add-in, open Excel, verify that the Menu Item Essbase is showing on the Menu Bar (if not, refer to the installation lab for instructions on installing the Add-in manually), click on Essbase and select Connect. Excel 2003 Excel 2007 (Add-Ins tab)

7. At the login prompt, type in ptsessbase in the Server box, admin for Username and password for Password. Click OK.

5. Select TBC/TBC in the Application/Database window and click OK.

56 Lab 2: BSO Cube

6. Double-click anywhere on the blank worksheet or click on Essbase | Retrieve from the Menu Bar.

When double-clicking (or retrieving) on a blank worksheet, the query will consist of every root (top level) member from each dimension. Notice that the Attribute dimensions do not show up. Attribute dimensions can be added to the query, but are not required. 7. Click Essbase | Options from the Menu Bar.

In the Display tab, select Subitems, #Missing Rows, Adjust Columns, type 0 (zero) into the #Missing Label text box, check Use Aliases and select TBCAlias from the dropdown box. Click OK.

57 Lab 2: BSO Cube

8. Double-click on Time, 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. #Missing is the null indicator for Essbase, so when we checked the Suppress #Missing option, the rows with no data are not displayed. 9. Double-click on MARKET to drilldown to the regions.

58 Lab 2: BSO Cube

10. 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. Do the same thing with the Time dimension (click on any member of the Time dimension).

11. Double-click on West, Central, South, and East to drilldown to the states.

59 Lab 2: BSO Cube

12 Type over MEASURES with Sales and SCENARIO with Actual.

Click Essbase | Retrieve from the Menu Bar.

The query now reads Actual Sales by State and Region across Time periods for total Products.

60 Lab 2: BSO Cube

13. Click on the blank cell to the right of PRODUCT and select Essbase | Member Selection.

Select PKGTYPE from the Dimension drop down box, click on PKGTYPE in the Members box and click Add so that PKGTYPE shows up in the Rules box. Click OK.

PKGTYPE is now visible on the spreadsheet. Double-click on PKGTYPE.

61 Lab 2: BSO Cube

Pivot Can to the columns underneath Time (right-click drag) so that Package Types no longer go down the rows.

Your query should look similar to the one below. Attribute dimensions can be added to any query whenever their analysis is needed, but their presence is not mandatory.

11 Smartview
Smartview is the successor to the Classic add-in with some important differences. First, while the classic add-in uses a TCP/IP connection to Essbase, Smartview uses HTTP/SOAP which allows for more flexibility in connecting with Essbase. Smartview also uses a server component (Analytic Provider Services) which handles the query generation to Essbase. Smartview works with multiple Office products and allows you to bring in content from various Oracle sources. We will now use Smartview to connect directly to Essbase and query in a similar manner as the classic Essbase add-in. 1. Before we begin with Smartview, we will first need to either remove the Essbase add-in or disable the mouse actions for the Essbase add-in. While both add-ins can run concurrently, some mouse actions such as double-clicking gives precedence to the Essbase add-in and may result in some undesired consequences. To disable any mouse actions for the Essbase add-in, go to Essbase | Options and de-select all the check boxes under Mouse Actions in the Global tab.

62 Lab 2: BSO Cube

To remove the Essbase add-in, go to Tools | Add-ins. De-select the check boxes next to both Essbase add-ins and click OK.

2. Since Smartview supports multiple Oracle sources, we will first need to define a connection to Essbase using the Smartview Data Source Manager. First, navigate to a blank worksheet or open a new workbook. Next, select Hyperion | Data Source Manager. In Excel 2007, you can either select Hyperion | Data Source Manager from the Add-Ins menu or click the Connect icon from the Hyperion menu.

3. Analytic Provider Services is the server component for Smartview, so in Data Source Manager, click Connect to Provider Services.

63 Lab 2: BSO Cube

4. Since we did not yet change the APS URL to point to the Linux VM, you will receive this message: Click Change APS URL.

In the Options screen under Hyperion Provider Service URL, check the box next to Override default and in the URL window, replace localhost with ptsessbase in the URL. Click OK.

64 Lab 2: BSO Cube

The Smartview Data Source Manager should now look like this:

5. In the Views dropdown, select All.

Right-click on Oracle Essbase and select Add.

65 Lab 2: BSO Cube

Ensure that Oracle Essbase is in the Product dropdown and type in ptsessbase for the Product Server Name, admin for User Name and password for Password. Click OK.

Drill down on ptsessbase and on TBC. Highlight the second TBC and click on the Ad-hoc/Open select Ad-hoc Analysis. You can also right-click on TBC and select Ad-hoc Analysis.

dropdown and

66 Lab 2: BSO Cube

6. Smartview has similar functionality with the classic add-in, however, the one major difference is the introduction of the POV Manager. The POV Manager allows for a less cluttered spreadsheet, while allowing dimensions to be dragged to/from the spreadsheet as they are needed in the analysis.

7. As with the Essbase add-in, 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. Drill-downs, drill-ups and pivots work the same way as in the Essbase add-in. You can right-click drag to/from the POV Manager and set the filters while the dimensions are in the POV Manager. To enable aliases, you must select an Alias table from Hyperion | Ad-Hoc Analysis | Change Alias Table. Try to replicate the query below based on your knowledge of the Essbase add-in and some of the tips mentioned here.

67 Lab 2: BSO Cube

12

Drill-through Reporting

1. If you were able to replicate the query above, skip to step 2. Otherwise, open the Lab_Queries.xls file from the In Class Files folder and select tab Lab 2.7. You will need to use Smartview to view the drill-through report so open the Data Source Manager and connect to Provider Services. Run an Adhoc Analysis on TBC.

2. Go to Hyperion | Ad-Hoc Analysis | Change Alias Table and select None.

3. Set formatting for drill-through cells, go to Hyperion | Options. In the Cell Styles tab, expand Analytic Services | Data cells. If you can not expand on Data cells, click on the drop down box where it says Default Styles and select Analytic Services.

68 Lab 2: BSO Cube

Check the box next to Drill-through, right-click on Drill-through and select Font.

Change the Font style to Bold and to your favorite Color. Click OK twice to return to the spreadsheet.

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, select Hyperion | Refresh or click the Refresh button on the POV Manager. The data should have changed to the Drill-through formatting.

5. Select one of the drill-through cells and select Hyperion | Ad Hoc Analysis | Drill-Through Reports.

70 Lab 2: BSO Cube

6. Click Launch to open the Supplier report.

The Supplier drill-through report should display in a new worksheet.

7. Double-click on a Product Family (ie. 100).

71 Lab 2: BSO Cube

8. Select one of the drill-through cells and select Hyperion | Ad Hoc Analysis | Drill-Through Reports. 9. Click Launch to open the POS report.

The POS drill-through report should display in a new worksheet.

13

Visual Explorer

Visual Explorer is a graphical reporting tool that allows you to visually navigate through the data. The problem with looking at data in a spreadsheet is that unless you know what to look for, it can be difficult to spot anomalies or trends in the data without looking at the data in a graphical manner. This is where Visual Explorer comes in. 1. Insert or navigate to a blank worksheet and from the Smartview Data Source Manager, right-click on the TBC database and select Ad-hoc Analysis.

72 Lab 2: BSO Cube

Start Visual Explorer by selecting Hyperion | Link View | Visualize in HVE.

Note: in the Essbase add-in, access Visual Explorer from Essbase | Visualize & Explore Click Cancel when the Show Me! screen appears.

73 Lab 2: BSO Cube

Select Edit | Clear | Clear Sheet

9. Expand Margin in the Measures panel so that Sales is visible.

74 Lab 2: BSO Cube

10. Drag Sales to the Rows box.

A single bar will appear representing Sales revenue for all Products across all Markets for the entire Year.

75 Lab 2: BSO Cube

11. Drag Gen2,MARKET to the Columns box.

Four bars will now appear representing Sales revenue for all Products for the entire Year by each Market Region.

76 Lab 2: BSO Cube

12. Drag Gen2,PRODUCT to the Color box.

The four bars turn to stacked bars with different colors representing each of the Product Lines. If you are not seeing the Product aliases, from the menu, go to Data | Alias File and select TBCAlias.

77 Lab 2: BSO Cube

13. Right-click on the Y-axis of the bar chart and select Add Reference Line. When the Reference Line dialog box appears, accept the default selections and click OK.

78 Lab 2: BSO Cube

An average line will appear representing the average Sales revenue for the Regions.

14. Drag Gen2,PRODUCT from the Color box to the Columns box to the right of Gen2,MARKET.

79 Lab 2: BSO Cube

The bar chart now represents Sales by Region and Product Line.

15. If you would like to see an average line across all Sales categories, right-click on one of the average lines and select Edit. In the Edit Reference Line dialog box, select the radio button for Entire Table and click OK.

80 Lab 2: BSO Cube

The average line will now represent the average for all the Sales categories.

81 Lab 2: BSO Cube

16. From the Measures panel drag Profit % to the Color box.

Each of the Sales bars will now turn to various shades of green, the darker the green the greater the Profit %. Note that in the West the Profit % of some Product Lines are relatively low despite the high Sales revenue. Further analysis could reveal the reasons for this anomaly.

82 Lab 2: BSO Cube

17. Now lets take a look at how Sales revenue gets impacted based on the amount of Marketing expenditures. First, remove Profit % by right-clicking on Profit % and selecting Remove. Next, remove the average line by rightclicking on it and selecting Remove.

18. Expand Total Expenses in the Measures panel and drag Marketing to the Columns box to the right of Gen2,PRODUCT.

83 Lab 2: BSO Cube

19. Drag Gen2,MARKET from the Columns box to the Color box.

20. Drag Gen2,PRODUCT from the Columns box to the Shape box.

84 Lab 2: BSO Cube

Your chart should now look similar to the one below. The marks on the chart represent the correlation between Marketing expenditures and Sales (as Marketing expenses increase, Revenue should also increase by some fixed factor). Each mark corresponds to a Region/Product Line combination. Color coding and the different shapes of the marks make it easy to identify which Region and Product Line the marks represent.

21. Adding a Trend Line will show the exact correlation between Sales and Marketing across all the data points. To add a Trend Line, right-click on a white area in the chart and select Trend Lines.

85 Lab 2: BSO Cube

A trend line will appear for each Region.

22. To show only one Trend Line, right-click on any Trend Line and select Edit Trend Lines. In the Trend Lines Options dialog box, uncheck Gen2,MARKET and click OK.

86 Lab 2: BSO Cube

You should now see one Trend Line. The marks below the Trend Line are the Region/Product Line combinations that are underperforming (where the Marketing expenses are high relative to Sales). The marks above the Line are overperformers (those where Sales are higher relative to their Marketing expenses).

23. To add more data points to the chart, drag Gen3,MARKET and Gen3,PRODUCT to the Level of Detail box.

87 Lab 2: BSO Cube

The chart should now look similar to the one below.

24. Move your mouse over one of the data points to get detailed information. Points below the trend line show below average sales relative to their marketing costs. Those below and to the far right of the trend line have extremely high marketing costs relative to the sales they are generating.

This concludes Lab 2. You may now close Visual Explorer and Excel. 88 Lab 2: BSO Cube

14 Shutting Down the VM

It is important that you shutdown your VM properly at the conclusion of each day. The correct shutdown procedure will ensure that the VM will function properly the next time you use it. 1. Close all client tools first, including Excel 2. Use the appropriate Shutdown scripts for each product you started (except for Essbase). All Shutdown scripts are included at the bottom of the Start Stop Services.txt file. Copy the appropriate script into a Terminal window to run. For shutting down multiple products, it is advised that you shut them down in the order listed on the file. For example, you should always stop Shared Services after all the Essbase products have been stopped.

3. Shut down Essbase by typing Exit or Quit in the terminal window it was started in. If you started any applications, it will ask if you would like to stop all the applications and exit Essbase. Type 1 and hit <Enter>. You should also stop Essbase before stopping Shared Services.

89 Lab 2: BSO Cube

5. When all the servers on the VM are stopped, you can shut down the VM by clicking on Actions at the top and selecting Log Out.

Select Shut down and click OK.

The VM will take a few minutes to shut down at that point. Never hit the X on your VMware program to shut down. This will place the VM in suspended mode and does not actually shut down the VM. When you turn your VM back on, it may behave abnormally. If this happens, shut down all servers and the VM properly and restart the VM.

90 Lab 2: BSO Cube