obiee 11gadmin tool

7/28/2019 OBIEE 11gAdmin Tool

1/387

Creating a Repository Using the Oracle BI 11gAdministration Tool

Purpose

This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool to build,modify, enhance, and manage an Oracle BI repository.

Time to Complete

Approximately 6 hours.

Overview

This tutorial shows you how to build an Oracle BI metadata repository using the Oracle BIAdministration Tool. You learn how to import metadata from data sources, simplify andreorganize the imported metadata into a business model, and then structure the business modelfor presentation to users who request business intelligence information via Oracle BI userinterfaces.

Prerequisites

Before starting this tutorial, you should:

1. Have access to or have Installed Oracle Business Intelligence Enterprise Edition 11g.

Please note: This tutorial is built using Oracle Business Intelligence Enterprise Edition

11.1.1.5. Due to product enhancements in 11.1.1.5, if you use an earlier version of the productto complete this tutorial, you will notice some differences in functionality:

New Diagramming Capability: The Physical and Business Model Diagrams have enhancedcapabilities in the 11.1.1.5 release, including an improved look-and-feel, the ability to displaycolumns in table objects in the diagram, and new diagram options like auto-layout, marqueezoom, and zoom to fit. Additionally, joins in the Physical and Business Model Diagrams arenow represented by a line with an arrow at the "one" end of the join, rather than the line withcrows feet at the "many" end of the join that was used in previous releases. When creatingjoins in the Physical and Business Model Diagrams, you now select the "many" end of the joinfirst, and then select the "one" end of the join. In previous releases, joins in the diagrams were

created by selecting the "one" end of the join first.

When setting up query logging, you must select Action > Set Online User Filter in IdentityManager to view users in the repository.

2. To complete this tutorial you must have access to the BISAMPLE schema that is included withthe Sample Application for Oracle Business Intelligence Suite Enterprise Edition Plus. There


2/387

are three options for accessing the BISAMPLE schema:

1. If you already have installed version 825 or V107 of the Sample Application, verify that youhave access to the BISAMPLE schema and begin the tutorial.

2. If you are interested in downloading and installing the complete Sample Application, you canaccess it here on the Oracle Technical Network (OTN). Please note, however, that only theBISAMPLE schema is required to complete this tutorial. If you want to install only theBISAMPLE schema, proceed to option 3.

3. Click here to access the ForOBE.7z file, which has the 825 version of the BISAMPLEschema and installation instructions. Save ForOBE.7z, unzip, and begin with READMEFIRST.txt.

Building the Physical Layer of a Repository

In this topic you use the Oracle BI Administration Tool to build the Physical layer of arepository.

The Physical layer defines the data sources to which Oracle BI Server submits queries and therelationships between physical databases and other data sources that are used to processmultiple data source queries. The recommended way to populate the Physical layer is byimporting metadata from databases and other data sources. The data sources can be of the sameor different varieties. You can import schemas or portions of schemas from existing datasources. Additionally, you can create objects in the Physical layer manually.

When you import metadata, many of the properties of the data sources are configuredautomatically based on the information gathered during the import process. After import, youcan also define other attributes of the physical data sources, such as join relationships, thatmight not exist in the data source metadata. There can be one or more data sources in thePhysical layer, including databases, flat files, XML documents, and so forth. In this example,you import and configure tables from the BISAMPLE schema included with the Oracle BI11gSample Application.

To build the Physical layer of a repository, you perform the following steps:

Create a New Repository Import Metadata Verify Connection Create Aliases Create Physical Keys and Joins


3/387

Create a New Repository

1. Select Start > Programs > Oracle Business Intelligence > BI Administration to open theAdministration Tool.

2. Select File > New Repository.


4/387

3. Enter a name for the repository. In this tutorial the repository name is BISAMPLE.


5/387

4. Leave the default location as is. It points to the default repository directory.

5. Leave Import Metadata set to Yes.

6. Enter and retype a password for the repository. In this tutorial BISAMPLE1 is the repositorypassword.


6/387

7 . Click Next.

Import Metadata

1 . Change the Connection Type to OCI 10g/11g. The screen displays connection fields based onthe connection type you selected.


7/387

2 . Enter a data source name. In this example the data source name is orcl. This name is the same

as the tnsnames.ora entry for this Oracle database instance.


8/387

3 . Enter a user name and password for the data source. In this example the username and

password are bothBISAMPLE. Recall that BISAMPLE is the name of the user/schema youcreated in the prerequisite section.


9/387

4 . Click Next.

5 . Accept the default metadata types and click Next.


10/387

6 . In the Data source view, expand the BISAMPLE schema.

7 . Use Ctrl+Click to select the following tables:

SAMP_ADDRESSES_DSAMP_CUSTOMERS_DSAMP_PRODUCTS_DSAMP_REVENUE_FSAMP_TIME_DAY_D


11/387

8 . Click the Import Selected button to add the tables to the Repository View.


12/387

9 . The Connection Pool dialog box appears. Accept the defaults and click OK.


13/387

10 .The Importing message appears.


14/387

11 .When import is complete, expand BISAMPLE in the Repository View and verify that the fivetables are visible.


15/387

12 .Click Finish to open the repository.


16/387

13 .Expand orcl > BISAMPLE and confirm that the five tables are imported into the Physicallayer of the repository.

Verify Connection

1 . Select Tools > Update All Row Counts.


17/387

2 . When update row counts completes, move the cursor over the tables and observe that rowcount information is now visible, including when the row count was last updated.

3 . Expand tables and observe that row count information is also visible for individual columns.


18/387

4 . Right-click a table and select View Data to view the data for the table.


19/387

5 . Close the View Data dialog box when you are done. It is a good idea to update row counts or

view data after an import to verify connectivity. Viewing data or updating row count, ifsuccessful, tells you that your connection is configured correctly.


20/387

Create Aliases

1 . It is recommended that you use table aliases frequently in the Physical layer to eliminateextraneous joins and to include best practice naming conventions for physical table names.Right-click SAMP_TIME_DAY_D and selectNew Object > Alias to open the Physical Tabledialog box.

2 . Enter D1 Time in the Name field.


21/387

3 . In the Description field, enter Time Dimension Alias at day grain. Stores one record foreach day.


22/387

4 . Click the Columns tab. Note that alias tables inherit all column definitions from the sourcetable.


23/387

5 . Click OK to close the Physical Table dialog box.

6 . Repeat the steps and create the following aliases for the remaining physical tables.

SAMP_ADDRESSES_D = D4 Address

SAMP_CUSTOMERS_D = D3 CustomerSAMP_PRODUCTS_D = D2 ProductSAMP_REVENUE_F = F1 Revenue


24/387

Create Keys and Joins

1 . Select the five alias tables in the Physical layer.

2 . Right-click one of the highlighted alias tables and select Physical Diagram > SelectedObject(s) Only to open the Physical Diagram. Alternatively, you can click the PhysicalDiagram button on the toolbar.


25/387

3 . Rearrange the alias table objects so they are all visible.


26/387

4 . You may want to adjust the objects in the Physical Diagram. If so, use the toolbar buttons tozoom in, zoom out, fit the diagram, collapse or expand objects, select objects, and so forth:

5 . Click the New Join button on the toolbar.

6 . Click the F1 Revenue table and then the D1 Time table. The Physical Foreign Key dialog boxopens. It matters which table you click first. The join creates a one-to-many (1:N) relationshipthat joins the key column in the first table to a foreign key column in the second table.


27/387

7 . Select the D1 Time. CALENDAR_DATE column, and then select F1Revenue.BILL_DAY_DT to join the tables. Ensure that the Expression edit box (at thebottom) contains the following expression:

"orcl".""."BISAMPLE"."D1 Time"."CALENDAR_DATE" ="orcl".""."BISAMPLE"."F1 Revenue"."BILL_DAY_DT"


28/387

8 . Click OK to close the Physical Foreign Key dialog box. The join is visible in the PhysicalDiagram.


29/387

Please be aware of the following upgrade considerations for Oracle BI EE 11g Release 1(11.1.1.5): Joins in the Physical and Business Model diagrams are now represented by a line

with an arrow at the "one" end of the join, rather than the line with crows feet at the "many"end of the join that was used in previous releases. When creating joins in the Physical andBusiness Model Diagrams, you now select the "many" end of the join first, and then select the"one" end of the join. In previous releases, joins in the diagrams were created by selecting the"one" end of the join first.

9 . Repeat the steps to create joins for the remaining tables. Use the following expressions as aguide. Please notice that D4 Address joins to D3 Customer.

"orcl".""."BISAMPLE"."D2 Product"."PROD_KEY" = "orcl".""."BISAMPLE"."F1Revenue"."PROD_KEY"

"orcl".""."BISAMPLE"."D3 Customer"."CUST_KEY" = "orcl".""."BISAMPLE"."F1Revenue"."CUST_KEY"

"orcl".""."BISAMPLE"."D4 Address"."ADDRESS_KEY" = "orcl".""."BISAMPLE"."D3


30/387

Customer"."ADDRESS_KEY"

10 .Click the Auto Layout button on the toolbar.

11 .Your diagram should look similar to the screenshot:.

12 .Click the X in the upper right corner to close the Physical Diagram.

13 .Select File > Save or click the Save button on the toolbar to save the repository.


31/387

14 .Click No when prompted to check global consistency. Checking Global Consistency checks forerrors in the entire repository. Some of the more common checks are done in the BusinessModel and Mapping layer and Presentation layer. Since these layers are not defined yet, bypassthis check until the other layers in the repository are built. You learn more about consistencycheck later in this tutorial.

15 .Leave the Administration Tool and the repository open for the next topic.

Congratulations! You have successfully created a new repository, imported a table schemafrom an external data source into the Physical layer, created aliases, and defined keys and joins.

In the next topic you learn how to build the Business Model and Mapping layer of a repository.

Building the Business Model and Mapping Layer of a Repository


32/387

In this topic you use the Oracle BI Administration Tool to build the Business Model andMapping layer of a repository.

The Business Model and Mapping layer of the Administration Tool defines the business, orlogical, model of the data and specifies the mappings between the business model and thePhysical layer schemas. This layer is where the physical schemas are simplified to form thebasis for the users view of the data. The Business Model and Mapping layer of theAdministration Tool can contain one or more business model objects. A business model objectcontains the business model definitions and the mappings from logical to physical tables for thebusiness model.

The main purpose of the business model is to capture how users think about their businessusing their own vocabulary. The business model simplifies the physical schema and maps theusers business vocabulary to physical sources. Most of the vocabulary translates into logicalcolumns in the business model. Collections of logical columns form logical tables. Each logicalcolumn (and hence each logical table) can have one or more physical objects as sources.

There are two main categories of logical tables: fact and dimension. Logical fact tables containthe measures by which an organization gauges its business operations and performance.Logical dimension tables contain the data used to qualify the facts.

To build the Business Model and Mapping layer of a repository, you perform the followingsteps:

Create a Business Model Examine Logical Joins Examine Logical Columns Examine Logical Table Sources Rename Logical Objects Manually Rename Logical Objects Using the Rename Wizard Delete Unnecessary Logical Objects Create Simple Measures

Create a Business Model

1. Right-click the white space in the Business Model and Mapping layer and select New BusinessModel to open the Business Model dialog box.


33/387

2. Enter Sample Sales in the Name field. Leave Disabled checked.


34/387

3. Click OK. The Sample Sales business model is added to the Business Model and Mapping layer.

4. In the Physical layer, select the following four alias tables:


35/387

D1 TimeD2 ProductD3 CustomerF1 Revenue

Do not select D4 Address at this time.

5 . Drag the four alias table from the Physical layer to the Sample Sales business model in theBusiness Model and Mapping layer. The tables are added to the Sample Sales business model.Notice that the three dimension tables have the same icon, whereas the F1 Revenue table hasan icon with a # sign, indicating it is a fact table.


36/387

Examine Logical Joins

1. Right-click the Sample Sales business model and select Business Model Diagram > WholeDiagram to open the Business Model Diagram.

2 . If necessary, rearrange the objects so that the join relationships are visible.

Because you dragged all tables simultaneously from the Physical layer onto the business model,the logical keys and joins are created automatically in the business model. This is because the


37/387

keys and join relationships were already created in the Physical layer. However, you typicallydo not drag all physical tables simultaneously, except in very simple models. Later in thistutorial, you learn how to manually build logical keys and joins in the Business Model andMapping layer. The process is very similar to building joins in the Physical layer.

3. Double-click any one of the joins in the diagram to open the Logical Join dialog box. In thisexample the join between D1 Time and F1 Revenue is selected.

Notice that there is no join expression. Joins in the BMM layer are logical joins. Logical joinsexpress the cardinality relationships between logical tables and are a requirement for a validbusiness model. Specifying the logical table joins is required so that Oracle BI Server hasnecessary metadata to translate logical requests against the business model into SQL queriesagainst the physical data sources. Logical joins help Oracle BI Server understand therelationships between the various pieces of the business model. When a query is sent to OracleBI Server, the server determines how to construct physical queries by examining how thelogical model is structured. Examining logical joins is an integral part of this process. TheAdministration Tool considers a table to be a logical fact table if it is at the many end of alllogical joins that connect it to other logical tables.


38/387

4 . Click OK to close the Logical Join dialog box.

5 . Click the X to close the Business Model Diagram.

Examine Logical Columns

1 . Expand the D1 Time logical table. Notice that logical columns were created automatically foreach table when you dragged the alias tables from the Physical layer to the BMM layer.

Examine Logical Table Sources

1 . Expand the Sources folder for the D1 Time logical table. Notice there is a logical table source,D1 Time. This logical table source maps to the D1 Time alias table in the Physical layer.


39/387

2 . Double-click the D1 Time logical table source (not the logical table) to open the Logical TableSource dialog box.


40/387

3 . On the General tab, rename the D1 Time logical table source to LTS1 Time. Notice that thelogical table to physical table mapping is defined in the "Map to these tables" section.


41/387

4 . On the Column Mapping tab, notice that logical column to physical column mappings aredefined. If mappings are not visible, select Show mapped columns.


42/387

5 . You learn more about the Content and Parent-Child Settings tabs later in this tutorial whenyou build logical dimension hierarchies. Click OK to close the Logical Table Source dialog box.If desired, explore logical table sources for the remaining logical tables.


43/387

Rename Logical Objects Manually

1. Expand the D1 Time logical table.


44/387

2. Click on the first logical column, BEG_OF_MONTH_WID, to highlight it.

3. Click on BEG_OF_MONTH_WID again to make it editable.


45/387

4 . Rename BEG_OF_MONTH_WID to Beg of Mth Wid. This is the manual method forrenaming objects. You can also right-click an object and select Rename to manually rename anobject.

Rename Objects Using the Rename Wizard1 . Select Tools > Utilities > Rename Wizard > Execute to open the Rename Wizard.

2 . In the Select Objects screen, click Business Model and Mapping in the middle pane.


46/387

3 . Expand the Sample Sales business model.


47/387

4 . Expand the D1 Time logical table.

5 . Use Shift+click to select all of the logical columns except for the column you alreadyrenamed, Beg of Mth Wid.


48/387

6 . Click Add to add the columns to the right pane.


49/387

7 . Repeat the steps for the three remaining logical tables so that all logical columns from theSample Sales business model are added to the right pane. Only the columns from F1 Revenueare shown in the screenshot.


50/387

8 . Click Next to move to the Select Types screen.


51/387

Notice that Logical Column is selected. If you had selected other object types, such as logicaltables, the type would have appeared here.

9 . Click Next to open the Select Rules screen.


52/387

10 . In the Select Rules screen, select All text lowercase and click Add to add the rule to the lowerpane.


53/387

11 .Add the rule Change each occurrence of '_' into a space.


54/387

12 .Add the rule First letter of each word capital.

13 .Click Next to open the Finish screen. Verify that all logical columns will be named accordingto the rename rules you selected.


55/387

14 .Click Finish.

15 . In the Business Model and Mapping layer, expand the logical tables and confirm that alllogical columns have been renamed as expected. The screenshot shows only the columns in D1Time.


56/387

16 . In the Physical layer, expand the alias tables and confirm that all physical columnshave notbeen renamed. The point here is you can change object names in the BMM layerwithout impacting object names in the Physical layer. When logical objects are renamed, therelationships between logical objects and physical objects are maintained by the logical columnto physical column mappings.


57/387

Delete Unnecessary Logical Objects

1 . In the BMM layer, expand Sample Sales > F1 Revenue.


58/387

2 . Use Ctrl+Click to select all F1 Revenue logical columns except for Revenue and Units.


59/387

3 . Right-click any one of the highlighted logical columns and select Delete. Alternatively you canselect Edit > Delete or press the Delete key on your keyboard.


60/387

4 . Click Yes to confirm the delete.

5 . Confirm that F1 Revenue contains only the Revenue and Units columns.


61/387

Create Simple Measures

1 . Double-click the Revenue logical column to open the Logical Column dialog box.

2 . Click the Aggregation tab.


62/387

3 . Change the default aggregation rule to Sum.


63/387

4 . Click OK to close the Logical Column dialog box. Notice that the icon has changed for theRevenue logical column indicating that an aggregation rule has been applied.

5 . Repeat the steps to define the SUM aggregation rule for the Units logical column.


64/387

Measures are typically data that is additive, such as total dollars or total quantities. The F1Revenue logical fact table contains the measures in your business model. You aggregated twological columns by summing the column data.

6 . Save the repository without checking global consistency.

Congratulations! You have successfully built a business model in the Business Model andMapping layer of a repository and created business measures.

Building the Presentation Layer of a Repository

You have created the initial Sample Sales business model in the repository. You now create thePresentation layer of the repository. The Presentation layer exposes the business model objectsin Oracle BI user interfaces so that users can build analyses and dashboards to analyze theirdata.

To build the Presentation layer you perform the following steps:

Create a Subject Area Create Presentation Tables Create Presentation Columns Rename Presentation Columns Reorder Presentation Columns

Create a Subject Area

1 . Right-click the hite space in the Presentation layer and select New Subject Area to open theSubject Area dialog box.


65/387

2 . On the General tab, enter Sample Sales as the name of the subject area.


66/387

3 . Click OK to close the Subject Area dialog box. The Sample Sales subject area is added to thePresentation layer.

Create Presentation Tables

1. Right-click the Sample Sales subject area and select New Presentation Table to open thePresentation Table dialog box.

2. On the General tab, enter Time as the name of the presentation table.


67/387

3 . Click OK to close the Presentation Table dialog box. The Time presentation table is added tothe Sample Sales subject area.

4 . Repeat the process and add three more presentation tables: Products, Customers, and BaseFacts.

Please note that you are using the manual method for creating Presentation layer objects. Forsimple models it is also possible to drag objects from the BMM layer to the Presentation layerto create the Presentation layer objects. When you create presentation objects by dragging


68/387

from the BMM layer, the business model becomes a subject area, the logical tables becomepresentation tables, and the logical columns become presentation columns. Note that all objectswithin a subject area must derive from a single business model.

Create Presentation Columns

1. In the BMM layer, expand the D1 Time logical table.

2. Use Ctrl+ Click to select the following logical columns:

Calendar DatePer Name HalfPer Name MonthPer Name QtrPer Name WeekPer Name Year.


69/387

3 . Drag the selected logical columns to the Time presentation table in the Presentation layer.


70/387

4 . Repeat the process and add the following logical columns to the remaining presentation tables:

Products: Drag Brand, Lob, Prod Dsc, Type from D2 Product.

Customers: Drag Cust Key, Name from D3 Customer.

Base Facts: Drag Revenue, Units from F1 Revenue.

Rename Presentation Columns

1. In the Presentation layer, expand the Products presentation table.


71/387

2. Double-click the Lob presentation column to open the Presentation Column dialog box. On theGeneral tab notice that "Use Logical Column Name" is selected. When you drag a logicalcolumn to a presentation table, the resulting presentation column inherits the logical columnname by default. In this example the Lob presentation column inherits the name of the logicalcolumn "Sample Sales"."D2 Product"."Lob".

3 . Deselect Use Logical Column Name. The Name field is now editable.


72/387

4 . Enter Line of Business in the Name field.


73/387

5 . Click OK to close the Presentation Column dialog box. Notice that the presentation columnname is now changed to Line of Business in the Presentation layer.

6 . In the BMM layer, expand D2 Product. Notice that the Lob logical column name is not

changed. The point here is you can change object names in the Presentation layer withoutimpacting object names in the BMM or Physical layers.

7 . In the BMM layer, rename the Prod Dsc logical column to Product. Notice that the namechange is inherited by the corresponding presentation column.


74/387

8 . Make the following name changes to logical objects in the BMM layer so that the names of thecorresponding presentation columns are also changed:

For the D3 Customer logical table:

Change Cust Key to Customer Number.

Change Name to Customer Name.


75/387

9 . Confirm that the corresponding presentation column names are changed.

Reorder Presentation Columns


76/387

1. In the Presentation layer, double-click the Time presentation table to open the PresentationTable dialog box.

2. Click the Columns tab.


77/387

3 . Select columns and use the up and down arrows, or drag the columns. to rearrange thepresentation columns into the following order from top to bottom:

Per Name YearPer Name HalfPer Name QtrPer Name MonthPer Name WeekCalendar Date


78/387

4 . Click OK to close the Presentation Table dialog box and confirm that the presentation columnorder is changed in the Presentation layer.

5 . Repeat the steps to reorder the columns in the Products presentation table:

BrandLine of BusinessTypeProduct


79/387

6 . Save the repository without checking global consistency.

Congratulations! You have successfully built the Presentation layer of a repository.

Testing and Validating a Repository

You have finished building an initial business model and now need to test and validate therepository before continuing. You begin by checking the repository for errors using theconsistency checking option. Next you load the repository into Oracle BI Server memory. Youthen test the repository by running an Oracle BI analysis and verifying the results. Finally, youexamine the query log file to observe the SQL generated by Oracle BI Server.

To test and validate a repository you perform the following steps:

Check Consistency

Disable Caching

Load the Repository Set Up Query Logging Create and Run and Analysis Check the Query Log

Check Consistency

1. Select File > Check Global Consistency.


80/387

2. You should receive the message Business model "Sample Sales" is consistent. Do you wantto mark it as available for queries?

3 . Click Yes. You should receive the message: Consistency check didn't find any errors,warnings or best practice violations.


81/387

If you do not receive this message, you must fix any consistency check errors or warningsbefore proceeding.

4 . Click OK. Notice that the Sample Sales business model icon in the BMM layer is now green,indicating it is available for queries.

5 . Save the repository without checking global consistency again.

6 . Select File > Close to close the repository. Leave the Administration Tool open.

Disable Caching


82/387

1. Open a browser and enter the following URL to navigate to Enterprise Manager FusionMiddleware Control:

http://:7001/em

In this tutorial the URL is http://localhost:7001/em

2. Log in as an administrative user. Typically you use the administrative user name and passwordprovided during the Oracle BI installation. In this example the user name is weblogic.

3 . In the left navigation pane, expand Business Intelligence and click coreapplication.

4 . Click the Capacity Management tab.


83/387

5 . Click the Performance sub tab.

6 . Locate the Enable BI Server Cache section. Cache is enabled by default.

7 . Click Lock and Edit Configuration.

8 . Click Close when you receive the confirmation message "Lock and Edit Configuration -Completed Successfully."


84/387

9 . Deselect Cache enabled. Caching is typically not used during development. Disabling cacheimproves query performance.

10 .Click Apply.


85/387

11 .Click ActivateChanges.

12 .Click Close when you receive the confirmation message Activate Changes - CompletedSuccessfully.

13 .Do not click Restart to apply recent changes yet. You do that after uploading the repositoryin the next set of steps.


86/387

Load the Repository

1. Click the Deployment tab.

2 . Click the Repository sub tab.


4 . Click Close when you receive the confirmation message "Lock and Edit Configuration -Completed Successfully."


87/387

5 . In the "Upload BI Server Repository" section, click Browse to open the Choose file dialog box.

6 . By default, the Choose file dialog box should open to the repository directory. If not, navigateto the repository directory with the BISAMPLE repository.


88/387

7 . Select the BISAMPLE.rpd file and click Open.


89/387

8 . Enter BISAMPLE1 as the repository password and confirm the password.

9 . Click Apply.


90/387

10 . In the BI Server Repository section, confirm that the Default RPD is now BISAMPLE with an

extension. In this example the file name is BISAMPLE_BI0025.


91/387



92/387

12 .Click Close when you receive the confirmation message Activate Changes - Completed

Successfully.

13 .Click Restart to apply recent changes to navigate to the Overview page.


93/387

14 .On the Overview page, click Restart.

15 .Click Yes when you receive the message Are you sure you want to restart all BI


94/387

components?

16 .Allow the Restart All processing to complete. This may take a few moments.

17 .Click Close when you receive the confirmation message Restart All - CompletedSuccessfully.

18 .Confirm that System Components are 100% and that five components are up. Leave FusionMiddleware Control open.


95/387

Set Up Query Logging

1 . Return to the Administration Tool, which should still be open.

2 . Select File > Open > Online to open the repository in online mode. You use online mode toview and modify a repository while it is loaded into the Oracle BI Server. The Oracle BI Server

must be running to open a repository in online mode.

3 . Enter BISAMPLE1 as the repository password and enter your administrative user name andpassword.


96/387

4 . Click Open to open the repository in online mode.

5 . Select Manage > Identity to open Identity Manager.


97/387

6 . In the left pane, select BI Repository.

7 . Select Action > Set Online User Filter.


98/387

8 . Enter an asterisk and click OK to fetch users from the identity store.


99/387

9 . In the right pane, double-click your administrative user to open the User dialog box. In thisexample the administrative user is weblogic.

10 . In the User dialog box, on the User tab, set Logging level to 2.

11 .Click OK to open the Check Out Objects dialog box.


100/387

12 . In the Check Out Objects dialog box, click Check Out. When you are working in a repositoryopen in online mode, you are prompted to check out objects when you attempt to performvarious operations.

13 .Select Action > Close to close Identity Manager.

14 .Select File > Check In Changes. Alternatively, you can click the Check In Changes icon onthe toolbar.


101/387

15 .Save the repository. There is no need to check consistency.

16 .Select File > Copy As to save a copy of the online repository with the security changes.


102/387

17 . In the Save Copy As dialog box, save the file as BISAMPLE.rpd, replacing the existingBISAMPLE repository.

18 .Click Yes when asked if you want to replace the existing BISAMPLE repository. This willcreate a new BISAMPLE repository with query logging set for the weblogic user.


103/387

19 .Select File > Close to close the repository.

20 .Click OK when you receive the following message:

"In order for your online changes to take effect, you will have to manually restart each non-master Oracle BI Server instance in the cluster."


104/387

21 .Leave the Administration Tool open.

Create and Run an Analysis

1. Open a browser or a new browser tab and enter the following URL to navigate to OracleBusiness Intelligence:

http://:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics

2. Sign in as an administrative user. Typically you use the administrative user name and passwordprovided during the Oracle BI installation. In this example the user name is weblogic. If youneed help identifying a user name and password, contact your company's Oracle BIAdministrator.


105/387

3 . In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.

4 . Select the Sample Sales subject area.

5 . In the left navigation pane, expand the folders in the Sample Sales subject area and confirm thatthe user interface matches the presentation layer of the repository.


106/387

6 . Double-click the following column names in the Subject Areas pane to add them to theanalysis:

Time.Per Name YearProducts.TypeBase Facts.Revenue


107/387

7 . Click Results.

8 . The analysis results are displayed in a compound layout, which includes a Title view and aTable view.


108/387

9 . Use the buttons at the bottom of the compound layout to view additional rows.


109/387

Check the Query Log

1 . Return to Fusion Middleware Control, which should still be open. If not, enterhttp://localhost:7001/em in a browser and sign in as your administrative user.

2 . Click the Diagnostics tab.


110/387

3 . Click the Log Messages sub tab.

4 . Scroll to the bottom of the window to the View / Search Log Files section.


111/387

5 . Click Server Log to navigate to the Log Messages screen.

6 . In the Log Messages screen, leave the data range set to Most Recent, 1 Days. Deselect allmessage types except for Trace.


112/387

7 . In the Message field, enter sending query to database.

8 . Click Search.

9 . There should be only one message at this point, but if there are more than one, select the lastmessage in the list. This is the most recent query sent to the database.


113/387

10 . In the bottom pane, click the Collapse Pane button (arrow on the right side) to view the logmessage. Your results should look similar to the screenshot.

11 .Click the Restore Pane button. Throughout this tutorial, you return to this view to check thequery log.

12 .Leave Fusion Middleware Control open.


114/387

Managing Logical Table Sources

In this set of steps you create multiple logical table sources for the D3 Customer logical table.To create multiple logical table sources you perform the following steps:

Open the Repository in Offline Mode

Add a New Logical Table Source Create Presentation Layer Objects Load the Repository Create and Run an Analysis Check the Query Log


1 . Return to the Administration Tool, which should still be open. If not, select Start > Programs> Oracle Business Intelligence > BI Administration.

2 . Open the BISAMPLE repository in offline mode with repository password is BISAMPLE1.Recall that earlier in this tutorial you created a copy of the online repository and saved it asBISAMPLE.rpd.

3 . Select Manage > Identity to open Identity Manager.

4 . Select BI Repository in the left pane.


115/387

5 . Recall that earlier in this tutorial you created a copy of the online repository with logging leveldefined for the administrative user. Confirm that your administrative user is visible in the rightpane. In this example the administrative user is weblogic.

6 . Double-click the administrative user to open the User dialog box. On the User tab, confirm


116/387

that logging level is set to 2.

7 . Click Cancel to close the User dialog box.

8 . Select Action > Close to close Identity Manager. The offline BISAMPLE repository now hasa user with a logging level set to 2. This will allow you to check the query log as you completethe remaining exercises in this tutorial. You will not have to repeat the steps of copying anonline repository.

Add a New Logical Table Source

1 . In the BMM layer, expand Sample Sales> D3 Customer > Sources. Notice that the D3Customer logical table has one logical table source named D3 Customer.


117/387

2 . Rename the D3 Customer logical table source (not the logical table) to LTS1 Customer.


118/387

3 . Double-click LTS1 Customer to open the Logical Table Source dialog box.

4 . Click the Column Mapping tab and notice that all logical columns map to physical columns inthe same physical table: D3 Customer. It may be necessary to scroll to the right to see thePhysical Table column. Make sure "Show mapped columns" is selected.


119/387

5 . Click OK to close the Logical Table Source dialog box.

6 . In the Physical layer, expand orcl > BISAMPLE.


120/387

7 . Drag D4 Address from the Physical layer to the D3 Customer logical table in the BMMlayer. Notice this creates a new logical table source named D4 Address for the D3 Customerlogical table. It also creates new logical columns that map to the D4 Address physical table.


121/387

8 . In the BMM layer, double-click the new D4 Address logical table source to open the LogicalTable Source dialog box.


122/387

9 . On the General tab, enter LTS2 Customer Address in the Name field.


123/387

10 .Click the Column Mapping tab and notice that all logical columns map to physical columns inthe same physical table: D4 Address. If necessary, select Show mapped columns anddeselect Show unmapped columns.


124/387

11 .Click OK to close the Logical Table Source dialog box.


125/387

12 .Confirm that the D3 Customer logical table now has two logical table sources: LTS1Customer and LTS2 Customer Address. A single logical table now maps to two physicalsources.


126/387

13 .Right-click the new ADDRESS_KEY column and select Delete. This is a duplicate columnand is not needed.

14 .Click Yes to confirm the delete.

15 .Use the Rename Wizard or a manual renaming technique to rename the new address logicalcolumns (with uppercase letters) in D3 Customer. Your results should look similar to the


127/387

screenshot. Hint: To use the Rename Wizard, select all of the new logical columns, then right-click any one of the highlighted columns and select Rename Wizard to launch the wizard. Ifyou need help using the Rename Wizard, refer to these steps from earlier in this tutorial.

16 .Rename the remaining logical table sources according to the following table. Recall that logicaltable sources are located in the Sources folder for a logical table. For example: D2 Product >Sources.

Logical Table Source Rename

D2 Product LTS1 Product


128/387

F1 Revenue LTS1 Revenue

Your results should look similar to the screenshot.

Create Presentation Layer Objects

1 . In the Presentation layer, right-click the Sample Sales subject area and select NewPresentation Table to open the Presentation Table dialog box.


129/387

2 . On the General tab, enter Customer Regions in the Name field.


130/387

3 . Click OK to close the Presentation Table dialog box. Confirm that the Customer Regionspresentation table is added to the Sample Sales subject area in the Presentation layer.

4 . In the BMM layer, expand Sample Sales > D3 Customer.


131/387

5 . Drag the following logical columns from D3 Customer to Customer Regions in thePresentation layer:

Address 1Address 2AreaCityCountry NameEstab NamePostal CodeRegion


132/387

State ProvinceState Province Abbrv

Your column names may be slightly different depending on how you renamed them.

6 . Reorder the Customer Regions presentation columns in the following order, from top tobottom:

RegionAreaCountry Name


133/387

State ProvinceState Province AbbrvCityPostal CodeAddress 1

Address 2Estab Name

7 . Double-click the Sample Sales subject area in the Presentation layer to open the Subject Areadialog box.


134/387

8 . Click the Presentation Tables tab.


135/387

9 . Reorder the presentation tables so that Customer Regions appears after Customers.

10 .Click OK to close the Subject Area dialog box. Confirm that the presentation tables appear inthe expected order.

You now have two presentation tables, Customers and Customer Regions, mapped to the samelogical table, D3 Customer. The D3 Customer logical table is mapped to two physical sources:

D3 Customer and D4 Address.

11 .Save the repository and check global consistency when prompted. You should receive amessage that there are no errors, warnings, or best practice violations to report.


136/387

If you do receive any consistency check errors or warnings, fix them before proceeding.

12 .Click OK to close the consistency check message.

13 .Close the repository. Leave the Administration Tool open.

Load the Repository

1. Return to Fusion Middleware Control, which should still be open. If not, open a browser andenter the following URL to navigate to Fusion Middleware Control:

http:///:7001/em


2. If your session has timed out, you will need to log in again. Log in as an administrative user.Typically you use the administrative user name and password provided during the Oracle BIinstallation. In this example the user name is weblogic.

3 . In the left navigation pane, expand Business Intelligence and click coreapplication.


137/387

4 . Click the Deployment tab.




138/387

7 . Click Close when you receive the confirmation message Lock and Edit Configuration -Completed Successfully.

8 . Click Browse and navigate to the directory with the BISAMPLE repository.



139/387

10 .Enter BISAMPLE1 as the repository password and confirm the password.

11 .Click Apply.


140/387

12 .Confirm that the default RPD is now BISAMPLE with an extension. In this example the file

name isBISAMPLE_BI0025.


141/387



142/387


Successfully.



143/387




144/387

components?

18 .Allow the processing to complete.

19 .Click Close when you receive the message Restart All - Completed Successfully.


1. Return to Oracle BI, which should still be open. If not, open a browser or browser tab andenter the following URL to navigate to Oracle Business Intelligence:

http:///:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics.

2. If your previous session has timed out, sign in as an administrative user. Typically you use theadministrative user name and password provided during the Oracle BI installation. In thisexample the user name is weblogic.


145/387

3 . In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.



146/387

5 . In the left navigation pane, expand the folders and confirm that the Customer Regions folderand corresponding columns appear.

6 . Create the following analysis by double-clicking column names in the Subject Areas pane:

Customer Regions.RegionCustomers.Customer NameProducts.Type

Base Facts.Revenue

7 . Click Results to view the analysis results. Use the buttons at the bottom of the results screen


147/387

to see more rows.

Check the Query Log1 . Return to Fusion Middleware Control, which should still be open.

2 . Click the Diagnostics tab.


148/387

3 . Click the Log Messages sub tab.

4 . Scroll to the bottom of the window to the View / Search Log Files section.


149/387

5 . Click Server Log to navigate to the Log Messages screen.

6 . In the Log Messages screen, leave the data range set to Most Recent, 1 Days. Deselect allmessage types except for Trace.

7 . In the Message field, enter sending query to database.


150/387

8 . Click Search.

9 . Select the last message in the list. This is the most recent query sent to the database.

10 . In the bottom pane, click the Collapse Pane button (arrow on the right side) to view the logmessage. Your results should look similar to the screenshot. The screenshot shows only apartial view of the log.

Notice that both D3 Customer and D4 Address are accessed. The presentation columnsincluded in the analysis were selected from two different presentation tables: Customers andCustomer Regions. Both of these presentation tables map to the same logical table, D3Customer. The D3 Customer logical table maps to two physical sources: D3 Customer and D4Address.


151/387

11 .Click the Restore Pane button.

12 .Leave Enterprise Manager open.

Creating Calculation Measures

In this set of steps you use existing measures to created a derived calculation measure. Tocreate a derived calculation measure you perform the following steps:

Open the Repository in Offline Mode Create a Calculation Measure Derived from Existing Columns Create a Calculation Measure Using a Function Load the Repository Create and Run an Analysis Check the Query Log


1 . Return to the Administration Tool, which should still be open. If not, select Start > Programs

> Oracle Business Intelligence > BI Administration.

2 . Select File > Open > Offline.

3 . Select BISAMPLE.rpd and click Open. Do not select any BISAMPLE repository with an


152/387

extension, for example, BISAMPLE_BI0025.rpd. Recall that these are the repositories thathave been loaded into Oracle BI Server memory.

4 . Enter BISAMPLE1 as the repository password and click OK to open the repository.

Create a Calculation Measure Derived from Existing Columns

1 . In the BMM layer, expand Sample Sales > F1 Revenue.


153/387

2 . Right-click F1 Revenue and select New Object > Logical Column to open the LogicalColumn dialog box.

3 . On the General tab, enter Actual Unit Price in the Name field.


154/387

4 . Click the Column Source tab.


155/387

5 . Select Derived from existing columns using an expression.


156/387

6 . Click the Edit Expression button to open Expression Builder.


157/387

7 . In the left pane select Logical Tables > F1 Revenue > Revenue.


158/387

8 . Click the Insert selected item button to move the Revenue column to the right pane.


159/387

9 . Click the division operator to add it to the expression.


160/387

10 . In the left pane select Logical Tables > F1 Revenue and then double-click Units to add it tothe expression.


161/387

11 .Click OK to close Expression Builder. Notice that the formula is added to the Logical Columndialog box.


162/387

12 .Click OK to close the Logical Column dialog box. The Actual Unit Price calculated measureis added to the business model.

13 .Drag Actual Unit Price from the BMM layer to the Base Facts presentation table in thePresentation layer.


163/387

14 .Save the repository and check consistency. Fix any errors or warnings before proceeding.

Create a Calculation Measure Using a Function

1 . In the BMM layer, right-click F1 Revenue and select New Object > Logical Column to openthe Logical Column dialog box.


164/387

2 . On the General tab, enter Revenue Rank in the Name field.



165/387



166/387

5 . Click the Edit Expression button to open Expression Builder.


167/387

6 . In the left pane select Functions > Display functions > Rank .


168/387

7 . Click the Insert selected item button to move the Rank function to the right pane.


169/387

8 . Click in the expression.


170/387

9 . In the left pane select Logical Tables > F1 Revenue and then double-click Revenue to add itto the expression.


171/387

10 .Click OK to close Expression Builder. Notice that the formula is added to the Logical Columndialog box.


172/387

11 .Click OK to close the Logical Column dialog box. The Revenue Rank calculated measure isadded to the business model.

12 .Drag Revenue Rank from the BMM layer to the Base Facts presentation table in thePresentation layer.


173/387

13 .Save the repository and check consistency. Fix any errors or warnings before proceeding.

14 .Close the repository. Leave the Admin Tool open.

Load the Repository1. Return to Fusion Middleware Control, which should still be open. If not, open a browser and

enter the following URL to navigate to Fusion Middleware Control Enterprise Manager:

http:///:7001/em


2. If necessary, log in as an administrative user. Typically you use the administrative user nameand password provided during the Oracle BI installation. In this example the user name is

weblogic.


174/387

3 . In the left navigation pane, expand Business Intelligence and click on coreapplication.

4 . Click the Deployment tab.



175/387


7 . Click Close when you receive the confirmation message Lock and Edit Configuration -Completed Successfully.

8 . Click Browse and navigate to the directory with the BISAMPLE repository.


176/387


10 .Enter BISAMPLE1 as the repository password and confirm the password.

11 .Click Apply.


177/387

12 .Confirm that the default RPD is now BISAMPLE with an extension. In this example the file

name isBISAMPLE_BI0025.


178/387



179/387


Successfully.



180/387




181/387

components?

18 .Allow the processing to complete.

19 .Click Close when you receive the message Restart All - Completed Successfully.


1. Return to Oracle BI, which should still be open. If not, open a browser or browser tab andenter the following URL to navigate to Oracle Business Intelligence:

http:///:7001/analytics

In this tutorial the URL is http://localhost:7001/analytics.

2. If necessary, log in as an administrative user. Typically you use the administrative user nameand password provided during the Oracle BI installation. In this example the user name isweblogic.


182/387

3 . In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.Hint: If your session has not timed out, you can create a new analysis by selecting New >Analysis.


5 . In the left navigation pane, expand the Base Facts folder and confirm that the Actual UnitPrice and Revenue Rankcolumns are visible.

6 . Create the following analysis by double-clicking column names in the Subject Areas pane:

Products.Product

Base Facts.RevenueBase Facts.Revenue RankBase Facts.UnitsBase Facts.Actual Unit Price

7 . Sort Revenue Rank in ascending order.


183/387

8 . Click Results to view the analysis results.

Please note that the Actual Unit Price calculation is correct, although it does not make sensefrom a business perspective. For example, the unit price for an LCD HD Television would notbe 9 dollars. This is a result of the underlying sample data.

Check the Query Log1 . In this set of steps you use another method to check the query log. Clickthe Administration link in the upper right.


184/387

1 . Click OK when you are asked "are you sure you want to navigate away from this page?"

1 . On the Administration page, under Session Management, select Manage Sessions.

1 . In the Cursor Cache section, locate your query and select View Log.

2 . Your log entry should look similar to the screenshot.


185/387

Note that the division of Revenue by Units is calculated in the outer query block (D1.c2 / nullif( D1.c1, 0) as c3 in this example). Because you defined the Actual Unit Price calculation usinglogical columns, the SUM aggregation rule is applied to the Revenue and Units columns firstand then the division is calculated.

3 . Click the browser back button to return to the Administration screen.

4 . Sign out of Oracle BI.

Creating Logical Dimensions with Level-Based Hierarchies

In this set of steps you add logical dimension hierarchies to the business model. A logicaldimension represents a hierarchical organization of logical columns belonging to a singlelogical dimension table. Logical dimensions can exist in the Business Model and Mapping layerand in the Presentation Layer. Adding logical dimensions to the Presentation layer exposesthem to users, which enables users to create hierarchy-based queries. You implement fourlogical dimensions for ABC: Time, Product, Office, and Customer. Creating logical dimensionswith hierarchies allows you to build level-based measures, define aggregation rules that vary bydimension, provide drill down on charts and tables in analyses and dashboards, and define thecontent of aggregate sources.To create logical dimensions with level-based hierarchies, youperform the following steps:

Open the Repository in Offline Mode Create a Logical Dimension for Product Create Logical Levels Associate Logical Columns with Logical Levels


186/387

Set Logical Level Keys Create a Logical Dimension for Time Associate Time Logical Columns with Logical Levels Create a Logical Dimension for Customer Set Aggregation Content for Logical Table Sources Test Your Work




3 . Select BISAMPLE.rpd and click Open. Do not select any BISAMPLE repository with anextension, for example, BISAMPLE_BI0001.rpd. Recall that these are the repositories thathave been loaded into Oracle BI Server memory.


Create a Logical Dimension for Product

1 . In the BMM layer, right-click the Sample Sales business model and select New Object >Logical Dimension > Dimension with Level-Based Hierarchy to open the LogicalDimension dialog box.

2 . Name the logical dimension H2 Product .


187/387

3 . Click OK. The logical dimension is added to the Sample Sales business model.

Create Logical Levels

1 . Right-click H2 Product and select New Object > Logical Level.


188/387

2 . Name the logical level Product Total .


189/387

3 . Because this level represents the grand total for products, select the Grand total level checkbox. Note that when you do this, the Supports rollup to higher level of aggregation field isgrayed out and protected.


190/387

4 . Click OK to close the Logical Level dialog box. The Product Total level is added to the H2Product logical dimension.

5 . Right-click Product Total and select New Object > Child Level to open the Logical Leveldialog box.


191/387

6 . Name the logical level Product Brand.


192/387

7 . Click OK to close the Logical Level dialog box. The Product Brand level is added to thelogical dimension.

8 . Repeat the steps to add the following child levels:

Product LOB as a child of Product Brand


193/387

Product Type as a child of Product LOBProduct Detail as a child of Product Type

Use the screenshot as a guide:

Associate Logical Columns with Logical Levels

1 . Expand the D2 Product logical table.


194/387

2 . Drag the Brand column from D2 Product to the Product Brand level in H2 Product.

3 . Continue dragging logical columns from the D2 Product logical table to their corresponding

levels in the H2 Product logical dimension:

Logical Column Logical Level

Lob Product LOB

Type Product Type

Product Product Detail

Prod Key Product Detail

Your results should look similar to the screenshot:


195/387

Set Logical Level Keys

1 . Double-click the Product Brand logical level to open the Logical Level dialog box. On theGeneral tab, notice that the Product LOB child level is displayed.


196/387

2 . Click the Keys tab.


197/387

3 . Enter Brand for Key Name.


198/387

4 . In the Columns field, use the drop down list to select D2 Product.Brand.


199/387

5 . Check Use for Display. When this is selected, users can drill down to this column from ahigher level.


200/387

6 . Set Brand as the Primary key.


201/387

7 . Click OK to close the Logical Level dialog box. The icon changes for Brand to show that it isthe key for the Product Brand level.


202/387

8 . Use a different technique to create a logical level key: Right-click Lob for the Product LOBlevel and select New Logical Level Key to open the Logical Level Key dialog box.

9 . In the Logical Level Key dialog box, accept the defaults and click OK.


203/387

10 .The icon changes for Lob to show that it is the key for the Product LOB level.

11 .Use either method to set the remaining keys for the H2 Product logical dimension:

LogicalLevel

Logical LevelKey

Use forDisplay

ProductType

Type Yes

ProductDetail

Product Yes


204/387

ProductDetail

Prod Key No


Please note that the Detail level (lowest level of the hierarchy) must have the column that isthe logical key of the dimension table associated with it and it must be the key for that level:Prod Key in this example.

12 .Set Prod Key as the primary key for the Product Detail level. Hint: Double-click the level andselect the Keys tab.


205/387

Create a Logical Dimension for Time

1 . Use a different technique to create a logical dimension for Time. Right-click the D1Time logical table and selectCreate Logical Dimension > Dimension with Level-BasedHierarchy.


206/387

2 . A new logical dimension, D1 TimeDim in this example, is automatically added to the businessmodel.

3 . Rename D1 TimeDim to H1 Time .


207/387

4 . Expand H1 Time . Notice that two level were created automatically: D1 Time Total and D1Time Detail. D1 Time Detail is populated with all of the columns from the D1 Time logicaltable.


208/387

5 . Rename D1 Time Total to Time Total, and rename D1 Time Detail to Time Detail.


209/387

6 . Right-click Time Detail and select New Object > Parent Level to open the Logical Leveldialog box.

7 . On the General tab, name the logical level Week, and check Supports rollup to higher levelof aggregation.


210/387

8 . Click OK to close the Logical Level dialog box. The Week level is added to the H1 Timelogical dimension.

9 . Repeat the steps to add the remaining logical levels:

Month as a parent of WeekQuarter as a parent of MonthHalfas a parent of Quarter


211/387

Year as a parent of Half

Your final results should look similar to the screenshot:

Associate Time Logical Columns with Logical Levels

1 . Use a different technique to associate logical columns with logical levels. Drag the logicalcolumns from the Time Detail logical level (not from the D1 Time logical table) to theircorresponding levels in the H1 Time logical dimension. This is a convenient technique whenlogical columns are buried deep in the business model.

Logical Column Logical Level

Per Name Year Year

Per Name Half Half

Per Name Qtr QuarterPer Name Month Month

Per Name Week Week



212/387

2 . Delete all remaining columns from the Time Detail level except for Calendar Date so thatonly Calendar Date is associated with the Time Detail level. Notice that deleting objects fromthe hierarchy does not delete them from the logical table in the business model.


213/387

3 . Set the logical keys for the H1 Time logical dimension according to the following table:

Logical Level Level Key Use for Display

Year Per Name Year Yes

Half Per Name Half Yes

Quarter Per Name Qtr Yes

Month Per Name Month Yes

Week Per Name Week Yes

Time Detail Calendar Date Yes

Create a Logical Dimension for Customer


214/387

1 . Use either technique to create a logical dimension with a level-based hierarchy named H3Customer for the D3 Customer logical table with the following levels, columns, and keys.Hint: Create the levels first, then double-click a logical column to open the Logical Columndialog box and use the Levels tab to associate the logical column with a logical level.

Level Column Key Use forDisplay

Customer Total

Customer Region Region Region Yes

Customer Area Area Area Yes

CustomerCountry

Country Name Country Name Yes

Customer State State Province State Province Yes

Customer City City City Yes

Customer PostalCode Postal Code Postal Code Yes

Customer Detail

CustomerName

CustomerNumber

CustomerName

CustomerNumber

Yes

No

Set Customer Total as the grand total level.

Set Customer Number as the primary key for the Customer Detail level.



215/387

Set Aggregation Content for Logical Table Sources

1 . Expand D1 Time > Sources.

2 . Double-click the LTS1 Time logical table source to open the Logical Table Source dialog box.


216/387

3 . Click the Content tab.

4 . Confirm that Aggregation content, group by is set to Logical Level and the logical level isset to Time Detail for the H1 Time logical dimension.


217/387

5 . Click OK to close the Logical Table Source dialog box.

6 . Repeat to verify or set content settings for the remaining logical table sources using the tableand screenshots as a guide:

Logical Table SourceLogical

DimensionLogical Level

LTS1 Product H2 Product Product DetailLTS1 Customer H3 Customer

CustomerDetail

LTS2 CustomerAddress

H3 CustomerCustomerDetail

LTS1 RevenueH1 Time Time Detail


218/387

H2 Product

H3 Customer

Product Detail

CustomerDetail


219/387


220/387


221/387

7 . Save the repository and check global consistency. Fix any errors or warnings beforeproceeding. Notice that you did not have to make any changes to the Presentation layer.

8 . Close the repository. Leave the Administration Tool open.

Test Your Work

1 . Return to Fusion Middleware Control and load the BISAMPLE repository. If you need help,click here to review steps from earlier in this tutorial.

2 . Return to Oracle BI, which should still be open, and sign in if necessary.


222/387

3 . Create the following analysis to test the Product hierarchy.

Products.BrandBase Facts.Revenue

4 . Click Results.

5 . Click on the BizTech brand and verify that you can drill down through the hierarchy to seerevenue data at each level.

6 . Select New > Analysis > Sample Sales.


223/387

7 . Click OK to confirm that you want to navigate away from this page.

8 . Create the following analysis:

Time.Per Name YearBase Facts.Revenue


224/387

9 . Click Results and verify that you can drill down through the Time hierarchy.

10 .Repeat the steps and create the following analysis to test the Customers hierarchy:

Customer Regions.RegionBase Facts.Revenue

11 .Click Results and verify that you can drill down through the Customers hierarchy.

12 .Sign out of Oracle BI. Click OK when prompted about navigating away from this page. Leavethe Oracle BI browser page open.

Creating Level-Based Measures

In this set of steps you create level-based measures that calculate total dollars at various levelsin the Product hierarchy, and then use a level-based measure to create a share measure.

To create level-based measures and a share measure, you perform the following steps:


225/387

Open the Repository in Offline Mode Create Level-Based Measures Create a Share Measure Test Your Work




3 . Select BISAMPLE.rpd and click Open. Do not select any BISAMPLE repository with anextension, for example, BISAMPLE_BI0001.rpd. Recall that these are the repositories thathave been loaded into Oracle BI Server memory.


Create Level-Based Measures

1 . In the Business Model and Mapping layer, right-click the F1 Revenue table and select New

Object > Logical Column to open the Logical Column dialog box.


226/387

2 . On the General tab, enter Product Total Revenue in the Name field.


227/387



228/387



229/387

5 . Open the Expression Builder.


230/387

6 . In the Expression Builder, add Logical Tables > F1 Revenue > Revenue to the expression.Recall that the Revenue column already has a default aggregation rule of Sum.


231/387

7 . Click OK to close Expression Builder.

8 . Click the Levels tab.


232/387

9 . For the H2 Product logical dimension, select Product Total from the Logical Level drop-down list to specify that this measure should be calculated at the grand total level in theproduct hierarchy.


233/387

10 .Click OK to close the Logical Column dialog box. The Product Total Revenue measureappears in the Product Total level of the H2 Product logical dimension and the F1 Revenuelogical fact table.


234/387

11 .Repeat the steps to create a second level-based measure:

Name Logical Dimension Logical Level

Product Type Revenue H2 Product Product Type


235/387

12 .Expose the new columns to users by dragging Product Total Revenue and Product TypeRevenue to the Base Facts presentation table in the Sample Sales subject area in thePresentation layer. You can drag the columns from either the H2 Product logical dimension orthe F1 Revenue logical table.


236/387

Create a Share Measure

1 . In the Business Model and Mapping layer, right-click the F1 Revenue table and select NewObject > Logical Column to open the Logical Column dialog box.

2 . On the General tab, name the logical column Product Share.


237/387

3 . On the Column Source tab, select "Derived from existing columns using an expression."


238/387

4 . Open the Expression Builder.


239/387

5 . In the Expression Builder, Select Functions > Mathematic Functions > Round.


240/387

6 . Click Insert selected item. The function appears in the edit box.


241/387

7 . Click Source Number in the formula.


242/387

8 . Enter 100* followed by a space.


243/387

9 . Insert Logical Tables > F1 Revenue > Revenue.


244/387

10 .Using the toolbar, click the Division button. Another set of angle brackets appears,.


245/387

11 .Click .


246/387

12 . Insert Logical Tables > F1 Revenue > Product Total Revenue. Recall that this is the totalmeasure for the hierarchy.


247/387

13 .Click between the last set of angle brackets, , and enter 1. This represents thenumber of digits of precision with which to round the integer.


248/387

14 .Check your work:

Round(100* "Sample Sales"."F1 Revenue"."Revenue" / "Sample Sales"."F1 Revenue"."ProductTotal Revenue" , 1)

This share measure will allow you to run an analysis that shows how revenue of a specificproduct compares to total revenue for all products.

15 .Click OK to close the Expression Builder. The formula is visible in the Logical Column dialogbox.


249/387

16 .Click OK to close the Logical Column dialog box. The Product Share logical column is addedto the business model.


250/387

17 .Add the Product Share measure to the Base Facts presentation table.

18 .Save the repository. Check consistency. You should receive the following message.


251/387

If there are consistency errors or warnings, correct them before you proceed.

19 .Close the repository.

Test Your Work

1 . Return to Fusion Middleware Control and load the BISAMPLE repository. If you need help,click here to review steps from earlier in this tutorial.

2 . Return to Oracle BI, which should still be open, and sign in.

3 . Create the following analysis to test the level-based and share measures.

Products.ProductBase Facts.RevenueBase Facts.Product Type RevenueBase Facts.Product Share

4 . For the Product Share column, select Column Properties.

5 . On the Data Format tab, select Override Default Data Format.


252/387

6 . Change Treat Numbers As to Percentage and set Decimal Places to 2. Deselect Use 1000'sseparator.


253/387

7 . Click OK to close the Column Properties dialog box.

8 . Sort Product Share in descending order.


254/387

9 . Click Results. Notice that Product Type Revenue returns dollars grouped by Type eventhough the query is at a different level than Type; Product in this example. Product Shareshows the percent of total revenue for each product sorted in descending order.

10 .Sign out of Oracle BI.

11 .Click OK when you receive the message: Are you sure you want to navigate away from thispage?

Creating Logical Dimensions with Parent-Child Hierarchies

A parent-child hierarchy is a hierarchy of members that all have the same type. This contrastswith level-based hierarchies, where members of the same type occur only at a single level of thehierarchy. The most common real-life occurrence of a parent-child hierarchy is anorganizational reporting hierarchy chart, where the following all apply:

Each individual in the organization is an employee. Each employee, apart from the top-level managers, reports to a single manager. The reporting hierarchy has many levels.In relational tables, the relationships between different members in a parent-child hierarchy areimplicitly defined by the identifier key values in the associated base table. However, for eachOracle BI Server parent-child hierarchy defined on a relational table, you must also explicitlydefine the inter-member relationships in a separate parent-child relationship table.


255/387

To create a logical dimension with a parent-child hierarchy, perform the following steps:

Open the Repository in Offline Mode Import Metadata and Define Physical Layer Objects Create Logical Table and Logical Columns Create a Logical Join Create a Parent-Child Logical Dimension Define Parent-Child Settings Create Presentation Layer Objects Test Your Work




3 . Select BISAMPLE.rpd and click Open. Do not select any BISAMPLE repository with an

extension, for example, BISAMPLE_BI0001.rpd. Recall that these are the repositories thathave been loaded into Oracle BI Server memory.


Import Metadata and Define Physical Layer Objects

1 . In the Physical layer, expand orcl.

2 . Right-click Connection Pool and select Import Metadata to open the Import Wizard.


256/387

3 . In the Select Metadata Types screen, accept the defaults and click Next.


257/387

4 . In the Select Metadata Objects screen, in the data source view, expand BISAMPLE and select

the following tables for import:

SAMP_EMPL_D_VHSAMP_EMPL_PARENT_CHILD_MAPSAMP_EMPL_POSTN_D


258/387

5 . Click the Import Selected button to move the tables to the Repository View.


259/387

6 . Click Finish to close the Import Wizard.

7 . Confirm that the three tables are visible in the Physical layer of the repository.


260/387

8 . Right-click SAMP_EMPL_PARENT_CHILD_MAP and select View Data.

This is an example of a parent-child relationship table with rows that define the inter-memberrelationships of an employee hierarchy. It includes a Member Key column, which identifies themember (employee); an Ancestor Key, which identifies the ancestor (manager) of the member; aDistance column, which specifies the number of parent-child hierarchy levels from the memberto the ancestor; and a Leaf column, which indicates if the member is a leaf member.

9 . Create the following aliases for the tables:

Table Alias

SAMP_EMPL_D_VH D50 Sales Rep

SAMP_EMPL_PARENT_CHILD_MAPD51 Sales RepParent Child

SAMP_EMPL_POSTN_D D52 Sales Rep


261/387

Position

10 .Use the Physical Diagram to create the following physical joins for the alias tables:

"orcl".""."BISAMPLE"."D52 Sales Rep Position"."POSTN_KEY" ="orcl".""."BISAMPLE"."D50 Sales Rep"."POSTN_KEY"

"orcl".""."BISAMPLE"."D50 Sales Rep"."EMPLOYEE_KEY" = "orcl".""."BISAMPLE"."D51Sales Rep Parent Child"."ANCESTOR_KEY"

"orcl".""."BISAMPLE"."D51 Sales Rep Parent Child"."MEMBER_KEY" ="orcl".""."BISAMPLE"."F1 Revenue"."EMPL_KEY"


262/387

Create Logical Table and Logical Columns

1 . In the BMM layer, right-click the Sample Sales business model and select New Object >Logical Table to open the Logical Table dialog box.


263/387

2 . On the General tab, name the logical table D5 Sales Rep.


264/387

3 . Click OK to add the logical table to the business model.

Notice that the D5 Sales Rep

obiee 11gadmin tool

Documents